Syslog Configuration
Configuration to ingest syslog
This section describes configuration parameters to control syslog ingestion
JSON File Configuration
Location on manager node: ~/opt/augtera/etc/telemetry.json
UI Configuration
Configuration under Settings->Config: config->telemetry
Configuration Properties
The following table explains the attributes of Syslog and provides a description of each one of them.
Num | Attribute | Type | Description |
---|---|---|---|
1 | syslog Required Inheritance | Object | Syslog port map configuration |
2 | proto | String | UDP or KafkaReader |
3 | port | Integer | Port designated for syslog traffic. Use the standard port or indicate the designated port. The standard UDP port is 514. |
4 | disable Required | Boolean | Enables or disables syslog configuration. By default, syslog is enabled since it is set to |
Options Configuration | |||
5 | options | List | Define custom options for severity-cutoff, severity-cutoff-low-priority, timezone, and expiration-date. |
6 | severity-cutoff | String | Severity level until which syslog is ingested and carried across Augtera pipeline. The default level is |
7 | severity-cutoff-low-priority | String | Any messages between the |
8 | timezone | String | Indicate the timezone for the syslog source and not the local timezone. This is needed for syslog in RFC 3164 format. If this is configured incorrectly, the data might not appear in the UI Trends. Value should be a standard TZ identifier. |
Following is a sample JSON configuration snippet to ingest syslog over UDP port 514. Data above the warning
level will appear in the UI. Any messages below info
will be dropped. Any message below level warning
and info
will only be ingested if there is a matching classifier.
Last updated