-
Notifications
You must be signed in to change notification settings - Fork 811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metrics for EBS CSI Controller is not available #1993
Comments
Hi @ujala-singh I was unable to reproduce this in a similar environment. Could you run through the steps below to check if the metrics endpoint is accessible within the container?
Here is an example of the expected output:
|
Thanks @torredil ! |
I am also seeing this, I have used the debug to access the pod, and / $ wget -O - http://localhost:3301/metrics
Connecting to localhost:3301 (127.0.0.1:3301) So does not return anything, I cannot see any errors in the logs. Not sure where else to look.... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I am using EBS CSI Drivers as an add-on from AWS EKS Clusters. Somehow by providing some custom values, I am able to expose the port 3301 and metrics endpoint, but while scraping it doesn't give any metrics.
What you expected to happen?
I would expect, it should return all of the metrics which are exposed by the application.
Anything else we need to know?:
Added one arg to
ebs-plugin
conatiner:--http-endpoint=0.0.0.0:3301
and exposed the port:Later created the service and serviceMonitor for the same as mentioned [here]:
Vmagent is able to discover the target but there are no metrics available.
Environment
Logs
Debugging
Curl Request is not giving any metrics.
The text was updated successfully, but these errors were encountered: