[zeeg]

Author here.

Y’all realize we’d just make more money if everyone has better instrumentation and we could spend less time on it, and more time on the product, right?

There is no conspiracy. It’s simple math and reasoning. We don’t compete with most otel consumers.

I don’t know how you could read what I posted and think sentry believes otel is a threat, let alone from the fact that we just migrated our JS SDK to run off it.

[merb]

I use sentry selfhosted and started with Otel under gcloud and grafana and everything worked. Perfectly even, with low effort in dotnet.

However with sentry it’s still a pain and the visualization in sentry is kinda weird, since it goes beyond tracing.

And since sentry itself has no otel endpoint it is also really hard to do things like tail sampling.

[zeeg]

Can you give more context on what you mean around sampling. What does an OTLP endpoint have to do with it?

[merb]

multiple services, that should be sampled based on latency. this only works if you have something like: https://github.com/open-telemetry/opentelemetry-collector-co... or https://grafana.com/docs/tempo/latest/configuration/grafana-... in between.

we do use it quite extensivly besides the overhead, because we get lots of insights wenn we have a slow running endpoint.