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
When using the opentelemetry-kube-stack chart, the provided daemon_scrape_configs.yaml contains a kubernetes-pods job. However, I am unable to make this work. Here's the simplest reproduction:
Here are logs from the target allocator. I do see this error:
"error":"could not find collector for node "
I dug into the code but couldn't figure out why it can't get the name of the node.
Target allocator logs
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Starting the Target Allocator"}
{"level":"info","ts":"2025-04-27T07:49:38Z","logger":"allocator","msg":"Starting server..."}
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Waiting for caches to sync for namespace"}
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Caches are synced for namespace"}
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Waiting for caches to sync for servicemonitors"}
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Caches are synced for servicemonitors"} {"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Waiting for caches to sync for podmonitors"}
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Caches are synced for podmonitors"}
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Waiting for caches to sync for probes"} {"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Caches are synced for probes"}
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Waiting for caches to sync for scrapeconfigs"}
{"level":"info","ts":"2025-04-27T07:49:38Z","msg":"Caches are synced for scrapeconfigs"}
{"level":"info","ts":"2025-04-27T07:49:43Z","logger":"allocator","msg":"Service Discovery watch event received","targets groups":3}
{"level":"info","ts":"2025-04-27T07:49:43Z","logger":"allocator","msg":"Could not assign targets for some jobs","allocator":"per-node","targets":1,"error":"could not find collector for node "}
{"level":"info","ts":"2025-04-27T07:49:48Z","logger":"allocator","msg":"Service Discovery watch event received","targets groups":3}
{"level":"info","ts":"2025-04-27T07:53:23Z","logger":"allocator","msg":"Could not assign targets for some jobs","allocator":"per-node","targets":1,"error":"could not find collector for node "}
What am I missing to get this working? The helm chart creates the appropriate service accounts and cluster role + clusterrolebindings.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
When using the
opentelemetry-kube-stack
chart, the provideddaemon_scrape_configs.yaml
contains akubernetes-pods
job. However, I am unable to make this work. Here's the simplest reproduction:values.yaml
I then set up some pods with the
prometheus.io/scrape: "true"
annotation and confirmed they are exposing metrics.I checked the target allocator's
/jobs
:However, the targets are empty:
It is missing the
kubelet
andkubernetes-jobs
jobs. The scrape config is correct though:scrape_configs.json
Here are logs from the target allocator. I do see this error:
I dug into the code but couldn't figure out why it can't get the name of the node.
Target allocator logs
What am I missing to get this working? The helm chart creates the appropriate service accounts and cluster role + clusterrolebindings.
The text was updated successfully, but these errors were encountered: