[Eric Wright]

I don’t remember if I’ve tried in the past to use an error state only alert.  The error state doesn’t happen very often, seems like it only occurs when we have an issue resolving a DNS name.  I could try that.  Seems odd that the rest of the states work on the existing alerts though.

The difference between the all and any is that I’ve got a bunch of threads on the same alert and I want to track if any of them get into the error state for more than 15 minutes.

[Eric Wright]

The alert has been in place for at minimum a few months.  Works for the other statuses, sends the email without issue.  The only status that its having an issue with is the error status.

[Eric Wright]

Attachment attempt number 2

Attachments:

You must be logged in to view attached files.

[Eric Wright]

I hate to hijack the thread, but here is a slimmed down version of the alert.  This alert is working for the down/opening status but not the error status.

[Eric Wright]

Did changing the alert type fix the issue for you?  I’m having the exact same issue in our engine.  I have multiple protocol alerts setup which are working completely fine…except when the thread is in an error status.  We’re currently on version 6.2.1, going to be upgrading to 20.1.1 tonight.  Not sure if that upgrade will fix the issue or if this is something that is happening in multiple versions.

[Author]

Replies