-
Notifications
You must be signed in to change notification settings - Fork 6
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
alias not matching prometheus #5
Comments
Hi @Adel-Magebinary, There could be many reasons for this. I have a few questions:
|
Hi Isaac, Are other Joyent-specific queries working properly? No. regular expression somehow not matching with sapi. or instances. Once I remove the . in the alias regular express, everything shows up. Is your sapi service running and healthy? Yes. sdc-healthcheck and curl test all pass. Do the prometheus logs show any errors? I haven't checked my log file. But I don't think prometheus is throwing any error. Will check this soon. Do the grafana logs show any errors? No errors. Looks like prometheus query with alias doesn't return anything but success status. Does this error show up when the query is executed from the prometheus interface itself, or only In both. There was no error but just can't find the report data. What does your Prometheus config file look like? global: scrape_timeout is set to the global default 10sNote: you can create multiple stanzas starting with "job_name"scrape_configs:
|
This all looks good. Let me know if you find anything in the prometheus logs. I do have one question - what is the alias of your sapi service? The regex expects the aliases to be numbered - sapi0, sapi1, etc. I am curious if yours is just named "sapi" - this would explain why the data shows up when you delete the dot in the regex. |
Hello Isaac, It's sapi0. It's just not regx matching it. Will check Prometheus logs shortly. Cheers, |
Hello Isaac, What is your grafana version? |
I'm currently running 5.3.2. |
rate(net_agg_bytes_in{alias=~"sapi."}[5m]) is not matching anything for me atm?
Is this because of my Prometheus version?
Cheers,
Adel.
The text was updated successfully, but these errors were encountered: