This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Alert Reset Actions not firing

It seems that when an alert fires, it is not firing off the reset actions. The action gets triggered and the triggered action fires. Once the reset condition happens, the alert resets, but no action fires.

I have tried this with the built in alerts and i have created an alert from scratch. Before I place a ticket, anyone have ideas on what else I could do?

Parents
  • It's probably *not* this, but it could be some issue with Orion trying to send the email (email recipients not existing in email system you are sending to, address formatting issue, some sort of block on the email side, etc.).  You can look for failed email alerts with the MS SQL query example below (If you're comfortable querying the Orion database directly). The error is in  "'Message" column of the query,  I'm using NPM 11.0.1 so it will probably work against the 11.x versions.

    SELECT TOP 100 [MsgID]

          ,[LogDateTime]

          ,[AlertDefID]

          ,[ObjectType]

          ,[ObjectID]

          ,[ObjectName]

          ,[ActionType]

          ,[Message]

      FROM [SolarWindsOrion].[dbo].[AlertLog]

      where message like 'Failed%'

  • I ran it and didn't pull up anything from this year.

Reply Children
  • The only other gotcha I can think of is if you are using the "Test" button to test the alerting.  This button is not to actually test alerting as its more of a "test to make sure the trigger condition and SMTP server are working" and not much else.

    If you are *not* using this button and letting Orion itself trigger the alerting, then I'd say it's in the alert rule configuration or you've found a bug/condition within Orion itself.

    If you hit the "Export" button on the rule and post the *.AlertDefinition" file as file attachment to this post (as some others above have suggested) then the alert rule can be examined/imported by others and the issue might be found.  If you do this you will be exposing any IP addresses/email addresses/hostnames, etc. defined  in the rule.  It's a small XML file so you could remove that info from the file by hand.