#QoS scheduling

1 messages · Page 1 of 1 (latest)

waxen herald
#

Could you share logs? It could be due to workload Zapi call taking long time and impacting next poll.

sterile plinth
quartz crest
#

@sterile plinth As per the shared log file, It doesn't seem to have any issue relate to workload and workloadDetail templates. And yes, collection happens 4 times in minute. Just to make sure Prometheus scraps at 15s interval, run this query in Prometheus and count should be exactly 4. count_over_time(node_uptime[1m])

#

From Grafana perspective, Could you check what interval it would be showing in your panel? Based on the Data point and selected time range, Grafana will decide interval. Attaching screenshot for one panel just for reference.

sterile plinth
#

Hi @quartz crest! I appreciate your comment. The interval on Grafana is set for 15 seconds but I see the counts are 1 instead of 4 in Prometheus. I feel like I am doing something wrong with Prometheus scraping. Would it be possible to share with me which config I should change to shorten the interval? I have tried adding scrape_interval on prometheus.yaml but it didn't work.

#

These are from
/opt/prometheus-scrapers/scrapers.yml
/opt/packages/harvest2/docker/prometheus/prometheus.yml

#

BTW I am using NAbox. Thanks for your help 🙂

waxen herald
#

@sterile plinth As per your prometheus configuration screenshot, scarape_interval is 1m. Adding @night garnet for NABox related things

night garnet
#

There is no way to customize scrape intervals in NAbox currently, give me some time to figure out how default interval is applied, I don't have scrape_interval anywhere in NAbox code, so I think it's just a default to 60s

#

Prom default is 1min indeed

#

so you can change it in /usr/local/nabox/files/prometheus/prometheus.yml and it should be persistent

#

Well, except during upgrades...

sterile plinth
#

@night garnet Thank you so much! It's been applied to the prometheus.