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
I have difficulties completing the configuration of otelcol and kubernetes information.
I feel there is something blurry in the metric I collect from my cluster, because, even with a simple configuration, I cannot retrieve container.id from extra_metadata_labels in kubeletstats.
In my understanding, this is the only way to help further k8sattributes to attach all the k8s. resource attributes to the metrics kubeletstats generates (… for pod and container metrics).
What I feel strange is also I cannot connect to the node metric server on port 10250 from node name.
Pinging code owners for receiver/kubeletstats: @dmitryax@TylerHelmuth@ChrsMark. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.
Component(s)
receiver/kubeletstats
Describe the issue you're reporting
I have difficulties completing the configuration of otelcol and kubernetes information.
I feel there is something blurry in the metric I collect from my cluster, because, even with a simple configuration, I cannot retrieve
container.id
fromextra_metadata_labels
inkubeletstats
.In my understanding, this is the only way to help further
k8sattributes
to attach all thek8s.
resource attributes to the metricskubeletstats
generates (… for pod and container metrics).What I feel strange is also I cannot connect to the node metric server on port
10250
from node name.reference
v1.31.1
otel/opentelemetry-collector-k8s:0.120.0
configuration
Kubeletstat receiver
Full configuration
Cluster Role
helm additional configuration
I disabled most of presets, using
alternateConfig
to limit the number of automatic writing…Also, checking proxy/stats/summary don't show any
container.id
. Not sure this is a clue:metric from /api/v1/nodes/nodeName:10250/proxy/stats/summary
The text was updated successfully, but these errors were encountered: