Alert Escalation Throttle Auditing?
Is there somewhere logging alert throttling for the escalation chains... it's currently a tedious process to unravel what would have caused (random example: ~1623 throttle alert tickets in our ticketing system).
The throttle ticket doesn't contain any researchable information.
The Audit Log doesn't show those events.
Looking at the closed alerts didn't show the volume that would account for that quantity of throttle tickets.
Does it consider throttling in a sliding time window and alert a new throttle for every new alert at the far end of the window? If so, that would negate the purpose of the throttling once it scales past the quantity set for the throttling threshold.
Cole McDonald
Posted 1 year ago·Last reply 1 year ago
3 comments
Cole McDonald
OP1 year agoI've opened a case with support to see if I can figure out why we're throttling so much. Feels broken, but can't identify the source of the problem.
For any LM internal folks interested in it, case # is 00283679
Cole McDonald
OP1 year agoI normally view alerts with ##externalticketid## as an added column in the main alerts page and it didn't show me anything that would have created enough tickets to trigger the throttle.
Shack
·1 year agoThe only way so far I've been able to see what chain an alert made it to is by running an Alert History report and adding the column externalticketid. When I do that it will show the stage or stages involved in the alert.