Skip to content
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

graphs for cpu and other not displayed when min step set to auto #169

Open
pschonmann opened this issue Jul 26, 2024 · 7 comments
Open

graphs for cpu and other not displayed when min step set to auto #169

pschonmann opened this issue Jul 26, 2024 · 7 comments

Comments

@pschonmann
Copy link

pschonmann commented Jul 26, 2024

Hi, im scraping data from servers every 60s.
When i import dashboard in default, every metric where is [$__rate_interval] isnt displayed.
When i set min step to 1m, it works.

Would be possible to add min step as variable ?

ii grafana 11.1.2 amd64 Grafana
hi prometheus 2.24.1+ds-1+b7 amd64 Monitoring system and time series database

@CherrySuryp
Copy link

Same here.
Dashboards works just fine when time range set to "last 24 hours".
But when I'm trying to set smaller time range - "no data" error appears in every visualisation where [$__rate_interval] applied.
I fixed it by replacing [$__rate_interval] with [$__range]. But should it work like this?

24h time range applied:

telegram-cloud-photo-size-2-5348333421941875405-y

12h time range applied:

telegram-cloud-photo-size-2-5348333421941875406-y

@waldner
Copy link

waldner commented Aug 29, 2024

Same here, the workaround is also inconvenient because it requires editing a lot of panels.

@Confetti-Camouflage
Copy link

Confetti-Camouflage commented Sep 5, 2024

Make sure your datasource is configured correctly. Grafana expects the default scraping interval for Prometheus datasources to be 15s. Prometheus, however, defaults to only scraping every 1m. Changing them to both match (in my case Prometheus to 15s) fixed the graphs not showing for me.

@CherrySuryp
Copy link

CherrySuryp commented Sep 6, 2024

@Confetti-Camouflage Nope, didn't work.
I have scrape_interval: 1m set in prom config, and 1m refresh interval in Grafana. Everything's remains same :(

15s scrape interval seems to be too fast (I have about 200 servers so yeah), so it's easier to update __rate_interval to __range though.

@shaoxp
Copy link

shaoxp commented Sep 14, 2024

i met a similar problem. when use $__rate_interval, lots of panel will meet error as following.
chrome_Pj7TyZm0hl

I changed to use __range temporary to go, and it seems everything go fine. not sure whether it has potential risk for this change. please advice if you see anything. thanks.

@pschonmann
Copy link
Author

i met a similar problem. when use $__rate_interval, lots of panel will meet error as following.
I changed to use __range temporary to go, and it seems everything go fine. not sure whether it has potential risk for this change. please advice if you see anything. thanks.

Isnt problem, that you replaced "1m" with wrong syntax "1m1" somewhere ?

@CherrySuryp
Copy link

Hi everyone, I just found exactly same dashboard template that just works, you might consider switching to it.
https://grafana.com/grafana/dashboards/12486-node-exporter-full/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants