-
Notifications
You must be signed in to change notification settings - Fork 1.9k
metricbeat - kubernetes event.module gets "connection refused" accessing /stats/summary endpoint on EKS #300
Comments
Additional info:
Gives So I updated the config to:
Which results in So I updated the config to:
Which gives |
Hi @robertgates55! Could you try the configuration suggested in elastic/beats#10937 (comment) to see if it works for you? I don't have an EKS cluster to test on (and we don't have automated tests for it). |
So I've tried that:
and now get:
So is it that the helm chart needs to grant more permissions to the serviceaccount? |
Hi, I believe I have encountered the same issue. I think there are some missing rights indicated in the logs:
I have adapted the clusterrole to the following and do not receive error messages anymore:
Also I do now see more info in the events, eg the key "kubernetes.node._module.labels.kubernetes_io/arch" is populated. |
Thanks for all the information added here! There are indeed some resources missing and the rules are currently hardcoded. I just opened #310 which makes them configurable and adds more by default. |
Chart version:
metricbeat 7.3.2
Kubernetes version:
1.13
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
AWS EKS
Helm Version:
v2.14.3 (client & server)
helm get release
outputDescribe the bug:
I'm getting "connection refused" errors when the metricbeat module attempts to query from the /stats/summary endpoint.
Basic out of the box configuration is this:
But I've also tried various configurations/combinations
Given that the :10250 ro endpoint is marked as deprecated (and likely thus not being exposed by my EKS cluster), what is the recommended configuration to scrape these metrics?
The text was updated successfully, but these errors were encountered: