On Mon, 8 Jun 2020 at 07:41, Rajesh Reddy Nachireddi < [email protected]> wrote:
> Ok, thanks for the clarification. It is a necessary feature rather than a > good-to-have feature. > > @[email protected] <[email protected]> > As prometheus usage is getting to multiple industries, would it be > possible to consider this > https://github.com/prometheus/alertmanager/issues/204 under prometheus. > As Ben said this is a case for avg_over_time or max_over_time. Looking at just the last point would be too fragile, and once an alert fires adding additional semantics is only rearranging the deckchairs. See https://www.robustperception.io/alerting-on-gauges-in-prometheus-2-0 and https://www.robustperception.io/running-into-burning-buildings-because-the-fire-alarm-stopped Brian > > The approach you mentioned doesn't scale well in large enterprise > environments. > > On Mon, Jun 8, 2020 at 12:06 PM Brian Candler <[email protected]> wrote: > >> On 08/06/2020 07:31, Rajesh Reddy Nachireddi wrote: >> > Thanks Brian. Do we have this issue open under prometheus and with >> > examples working . >> >> >> No. Brian Brazil considers this feature unnecessary. >> >> -- Brian Brazil www.robustperception.io -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAHJKeLp%3DdqHVQSaZtZ21Q1Y7YkB8nQCad%3DNZ%2BFdxyVEEZy7B_A%40mail.gmail.com.
