Skip to content

Heroku drain / syslog #28270

@chr4ss12

Description

@chr4ss12

Problem Statement

I am trying to log Heroku system errors and send them to Sentry, the only way to do it is using Log drains: https://devcenter.heroku.com/articles/log-drains#syslog-drains

Right now it is possbible to create new HTTP webservice as a log drain that wraps Sentry, but it's not optimal and also can get quite expensive / is not too trivial to set up.

That gives us a way to see errors such as when timeout happens, when deployment fails, when dynos are restarted due to unexpected issues, eg anything that is not coming directly from the hosted app itself.

Solution Brainstorm

It would be nice if

  1. Sentry would expose some kind of syslog drain that I can use
  2. I can configure what gets filtered (heroku emits a lot of information messages)

Papertrail already provides what I am looking for (as far as Heroku goes: https://www.papertrail.com/help/heroku/) but it would be nice to stick with Sentry

https://stackoverflow.com/questions/29754052/integrate-heroku-system-errors-with-sentry

We want to define a set of lightweight metrics that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that do NOT overlap with Tracing. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples**:**

  • Node.js runtime metrics (e.g., event loop delay, heap usage)
  • Prisma-related metrics in Next.js
  • Mobile CPU / memory usage to help surface potential ANRs or app hangs

Candidate Metrics (add more below)

(please also add ideas, questions or examples in comments)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No fields configured for issues without a type.

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions