-
Notifications
You must be signed in to change notification settings - Fork 128
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
Promxy uses /api/v1/series for ALERTS_FOR_STATE #650
Comments
Thanks for opening an issue! I spent some time attempting to reproduce the error you are describing but I am unable to do so. When I run locally using the demo_robust.conf configuration and the I did some digging and I also can't see how a backfill query would hit the So at this point I am unable to reproduce your reported issue; if you could provide more detail so that I can reproduce the issue; or some additional logs/errors/etc. that would go a long way towards getting a repro case. |
Hi, the issue is occurring when rules.alertbackfill option is not specified. |
AH; that makes a lot more sense :) So I don't believe the issue is anything to do with the return value -- but everything to do with the query. Prometheus' restore query is VERY particular -- and it expects the labels to be exactly as it would generate them. If you enable IMO prometheus' query is being too strict -- but thats what it does. So I'd suggest checking if that is the case -- and seeing if you can adjust your configuration to make that align. If not; I am definitely open to suggestons on how to best make that work (I don't think I know any users that rely on the |
As its been a few months with no response I'm going to close this out (assuming it is abandoned). If this is still an issue please feel free to re-open! |
Hi!
Looks like restoring alert's state feature dosn't work.
Promxy uses /api/v1/series for ALERTS_FOR_STATE it can't restore alert's state because result from /api/v1/series contains no timestamp.
Tested on most recent versions and current master with prometheus and victoriametrics as backends.
The text was updated successfully, but these errors were encountered: