Open chinwobble opened 3 months ago
I've tracked down the issue. When I add this line
cfg.Instrumentations.Remove(Instrumentation.AWSResource);
The issue is fixed.
Thanks @chinwobble for reporting this, thanks also for finding a fix!
We'll look into ways to improve this. Either we figure out a way to only activate the AWS resource when our distro is used in AWS, oherwise we'll deactivate it by default.
Bug Report
Symptom
A clear and concise description of what the bug is.
What is the expected behavior?
What did you expect to see? That resource labels are working.
What is the actual behavior? When deployed to azure container apps, the telemetry is getting sent to grafana but the metrics and traces don't have any resource labels. I printed out the protobuf and I am seeing this.
Locally everything is working fine. I see prometheus metrics with labels,
instance
,job
, etcWhat did you see instead?
Reproduce
I have a very simple config writing to grafana cloud.
I am using these package versions
Additional Context
I tried setting extra environment variables like
OTEL_SERVICE_NAME
. This sets the service_name but not the instance property.