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.

Only active Alert report

Is it possible to have a report that only shows ACTIVE alerts?

We use NPM for two distinct purposes. One to Alert, the other to monitor.

I have a report that shows active EVENTS, but this is a little misleading in that it shows monitors that maybe critical but for which we have not configured an Alert.

It would be great to get to see just those monitors that have current Alerts.

Everything I have tried so far just either shows events history or alerts that have already been cleared.

Thanks!

  • This bit of SQL should get you that information:

    Select AlertStatus.ObjectName as Object, AlertDefinitions.AlertName as Alert, AlertStatus.TriggerTimeStamp as Date_Triggered

    From AlertStatus

    JOIN AlertDefinitions on AlertStatus.AlertDefID = AlertDefinitions.AlertDefID

    Regards,

    Matthew Harvey

    Loop1 Systems

  • Thanks Matthew

    I found a query that did a similar thing - but the report still shows alerts that are no longer current. It is still a history report.

    I am trying to get a report of alerts that have not reset, where the alert condition is still current

  • The Alerts view under the HOME tab shows the Active Alerts by default (i.e., alerts that have not been reset). If you want this as a report, there is also an out of the box resource to choose from in the Web Reporter.

    Core-Active-Alerts.png

  • You would find them on Advanced Alert Manager as well

    AA.JPG

  • thanks Vinay BY and HolyGuacamole

    I had found those reports earlier - they are similar to the one that mharvey suggested.

    They only list Alerts that have triggered, including historical alert triggers.

    I am trying to get a snapshot of those alerts that are CURRENTLY triggered - in other words only the alerts that have not reset.

  • I am absolutely positive the Active Alerts are the ones that have been triggered but not reset. Can you provide an example of why you think otherwise? I am beginning to suspect the Reset condition in your Alerts may not be properly defined, and hence the alerts are staying active.

  • thanks again

    The alerts do have a reset and are sending the reset email etc.

    I think my issue is that SW does not have an auto acknowledge that is stopping me getting what I need.

    Really what I need is some way of distinguishing between those monitors I want to be used for alerts and those monitors I am using for diagnostic purposes.

    To that end we are adding a custom property to make that distinction and filtering on that.

    In the end its the monitors that trigger the alerts that I want to see, but without some way of finding out which monitors have alerts its difficult to do.

  • If you are receiving Reset emails, etc - then the alerts are working as expected. Also, the Alerts view is definitely a list of alerts that are triggered but not reset.

    Now, this is a slightly different discussion

    Really what I need is some way of distinguishing between those monitors I want to be used for alerts and those monitors I am using for diagnostic purposes.


    Can you provide an example or two? Maybe a screenshot of an active Alert in the Alerts view, and what you expect / what you do not expect to see? Where exactly have you used the custom property? Screenshots would really help.

  • I am resetting my expectations instead emoticons_happy.png

    We are using SW for two purposes

    One for giving a monitoring status and diagnostic view of the environment

    The other is alerting us when things go wrong

    We are looking at using custom properties to filter out the alerts and monitors we want to see alerts for etc.

    Really the purpose of this is to get to a way of providing useful management overview of systems, but also letting us maintain meaningful diagnostic information as well as differentiating between production and test/dev for devices/nodes/monitors/alerts etc

    .

  • I suggest you take a look at this

    TIPS & TRICKS: Stop the madness! Avoiding alerts but continuing to pull statistics.

    The strategy outlined works very well for your use cases as well.