Heroku

This guide configures logs. Replace YOUR_INGEST_KEY with your key on your server, never in a public example.

1. Create an HTTPS drain

Heroku sends application/logplex-1 frames using Basic authentication, with the ingest key as the password. This drain URL contains credentials. Treat it as a secret, avoid shell history and screenshots, and rotate the key if exposed.

heroku drains:add 'https://siteqwality:YOUR_INGEST_KEY@otlp.siteqwality.com/v1/heroku' --app YOUR_APP
heroku drains --app YOUR_APP

2. Generate traffic and verify

Make an application request that emits a log. This adapter collects Logplex frames, not arbitrary JSON. Use an application SDK for traces and metrics. Configure service/environment defaults on the ingest key when Logplex does not carry them.

heroku logs --tail --app YOUR_APP

See your data

Open Logs, Traces or Metrics. New data usually shows up within a minute, and a page that says it is waiting for data switches to your data on its own. Nothing arriving? See what each status code means in failure handling.

Production checklist

Store the key in your platform secret mechanism, rotate it when exposed and remove test keys. Set a stable service.name and deployment.environment.name; avoid user IDs or unbounded values in metric labels. Prefer a persistent queue, bounded retries and exporter failure monitoring. Review redaction and processors before increasing traffic.