Logging
Crunchy Bridge has logging integration to allow you to send your logs from your Postgres database to another logging-as-a-service provider.
All logs are send over TLS and verify the certificate of where they’re sending logs to. You can configure your logging integration for a database in the logging configuration panel.
Crunchy Bridge currently supports any logging provided that has a public certificate available within CentOS 8.
To help in configuring you can find the sample guide for a number of logging providrs:
LogDNA
Host: syslog-a.logdna.com
Template: <${PRI}>1 ${ISODATE} ${HOST} ${PROGRAM} ${PID} ${MSGID} [[email protected] key=\"**INSERT-YOUR-INGESTION-KEY-HERE**\"] $MSG\n
Port: 6514
Loggly
Host: logs-01.loggly.com
Template: <${PRI}>1 ${ISODATE} ${HOST} ${PROGRAM} ${PID} ${MSGID} [[email protected] tag=\"TAG\" ] $MSG\n
Port: 6514
LogEntries (Rapid7 InsightOps)
Host: REGION.data.logs.insight.rapid7.com
(where REGION is us or eu)
Template: TOKEN_HERE $ISODATE $HOST $MSG\n
Port: 443
SumoLogic
Host: syslog.collection.YOUR_DEPLOYMENT.sumologic.com
Template: <$PRI>1 $ISODATE $HOST $PROGRAM $PID $MSGID [[email protected]] $MSG\n
Port: 6514
Papertrail
Hostname: logsN.papertrailapp.com
(Where N is some integer)
Port: per-user
Template: The default is accepted. Some plans support IP restrictions (which may work with AWS if IPv6 is supported)
Datadog
Host: intake.logs.datadoghq.com
Template: <API_KEY> <${PRI}>1 ${ISODATE} ${HOST:--} ${PROGRAM:--} ${PID:--} ${MSGID:--} [[email protected] ddsource=\"test\" ddtags=\"env:test,user:test_user,<KEY:VALUE>\"] $MSG\n
Port: 10516