Better handling `op` (span name) when using opentelemetry instrumentation

[antoine-de]

Problem Statement

Hi,

I'm trying to replace the instrumentation in one of my python library from sentry_sdk to opentelementry-api (but still sending the traces to sentry.io), and it's way easier than when I tried some time ago, thanks 👍 (even if the documentation could use a migrating guide).

One thing that is bothering me is the different way of handling op (also called span.name). Before the op cardinality when very limited, and a good way to find the traces in sentry (I'm using the hosted sentry.io). But now, I don't see an easy way to control this op (it seems that apart from some http/db cases, it's only the name of the span).

Then it's harder to group the traces by name.

Is there a way to control this?

Solution Brainstorm

No response

Product Area

Unknown

[linear]

ENG-6487

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-performance for triage ⏲️

[bcoe]

@antoine-de the problem of how to populate op has been something top of our minds as we build our OTLP solution.

This ticket has been triaged and @mjq will follow up.

[mjq]

Hi @antoine-de!

You're right that we only automatically generate an op for a subset of OTel spans. But, you can control an OTel span's op in Sentry yourself by setting a sentry.op attribute on your OTel span. Does that help?