You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hostmetrics and kubeletstats receivers don't add a service.name and service.instance.id attribute, therefore when the OpenTelemetry Collector creates a target_info metric, the resource attributes are copied to the new metric and dropped from the scraped metric. This leaves the scraped metric with no resource attributes.
Should these attributes be added in the pipeline using the OpenTelemetry Collector pod name and id?
The hostmetrics and kubeletstats receivers don't add a
service.name
andservice.instance.id
attribute, therefore when the OpenTelemetry Collector creates atarget_info
metric, the resource attributes are copied to the new metric and dropped from the scraped metric. This leaves the scraped metric with no resource attributes.Should these attributes be added in the pipeline using the OpenTelemetry Collector pod name and id?
Reference: https://opentelemetry.io/docs/specs/otel/compatibility/prometheus_and_openmetrics/#resource-attributes-1
The text was updated successfully, but these errors were encountered: