-
Notifications
You must be signed in to change notification settings - Fork 103
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
Add metrics for workers. #21
Conversation
@pvdvreede thanks for the PR. We don't have CF workers in our setup so it's hard for me to actually test this out. |
@pvdvreede Oh, and more thing. Could you update the readme to reflect the changes you've made. Especially the list of metrics. |
yep, will update things, clean it up and rebase soon, thanks! |
Hey @pvdvreede! Thanks for your contribution. I was indeed able to fetch the correct data from the several accounts I'm having attached to the token I did use to test this one. The result is the following:
As @martinhaus mentioned, it would be nice to update the readme by adding the new counters you've added. Good job! |
Beat me to it @pvdvreede ! This is super useful 🧁 I just tested to build and run this container, but I see nothing related to workers in
I have tried with just the EDIT: actually, nothing related to Cloudflare at all, am I looking at the metrics for the exporter container itself? |
Seems to work only when I use the Global API key, not at all when I use a token scoped over @nouvellonsteph could you elaborate on how you setup the correct token? |
This actions issue #17 .
The functionality is there and will introspect the accounts the CF TOKEN has access to and then get worker metrics from there.
Not sure if this is the wanted behaviour as the token will need extra permissions (which i will update the readme with once things are looking good :) ).
Should I add a
CF_ACCOUNTS
env var to limit accounts to check? If the var does not exists it will not get any worker metrics, so its backward compatible?