Sentry: mapping OTLP service.name to DSNs for multiple Sentry Projects

[sodabrew]

Is your feature request related to a problem? Please describe.

The Sentry exporter takes a DSN argument which maps to a single Project, but I wouldn't want to run a separate OpenTelemetry Collector process for each of my projects.
https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/sentryexporter

Describe the solution you'd like
Ideally, Sentry itself could accept traces for multiple projects through a single API key and use the service name to put the traces into the right one.

Alternatively, have a mapping of service.name to dsn values in the opentelemetry collector config file. This wouldn't require changes to the Sentry hosted service and wouldn't be an unreasonable burden on the collector config (at least to have a starting point for next steps)

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/README.md#service

cc @AbhiPrasad

[AbhiPrasad]

I think this is a very reasonable request - in fact we’ve tracked a similar issue in our fork of the collector. getsentry#10

I’ll assign myself there and see if I can push out a patch. Thanks for reporting!

[sodabrew]

Thank you!

[RyanSiu1995]

Upvote for this.
Instead of getting API key, the exporter maybe can also respect a custom field, which contains DSN, inside the trace data.
Otherwise, we need to have a ton of sentry exporters inside the cluster.

[bloodsper]

Was this ever finished somewhere? If not; have people been setting up an insane amount of sentry exporters?

[Dalkenn]

I am also facing the same issue, was anybody able to do something about it ?

[ananthakumaran]

This issue can be worked around using routing processor. sample below

  processors:
    batch: {}
    memory_limiter: {}
    routing:
      attribute_source: resource
      from_attribute: service.name
      default_exporters:
      - logging
      table:
      - value: foo
        exporters: [sentry/foo]
      - value: bar
        exporters: [sentry/bar]
  exporters:
    logging: {}
    sentry/foo:
      dsn: "https://[email protected]/n"
    sentry/bar:
      dsn: "https://[email protected]/n"
  service:
    pipelines:
      traces:
        receivers:
          - otlp
        processors:
          - memory_limiter
          - batch
          - routing
        exporters:
          - logging
          - sentry/foo
          - sentry/bar

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

Pinging code owners for exporter/sentry: @AbhiPrasad. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• exporter/sentry: @AbhiPrasad

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.