Closed yairt2 closed 1 year ago
Pinging code owners for receiver/kubeletstats: @dmitryax @TylerHelmuth. See Adding Labels via Comments if you do not have permissions to add labels yourself.
Your prometheusremotewrite exporters are missing configuration.
exporters:
prometheusremotewrite:
endpoint: http://victoriametrics-victoria-metrics-cluster-vminsert.monitoring.svc.cluster.local:8480/insert/0/prometheus/api/v1/write
change to
exporters:
prometheusremotewrite:
endpoint: http://victoriametrics-victoria-metrics-cluster-vminsert.monitoring.svc.cluster.local:8480/insert/0/prometheus/api/v1/write
resource_to_telemetry_conversion:
enabled: true
reference docs: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/prometheusremotewriteexporter
Fantastic, that did the job. Thank you very much!
Component(s)
kubeletstats receiver
What happened?
Description: I'm trying to work with the kubeletstats receiver as a replacement for node exporter. All the metrics are being sent to a victoriametrics cluster as a prometheus remote write exporter. The opentelemtery is deployed as a daemon set on my kubernetes cluster. For some reason though i get the metrics, each metric only shows up once (as if they are being accumulated) and the only metric that shows the label k8s_node_name is the metric target_info.
Expected Result: all metrics are tagged with the k8s_node_name
Actual Result: only one metric is tagged "target_info"
Collector version
v0.86.0
Environment information
kubernetes
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response