Thank you Sally for your reply however turning on debug may help to troubleshoot future but not past alert occurrences. Is there any possibility to verify that prometheus may have generated a delayed/incorrect alert.
On Wednesday, May 27, 2020 at 11:27:18 PM UTC-7, Sally Lehman wrote: > > Hi Kedar! What evidence do you have that the alert was triggered outside > of prometheus, and how far can you follow it back? We could start there. > > You can turn on debug logging for both prometheus and alertmanager and > that may tell you more, --log.level=debug > > Sally > On Wednesday, May 27, 2020 at 11:53:55 AM UTC-7, kedar sirshikar wrote: >> >> Hi all, >> >> We have seen an alert getting triggered couple of days ago and it got >> resolved after 5 seconds. >> >> After checking container logs & grafana screenshots, no evidence was seen >> in support of the alert which was created and resolved. >> >> System does not show any symptom relevant to the particular alert since >> last week. >> >> So wanted to know if there is anything which can be tracked from >> prometheus side to know why alert was generated? >> >> Please let me know if someone has any inputs about these kind of >> suspicious alerts. >> >> Thanks. >> > -- 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 prometheus-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/a54c52c0-212d-48b9-adf7-3dc5fc5ebe72%40googlegroups.com.
