Add a Log Drain to your App

Integration Purposes

When an application starts having a higher traffic, reading logs can be cumbersome. Using a log management solution to gather the logs from all your applications and all your containers eases your work when trying to find an information amongst all these lines of logs. A few SaaS solutions exist such as Logentries, Logmatic.io, Papertrail or Graylog. You can also host such solution on Scalingo. Here is a tutorial on how to deploy the ELK stack on Scalingo. We also support sending your applications logs using the standard syslog protocol over UDP, TCP or TCP+TLS.

Third-party Provider integrations

Our system is also able to send logs to the following SaaS log processing providers:

  • Scalingo hosted ELK stack (how to setup)
  • Datadog
  • Logentries
  • Graylog
  • Papertrail
  • Syslog

Configuration of your Application on Scalingo

As this feature is private beta, you cannot activate logs drain by yourself. You need to add an environment variable containing the token to the used logs management service, and contact the support so that we activate the logs drain. In a matter of minutes, your logs flow to the logs management service.

The format of the environment variable depends on the provider:

  • Scalingo hosted ELK stack: https://USER:TOKEN@logstash-app-name.osc-fr1.scalingo.io
  • Datadog: datadog://DD_API_KEY?region=REGION. DD_API_KEY is the Datadog API key you can find here. REGION value is either eu or us depending on your Datadog account region.
  • Logentries: https://webhook.logentries.com/noformat/logs/LOG-TOKEN. Instructions to get the LOG-TOKEN are available on Logentries documentation.
  • OVH hosted Graylog: ovh://:TOKEN@REGION.logs.ovh.com:6514. Instructions to get the TOKEN and REGION variables are available on OVH documentation.
  • Papertrail: syslog+tls://logsN.papertrailapp.com:XXXXX. logsN and XXXXX are the log host and port number shown under log destination.
  • Syslog TCP+TLS: tcp+tls://example.com:12345

mode_edit Suggest edits