You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2022. It is now read-only.
with a condition of x number of message in the last 5 mins to trigger a pagerduty alert, the link in pagerduty is created with a relative timeframe resulting in the wrong logs shown. In other words, it shows the logs from the last 5 mins when I click on the link instead of when the incident was raised
i think the correct behaviour should be an absolute timeframe which trigger the condition so that even when the incident is view one hour later, the timeframe for the logs will still be correct
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
with a condition of x number of message in the last 5 mins to trigger a pagerduty alert, the link in pagerduty is created with a relative timeframe resulting in the wrong logs shown. In other words, it shows the logs from the last 5 mins when I click on the link instead of when the incident was raised
i think the correct behaviour should be an absolute timeframe which trigger the condition so that even when the incident is view one hour later, the timeframe for the logs will still be correct
The text was updated successfully, but these errors were encountered: