-
Notifications
You must be signed in to change notification settings - Fork 164
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
CF exporter not working anymore #493
Comments
Hi @mchabane which version of prometheus boshrelease do you have in use? |
Hello, We were in 30.1.1, and we upgraded to 30.3.0 but it did not fix the issue. |
On the VM that is running the cf_exporter can you try to reach you configured API via something like |
nc command result : We activated debug logs, and everything seems to work except "users".
|
what happens if you run
does that print some error messages? |
No error, it's very long to answer, and we are missing a lot of metrics (cf_application, cf_info ...). |
Hello, I removed "Events" filter and it's work again. But I need this filter. What could i do on my cloud foundry fondation to simulate events collector and see what is not working? |
I would expect, you need to |
Hello, cf curl /v3/audit_events/ , /v3/app_usage_events and /v3/service_usage_events works well with my admin user account. |
It also work well by curl the api with the cf_exporter client token. |
Hello @mchabane Just in case, are you using pxc-release and if so, are you using MySQL version 8.0? We have seen an impact on cloudfoundry API response times in our environments with this version of MySQL. |
Hello @gmllt, The pagination seems to be good, we have the same type of answer as an other foundation where we do not have issue. |
Hello @gmllt , |
Hello, Since some days our cf exporter does not work anymore with this error :
time="2024-07-01T13:34:50Z" level=error msg="[ 7] users error: The UAA service is currently unavailable"
time="2024-07-01T13:34:50Z" level=debug msg="[ 7] users (done, 186 sec)"
We checked our UAA and did not find anything.
The text was updated successfully, but these errors were encountered: