Alin Sinpalean

Well, that's pretty much what it does. Except it asks for 5m extra instead of 50% extra. The reason for that is that 5m is a "magical" constant for how...

@brian-brazil is right to point out that reset handling and aggregation could not possibly be handled in Grafana, because the query output is presumably already aggregated -- e.g. `sum by(job)...

[I was considering posting this as a comment on the Grafana issue, but figured the poor Grafana devs shouldn't have to deal with this. I'm also honestly not trying to...

Happy to hear that. And happy to provide whatever input is useful to make a decision. As I see it, the reason why the interval used by `rate` should behave...

Leaving aside the exact implementation details (how far back to look for a sample; interpolate vs. take the exact sample value; and so on) I still believe `xrate()` is the...

> V2 certainly seems to be wrong to me Well, there is no right solution, I'm afraid. If you look at [the graphs I've linked](https://free.github.io/xrate/index.html) V1 has the [worst behavior](https://free.github.io/xrate/Grafana%20-%20xrate%20-%20no%20range%20adjust%2C%20smooth%20counter%2C%20series%20start.png)...

Thanks for the heads-up. Because you had created the document I didn't get any notifications. I've changed it to send me notifications on all comments now.

Per [the documentation](https://github.com/prometheus-community/jiralert#alertmanager-configuration), the webhook endpoint is `/alert`, not `/alerts`.

I fully understand if this is not accepted as is, but I'd like to point out that AFAICT no one is going to be creating thousands upon thousands of metrics,...

Hey Dave, Your proposal sounds very enticing indeed. If you want to help maintaining a fork then it sounds like a plan. I have no idea how many people will...