Log Drain Support for Sentry Logging

[AbhiPrasad]

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.

[sgarner]

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]

@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]

✅ 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 /logdrain route.

[strokirk]

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.id would be useful to correlate.