pubsub() destination options
The following options are specific to the google-pubsub() destination in syslog-ng OSE.
NOTE: Since this destination is based on the http() destination, the HTTP destination options can also be used. The google-pubsub()
destination automatically configures some of these http()
destination options as required by the Google Pub/Sub AP.
attributes()
Type: | string |
Default: | "--scope rfc5424,all-nv-pairs --exclude MESSAGE" |
Description: A JSON object representing key-value pairs for the Pub/Sub Event, formatted as syslog-ng OSE value-pairs. By default, the google-pubsub()
destination sends the RFC-5424 fields as attributes. If different fields are required, override the default template. By default, the message part is sent in the data()
option
auth()
Description: This is an option for cloud-related authentication. Currently only the GCP Service Account authentication is supported.
Example: storing the key to the service account
auth(
service-account(
key("/path/to/service-account-key.json")
)
)
service-account()
See the example for auth()
above.
data()
Type: | string/template |
Default: | "${MESSAGE}" |
Description: The template used as the data element of the Google Pub/Sub message.
project()
Type: | string/template |
Default: |
Description: The ID of the Google Cloud project where syslog-ng OSE sends the data. The Pub/Sub API must be enabled for the project.
topic()
Type: | string |
Default: |
Description: The name of the Google Pub/Sub target topic to where syslog-ng OSE sends the data.