SyslogConfiguration
{
"enabled": false,
"address": "string",
"port": "string",
"transport_protocol": "string",
"queue_size": 0,
"tls_enabled": false,
"permitted_peer": "string",
"ssl_ca_certificate": "string",
"environment": "string",
"forward_debug_logs": false,
"custom_rsyslog_configuration": "string"
}Change this to true to use syslog
Required. The address or host for the syslog server. Can be a hostname or an IP address
Required. The port on which the syslog server listens
Required. The transport protocol used to send syslog messages to the server
Optional. The number of log messages the buffer holds before dropping messages. A larger buffer size might overload the system.
Required. Change this to true to use TLS.
Required when using tls_enabled is true. Either the accepted fingerprint (SHA1) or name of remote peer, e.g. *.example.com
Required when using tls_enabled is true. This certificate will ensure that logs get securely transported to the syslog destination
A human-readable identifier that will be included in log lines
Optional. Some components produce voluminous debug logs. Change this to true to prevent debug logs from being forwarded. They will still be written to local disk.
Optional. Accepts configuration for rsyslog in the rainerscript syntax. For example, 'if ($app-name startswith "exampleComponent") then stop' can be used to drop all traffic from a particular component. Entered configuration will be applied prior to the forwarding rule.