Rewrite fi - unset: field: "json.kubernetes.cluster"
For details, see the documentation of the AxoSyslog syslog-ng distribution.
SyslogNGOutput and SyslogNGClusterOutput resources have almost the same structure as Output and ClusterOutput resources, with the main difference being the number and kind of supported destinations.
You can use the following syslog-ng outputs in your SyslogNGOutput and SyslogNGClusterOutput resources.
SyslogNGOutput
SyslogNGClusterOutput
GRPC-based outputs use this configuration instead of the simple tls field found at most HTTP based destinations. For details, see the documentation of a related syslog-ng destination, for example, Grafana Loki.
tls
Application Default Credentials (ADC).
Application Layer Transport Security (ALTS) is a simple to use authentication, only available within Google’s infrastructure.
This is the default method, authentication is disabled (auth(insecure())).
auth(insecure())
This option sets various options related to TLS encryption, for example, key/certificate files and trusted CA locations. TLS can be used only with tcp-based transport protocols. For details, see TLS for syslog-ng outputs and the documentation of the AxoSyslog syslog-ng distribution.
Authentication settings. Only one authentication method can be set. Default: insecure
The parameters of the syslog-ng disk buffer. Using a disk buffer on the output helps avoid message loss in case of a system failure on the destination side. For details on how syslog-ng disk buffers work, see the documentation of the AxoSyslog syslog-ng distribution.
Prunes the unused space in the LogMessage representation
Description: Defines the folder where the disk-buffer files are stored.
This is a required option. The maximum size of the disk-buffer in bytes. The minimum value is 1048576 bytes.
Use this option if the option reliable() is set to no. This option contains the number of messages stored in overflow queue.
Use this option if the option reliable() is set to yes. This option contains the size of the messages in bytes that is used in the memory part of the disk buffer.
The number of messages stored in the output buffer of the destination.
If set to yes, syslog-ng OSE cannot lose logs in case of reload/restart, unreachable destination or syslog-ng OSE crash. This solution provides a slower, but reliable disk-buffer option.
Based on the ElasticSearch destination of AxoSyslog core.
apiVersion: logging.banzaicloud.io/v1beta1 @@ -2810,7 +2810,7 @@ 4.8.6.17 - Syslog (RFC5424) output< key: tls.key name: syslog-tls-cert transport: tls
For details on the available options of the output, see the documentation of the AxoSyslog syslog-ng distribution.
By default, syslog-ng OSE closes destination sockets if it receives any input from the socket (for example, a reply). If this option is set to no, syslog-ng OSE just ignores the input, but does not close the socket. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Enables putting outgoing messages into the disk buffer of the destination to avoid message loss in case of a system failure on the destination side. For details, see the Syslog-ng DiskBuffer options.
Flags influence the behavior of the destination driver. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Specifies how many lines are flushed to a destination at a time. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Address of the destination host
Unique name for the syslog-ng driver. If you receive the following error message during syslog-ng startup, set the persist-name() option of the duplicate drivers: Error checking the uniqueness of the persist names, please override it with persist-name option. Shutting down. See the documentation of the AxoSyslog syslog-ng distribution for more information.
persist-name()
Error checking the uniqueness of the persist names, please override it with persist-name option. Shutting down.
The port number to connect to. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Enables keep-alive messages, keeping the socket open. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Specifies the number of seconds syslog-ng waits for identical messages. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Specifies a template defining the logformat to be used in the destination. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Default: 0
Turns on escaping for the ‘, “, and backspace characters in templated output files. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Sets various options related to TLS encryption, for example, key/certificate files and trusted CA locations. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Specifies the protocol used to send messages to the destination server. For details, see the documentation of the AxoSyslog syslog-ng distribution.
Override the global timestamp format (set in the global ts-format() parameter) for the specific destination. For details, see the documentation of the AxoSyslog syslog-ng distribution.
For details on how TLS configuration works in syslog-ng, see the AxoSyslog Core documentation.
The name of a directory that contains a set of trusted CA certificates in PEM format. For details, see the AxoSyslog Core documentation.
The name of a file that contains a set of trusted CA certificates in PEM format. (Optional) For details, see the AxoSyslog Core documentation.
Name of a file, that contains an X.509 certificate (or a certificate chain) in PEM format, suitable as a TLS certificate, matching the private key set in the key-file() option. For details, see the AxoSyslog Core documentation.
Description: Specifies the cipher, hash, and key-exchange algorithms used for the encryption, for example, ECDHE-ECDSA-AES256-SHA384. The list of available algorithms depends on the version of OpenSSL used to compile syslog-ng.
The name of a file that contains an unencrypted private key in PEM format, suitable as a TLS key. For details, see the AxoSyslog Core documentation.
Verification method of the peer. For details, see the AxoSyslog Core documentation.
Configure required TLS version. Accepted values: [sslv3, tlsv1, tlsv1_0, tlsv1_1, tlsv1_2, tlsv1_3]
Use the certificate store of the system for verifying HTTPS certificates. For details, see the AxoSyslog Core documentation.
The name of a file that contains a set of trusted CA certificates in PEM format. For details, see the AxoSyslog Core documentation.
Name of a file that contains an X.509 certificate (or a certificate chain) in PEM format, suitable as a TLS certificate, matching the private key set in the key-file() option. For details, see the AxoSyslog Core documentation.
The following examples show some simple flows. For more examples that use filters, see Filter examples in Flows.
This Flow sends every message with the app: nginx label to the output called forward-output-sample.
app: nginx
forward-output-sample
This Flow sends every message with the app: nginx label to the gcs-output-sample and s3-output-example outputs.
gcs-output-sample
s3-output-example
Simple Logging definition with default values.
Simple Logging definition with TLS encryption enabled.
Defines a file output with timestamped log files.
Creates a dev/null output that can be the destination of messages you want to drop explicitly.
CAUTION:
Defines an Amazon S3 output to store your logs in a bucket.
Defines a Google Cloud Storage output to store your logs.
Rewrite filt - unset: field: "json.kubernetes.cluster"
apiVersion: logging.banzaicloud.io/v1beta1 @@ -2419,7 +2419,7 @@ 8.6.17 - Syslog (RFC5424) output key: tls.key name: syslog-tls-cert transport: tls