Thanks, It definitely makes sense to upgrade the prometheus version. As per the details analyzed till now, time series DB details fetched from Prometheus using API (*curl 'http://localhost:9090/api/v1/query_range?query=docker_service_up&start=2020-05-24T07:20:00.000Z&end=2020-05-24T08:10:00.000Z&step=1s <http://localhost:9090/api/v1/query_range?query=docker_service_up&start=2020-05-24T07:20:00.000Z&end=2020-05-24T08:10:00.000Z&step=1s>'*) are not justifying alert which lasted for 5 seconds whereas same API provides TSDB records asserting alert that lasted for 15 seconds. This is where I am stuck and unable to proceed further to figure out why alert was generated even if metric values from TSDB do not match to the values used in alert expression.
Thanks, Kedar. On Tuesday, June 2, 2020 at 2:03:37 PM UTC-7, Brian Candler wrote: > > On Tuesday, 2 June 2020 21:40:53 UTC+1, kedar sirshikar wrote: >> >> Please refer below details captured from prometheus container related to >> OS/Platform. >> >> root@prometheus-hi-res-s101:/# /prometheus/prometheus --version >> >> *prometheus, version 2.3.1* (branch: HEAD, revision: >> 188ca45bd85ce843071e768d855722a9d9dabe03) >> >> > That's almost 2 years old, so I'd suggest updating to 2.18.1 in case > there's some bug fix (also lots of other performance improvements) > > Otherwise sorry - any data used to alert should also have been recorded in > the time series database. > -- 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/7428a2d5-ab75-424b-b150-42f76fb63e44o%40googlegroups.com.
