-
Notifications
You must be signed in to change notification settings - Fork 487
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
unable to set wal_truncate_frequency (greater than scrape_frequency) #390
Comments
Hey, sorry you're running into this. Like the log message says, this is a bug (and an oversight on my part). Integrations you configure are given their own unique Prometheus config and currently don't expose changing the default |
Hi Robert, I'm not sure if this is related or not (so I didn't raise a new issue) but this is something I noticed.
If I increase the scrape_interval of job3 to anything more than 1m (eg: 2m) - then everything stops working (tcpdump shows no traffic). Thanks. |
Hmm, that's odd. Few tips for debugging that:
|
Heh, it was related after all:
I'll patiently wait until the next release - thanks a lot for your fantastic work on this! |
Hi,
I'm using: https://github.com/grafana/agent/releases/latest/download/agent-linux-amd64.zip
agent config:
results in:
Setting scrape_interval to 1m works.
Setting wal_truncate_frequency: 0s returns the expected error (must be greater than zero)
I'm not sure how I can check the wal_truncate_frequency after the agent has started (to confirm it's indeed 10m although based on the error message it doesn't appear to?).
Is there any way I can set the scrape_interval greater than 1m?
Thank you.
The text was updated successfully, but these errors were encountered: