Closed hamidp555 closed 11 months ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Hi @hamidp555, we don't handle service_id
in any special way on the metrics exporter: it is not added based on any other attributes or handled differently from any other custom tag. Your logs only show the ekziwbvbed5
value, so it does not seem like the exporter is adding multiple service_id
values on the metrics you shared with us. To further troubleshoot this, I would recommend:
gke-dt-testing-gke-d-prod1k-node-pool-3fde0b3b-5z2m.stellar-arcadia-205014
)service_id
values on your logs Hi @mx-psi thank you for your response, we will follow the troubleshooting suggestions I can see that the metric data from some collector with the same resources.name later on caused the issue in datadog. I was wondering how the resources: [{"name": "somevalue", "type": "host"}] can be configured for collector?
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been closed as inactive because it has been stale for 120 days with no activity.
Component(s)
exporter/datadog
What happened?
Description
The grouping of service metrics (exported by datadog exporter) in Datadog seems incorrect
Steps to Reproduce
1 - Deploy a collector with datadog exporter configured in GKE or AKS cluster 2 - Create a notebook in Datadog for one of the metrics coming from the collector 3 - filter by service_id 4 - You will see one metric associated with TWO service ids
Expected Result
Metric data is filtered by one servive_id and only ONE service_id should be seen for the metric data
Actual Result
Metric data is filtered by one servive_id and TWO different service_ids are seen for the metric data
If collector is restarted one of the service_id changes randomly
Collector version
0.71.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
Additional context
No response