Repository navigation
Log Drain Support for Sentry Logging #91726
Description
You can now send structured logs to Sentry! See the docs here.
Currently you need to use one of our SDKs to send logs, but we're exploring the use case of Log Drains. This issue tracks supporting log drain providers.
If you're interested in log drain support, please leave a react on this GitHub issue. That will help us prioritize this accordingly. We created some child issues to track popular providers, but if there is a provider missing let us know and we'll open a new issue for it.
Reacted by Simon Garner, leo-naeka, Paul Kuruvilla, zip-fa, Ansgar Hofmann, Neal Shepherd, Arkadiusz Sygulski, Philipp Steinrötter, Jesper Pedersen, Ian Tuomi and 18 more
Reacted by Dhrumil, Philipp Steinrötter, Oleh Pylypchak, Billy Taggart and Paul Kuruvilla
Activity
sgarner commentedon May 15, 2025
I would like to see Sentry supported as a Log Sink for Vector.
This could be as simple as Sentry having a compatible HTTP endpoint for receiving logs:
https://vector.dev/docs/reference/configuration/sinks/http/
Dhrumil-Sentry commentedon May 16, 2025
@sgarner how do you debug application code problems with logs from other sources? Just want to understand a few examples and your workflows today
lucas-devx commentedon May 16, 2025
✅ Suggested Solution
To support generic log drain providers, expose a universal ingestion endpoint that accepts structured log payloads (JSON over HTTP) with provider-specific adapters for normalization.
🔧 Each adapter could map common log fields (e.g.,
timestamp,level,message,request) into Sentry's event schema.📍Extend the existing ingestion pipeline or create a lightweight log-ingest service behind a
/logdrainroute.strokirk commentedon May 16, 2025
It's commonly useful to want see related logs from Apache, Nginx, other microservices, etc, when debugging an issue.
The Elastic Common Schema is amazingly useful to coordinate the naming of common log fields between multiple sources:
https://www.elastic.co/docs/reference/ecs
Anything with the same
trace.idwould be useful to correlate.49 remaining items
feat(config): Add vercel log drain endpoint feature flag (#5208)
feat(config): Add vercel log drain endpoint feature flag (#5208)
bastien-wink commentedon Oct 15, 2025
My logs are in CloudWatch, gathered from various files using CloudWatch agent. Are you planning a log drain for CloudWatch or maybe a simple a file watcher like Logstash can do ?
nickfreemandesign commentedon Oct 15, 2025
my solution is to just tail logs using the sentry-cli and then pipe those into cloudwatch. we will likely deprecate over time, sentry is just a middleman.
AbhiPrasad commentedon Oct 15, 2025
@bastien-wink you have a couple options here!
If you use the OpenTelemetry Collector, you can set up the filelogreciever to watch a file and forward this to Sentry via Sentry's OTLP Logs Endpoint. The Sentry docs for this are here: https://docs.sentry.io/concepts/otlp/#opentelemetry-logs.
You can set up a Fluentbit Agent, which has a file input, and then set up an OpenTelemetry Output to to Sentry's OTLP endpoint. Same design as the OTEL collector, just a different agent. Someone did this here Fluentbit.io Log Drain Support for Sentry Logging #98440 (comment)
Wait for us to finish up support for a Sentry sink for Vector, Vector Log Sink Support for Sentry Logging #92400. Then you can run a vector agent accordingly.
I would really recommend the OTEL collector! It's vendor agnostic and CNCF sponsored, and there are a variety of ways to configure it. This feels better than anything that is connected to a specific vendor (Cloudwatch agent -> AWS, Logstash -> Elastic, Vector -> Datadog).
We do have this issue, #98729, but we'll most likely just end up writing a guide that shows you how to forward your
CloudWatchto a lambda function, and then export your logs to Sentry after that.runephilosof-abtion commentedon Oct 16, 2025
It would be nice to get support for Scalingo https://doc.scalingo.com/platform/app/log-drain, either by supporting one of their existing protocols (syslog + tcp) or by working with Scalingo to have them add support for Sentry on their end.
AbhiPrasad commentedon Oct 16, 2025
@runephilosof-abtion I created a GH issue to track this here: #101599. I recommend reaching out to Scalingo support as well, maybe that'll help them prioritize this on their side!