siteadmin:filebeat_for_windows_configuration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| siteadmin:filebeat_for_windows_configuration [2018/03/06 09:30] – admin | siteadmin:filebeat_for_windows_configuration [2019/10/18 13:54] (current) – [Experimental] admin | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Edit the filebeat.yml file: | Edit the filebeat.yml file: | ||
| - | - Under **filebeat.prospectors** make the path the path to the directory containing the NPS log files (e.g C: | + | - Under **filebeat.prospectors** make the path the path to the directory containing the NPS log files (e.g //C: |
| - | - If there is a line 'enabled: false' | + | - If there is a line **enabled: false** then change it to **true**. |
| - | - Make sure that the 'output.elasticsearch' | + | - Make sure that the **output.elasticsearch** output is commented out |
| - | - Under 'output.logstash' | + | - Under **output.logstash** the key line is **hosts: |
| - Everything else in that section should be commented out. | - Everything else in that section should be commented out. | ||
| - Start/ | - Start/ | ||
| - | This is the bare minimum for taking the logs from NPS and sending them to the Govroam log server. Get this working first before trying the encryption. JISC will need to know the hostname/IP address of the system sending the logs (or the public IP from which the logs originate) so that the firewall can be updated. | + | This is the bare minimum for taking the logs from NPS and sending them to the Govroam log server. Get this working first before trying the encryption. |
| + | |||
| + | **JISC will need to know the hostname/IP address of the system sending the logs (or the public IP from which the logs originate) so that the firewall can be updated.** | ||
| Adding encryption is pretty straightforward. | Adding encryption is pretty straightforward. | ||
| - | - Under 'output.logstash' | + | - Under **output.logstash** add the line **ssl.enabled: |
| - | - Change the port from 5044 to 5055. | + | - Change the port from **5044** to **5055**. |
| + | |||
| + | If you're using the hostname **elk.govroam.uk** and have a set of Root CAs installed (normally the default for the OS) then filebeat should just be able to enable encryption. Run it in command line mode to see any errors. See the [[https:// | ||
| + | |||
| + | ====Experimental==== | ||
| + | |||
| + | Suggested here: https:// | ||
| - | If you're using the hostname ' | + | < |
| + | filebeat.prospectors: | ||
| + | - type: log | ||
| + | paths: | ||
| + | - /path/to/log | ||
| + | encoding: ' | ||
| + | # multiline.pattern: ' | ||
| + | # multiline.negate: | ||
| + | # multiline.match: after | ||
| + | fields_under_root: | ||
| + | </ | ||
siteadmin/filebeat_for_windows_configuration.1520328643.txt.gz · Last modified: 2018/03/06 09:30 by admin
