service_name or something should match between traces and profiles

[madhan29]

I have a question I was enabled all the things but still not getting pyroscope.profile.id as a attribute question here is service name is both traces and profiles also should match because in profile I was tagging servcie name differently, in trace it's being collected automatically so it's not matching.

[aleks-p]

The main reason we want matching service names between traces and profiles is so that the profile with that id can be uniquely and efficiently discovered in the Pyroscope read path.

If you don't control the service names, you could use other labels that are more likely to match, e.g., namespace + container in Kubernets contexts. Of course, this only works if those labels are sent to Pyroscope which requires a bit of work when using this extension but should in theory be possible.

When using traces-to-profiles with Tempo, you would configure those labels in the datasource as described at https://grafana.com/docs/grafana-cloud/connect-externally-hosted/data-sources/tempo/configure-tempo-data-source/#trace-to-profiles.

[madhan29]

@aleks-p thanks for the reply I can use other labels the problem I was facing is after instrumenting pyroscope java agent and otel java agent with my application mentioned as per this link
https://grafana.com/docs/pyroscope/latest/configure-client/trace-span-profiles/java-span-profiles/
still i'm not getting pyroscope.profile.id as label in my traces, so I tried for go and got to know that pyroscope itself instrumented with required sdk to correlate traces to profiles, so I tested pyroscope traces still I can't see pyroscope.profile.id as labels
I was using grafana alloy + beyla integration to collect traces and metrics and pyroscope.ebpf and pyroscope.java to collect profiles.