Open thinkocapo opened 9 months ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-sdks-web-backend for triage ⏲️
Routing to @getsentry/product-owners-docs for triage ⏲️
Routing to @getsentry/product-owners-sdks-web-backend for triage ⏲️
PHP is documented in the same place as Python, see https://docs.sentry.io/platforms/php/usage/distributed-tracing/custom-instrumentation/.
We had some internal debate about where to put this piece of information. I definitely agree with you that this is a bit hidden. We'll take another look!
as per discussion this should be discoverable coming from either direction
I had 2 customers in the past month request this for Golang. Contact me for details.
I agree with @thinkocapo and @cleptric that putting it under "Sentry for X > Usage > Distributed Tracing > Custom Instrumentation"
is basically hiding it.
We should have a top level section like "Performance Monitoring"
for "Distributed Tracing"
.
This was not done in the past, because we have no product called “distributed tracing” and we only have those top level sections for products of Sentry.
I think it still makes sense though to have a top level section “distributed tracing”.
Core or SDK?
Platform/SDK
Which part? Which one?
all backend SDK's
Description
A lot of time wasted debugging why tracing doesn't work. It happened recently with Azure Functions, and there's no clear code example workaround (Custom Instrumentation) on how to do it.
relates to https://github.com/getsentry/sentry-javascript/issues/8996 may relate to https://github.com/getsentry/sentry-javascript/issues/9011
Python docs have the example code on how to extract trace info and set it properly.
It's under Usage > Distributed Tracing > Custom Instrumentation > Extract Incoming Trace Information
Documentation for... Node does not have it PHP does not have it
Suggested Solution