Document default values for 'Span.op' on auto instrumented SDKs

[marandaneto]

http.server for HTTP servers
http.client for HTTP clients

Context: #242
Also getsentry/sentry-java#1165 (comment)

Python does http for HTTP clients
https://github.com/getsentry/sentry-python/blob/ca828c9486f4a0030a744849a4e8e10c5a1c7aeb/sentry_sdk/integrations/stdlib.py#L81

as only http alone is ambiguous, I'd prefer to be more specific.

Let's fix this on Python (and what else?) and write it down on the docs?

[marandaneto]

cc @untitaker @rhcarvalho @bruno-garcia

[untitaker]

sgtm

[bruno-garcia]

At first I thought it was related to https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md but turns out it's just our on op for Spans.

Makes sense to align like you suggested. That means we're changing python though @ahmedetefy or @rhcarvalho ? To have http.server and http.client ? Possibly other SDKs too.

[rhcarvalho]

Yes, AFAICT the names were based on old versions of the semantic conventions (same for span statuses).

I'm good with http.server and http.client, don't see a problem with changing this for all SDKs. AFAIK the Sentry UI does not rely on specific names.

[ahmedetefy]

Sounds good! Opened up a ticket for it https://app.asana.com/0/1159797622087522/1200117075062458

[marandaneto]

https://develop.sentry.dev/sdk/performance/span-operations/