Sentry exporter not exporting traces to sentry

[chkp-talron]

Component(s)

exporter/sentry

What happened?

I've had a working setup with collector and jaeger but due to issues with it's backend storage im looking into using another backend. sentry also exists in our company so Im trying to export my traces to it.
it seems sentry exporter is loaded but nothing is actually being exported.
I can't see any debug logs for it from the collector and i cant see any data in sentry.

I'm not using the sentry sdk in my services, just exporting traces from my services using otlp as done for jeager.
AFAIK, that should suffice for basic tracing, no need for the extra features the sentry sdk gives fror now.

with jaeger i could see connection status before data was sent to jaeger
with sentry i cant see any connection to sentry backend.

Collector version

0.91.0

Environment information

Environment

AWS EKS
Sentry version: self-managed 21.8.0 (this is quite old but that what's installed on out site, not sure if this is the issue)

OpenTelemetry Collector configuration

exporters:
      sentry:
        dsn: my-dsn
        environment: my-env
        insecure_skip_verify: true
      logging:
        verbosity: detailed
    extensions:
      health_check: {}
      memory_ballast:
        size_in_percentage: 20
    processors:
      batch: {}
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: ${env:MY_POD_IP}:4317
          http:
            endpoint: ${env:MY_POD_IP}:4318
    service:
      extensions:
      - health_check
      - memory_ballast
      pipelines:
        traces:
          exporters:
          - logging
          - sentry
          processors:
          - batch
          receivers:
          - otlp
      telemetry:
        logs:
          level: DEBUG

Log output

2023-12-24T07:12:12.484Z        info    service@v0.91.0/telemetry.go:86 Setting up own telemetry...
2023-12-24T07:12:12.484Z        info    service@v0.91.0/telemetry.go:203        Serving Prometheus metrics      {"address": ":8888", "level": "Basic"}
2023-12-24T07:12:12.484Z        debug   extension@v0.91.0/extension.go:165      Beta component. May change in the future.       {"kind": "extension", "name": "health_check"}
2023-12-24T07:12:12.484Z        debug   extension@v0.91.0/extension.go:165      Beta component. May change in the future.       {"kind": "extension", "name": "memory_ballast"}
2023-12-24T07:12:12.484Z        info    exporter@v0.91.0/exporter.go:275        Deprecated component. Will be removed in future releases.       {"kind": "exporter", "data_type": "traces", "name": "logging"}
2023-12-24T07:12:12.484Z        debug   exporter@v0.91.0/exporter.go:273        Beta component. May change in the future.       {"kind": "exporter", "data_type": "traces", "name": "sentry"}
2023-12-24T07:12:12.484Z        debug   processor@v0.91.0/processor.go:287      Stable component.       {"kind": "processor", "name": "batch", "pipeline": "traces"}
2023-12-24T07:12:12.484Z        debug   receiver@v0.91.0/receiver.go:294        Stable component.       {"kind": "receiver", "name": "otlp", "data_type": "traces"}
2023-12-24T07:12:12.485Z        info    service@v0.91.0/service.go:145  Starting otelcol-contrib...     {"Version": "0.91.0", "NumCPU": 4}
2023-12-24T07:12:12.486Z        info    extensions/extensions.go:34     Starting extensions...
2023-12-24T07:12:12.486Z        info    extensions/extensions.go:37     Extension is starting...        {"kind": "extension", "name": "memory_ballast"}
2023-12-24T07:12:12.560Z        info    ballastextension@v0.91.0/memory_ballast.go:41   Setting memory ballast  {"kind": "extension", "name": "memory_ballast", "MiBs":3164}
2023-12-24T07:12:12.560Z        info    extensions/extensions.go:52     Extension started.      {"kind": "extension", "name": "memory_ballast"}
2023-12-24T07:12:12.561Z        info    extensions/extensions.go:37     Extension is starting...        {"kind": "extension", "name": "health_check"}
2023-12-24T07:12:12.562Z        info    healthcheckextension@v0.91.0/healthcheckextension.go:35 Starting health_check extension {"kind": "extension", "name": "health_check", "config": {"Endpoint":"0.0.0.0:13133","TLSSetting":null,"CORS":null,"Auth":null,"MaxRequestBodySize":0,"IncludeMetadata":false,"ResponseHeaders":null,"Path":"/","ResponseBody":null,"CheckCollectorPipeline":{"Enabled":false,"Interval":"5m","ExporterFailureThreshold":5}}}
2023-12-24T07:12:12.574Z        warn    internal@v0.91.0/warning.go:40  Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks        {"kind": "extension", "name": "health_check", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-12-24T07:12:12.574Z        info    extensions/extensions.go:52     Extension started.      {"kind": "extension", "name": "health_check"}
2023-12-24T07:12:12.574Z        info    zapgrpc/zapgrpc.go:178  [core] [Server #1] Server created       {"grpc_log": true}
2023-12-24T07:12:12.574Z        info    otlpreceiver@v0.91.0/otlp.go:83 Starting GRPC server    {"kind": "receiver", "name": "otlp", "data_type": "traces", "endpoint":"10.104.91.138:4317"}
2023-12-24T07:12:12.575Z        info    otlpreceiver@v0.91.0/otlp.go:101        Starting HTTP server    {"kind": "receiver", "name": "otlp", "data_type": "traces", "endpoint": "10.104.91.138:4318"}
2023-12-24T07:12:12.575Z        info    healthcheck/handler.go:132      Health Check state change       {"kind": "extension", "name": "health_check", "status": "ready"}
2023-12-24T07:12:12.575Z        info    service@v0.91.0/service.go:171  Everything is ready. Begin running and processing data.
2023-12-24T07:12:12.576Z        info    zapgrpc/zapgrpc.go:178  [core] [Server #1 ListenSocket #2] ListenSocket created {"grpc_log": true}

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/sentry: @AbhiPrasad

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

[JaredTan95]

No more specific exception logs are provided

[chkp-talron]

No more specific exception logs are provided

that the issue, i don't see any exception related to sentry exporter

[AbhiPrasad]

If you set up a SAAS sentry instance and try to send some data to it, does it show up? I'm wondering if this is a self-hosted issue.

The OTEL config seems fine to me.

[chkp-talron]

we are not authorized per company security policy to send data outside of our env, hence the local sentry deployment.
if there is an issue with connecting to sentry i assume extra debug logs in the exporter would help, as i cant see any logs for this exporter.

[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.