Heroku log drains

This is the simplest integration path for Heroku applications. Heroku can forward logs directly to logging24 via its syslog drain mechanism, without running your own forwarder process.

When to use this

Your workloads run on Heroku.
You want the fastest managed path into logging24.
You do not want to operate a separate forwarding agent.

Quickstart

heroku drains:add -a YOUR_APP_NAME syslog+tls://ingest.logging24.com:9100
heroku drains --json

After creating the drain, take the drain token reported by Heroku and associate it with a logging24 write token in the web UI.

Setup flow

1. Add the drain

heroku drains:add -a YOUR_APP_NAME syslog+tls://ingest.logging24.com:9100

2. Retrieve the drain token

heroku drains --json

Look for the drain entry pointing to syslog+tls://ingest.logging24.com:9100 . The token value in that entry is the external identifier you bind to the logging24 write token.

3. Create the logging24 write token

Create a new write token in the logging24 web UI.
Select the external-ID mode intended for Heroku drains.
Paste the Heroku drain token as the external identifier.
Choose prefixes that make the logs searchable later, such as app name and environment.

Operational notes

Transport	Heroku sends logs to logging24 over syslog+TLS on port `9100` .
Identity	The Heroku drain token is what links incoming traffic to the logging24 write-token configuration.
Prefix design	Use prefixes that help later query scoping, for example app name in `prefix0` and environment in `prefix1` .

Troubleshooting

Confirm the drain is attached with heroku drains or heroku drains --json .
Verify the drain token was copied exactly into the logging24 token configuration.
If data is still missing, compare this setup with Syslog/TLS Forwarding because Heroku ultimately uses the same receiver path.