Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Alert issue

dquerry

Can anyone help me with this alert? It was working fine on Friday, but now nothing.

Trigger Alert when all of the following apply

Node Name is equal to mynode

Trigger Alert when any of the following apply

Node Status is equal to down

Node Status is equal to Warning

Node Status is equal to Unknown

Application Status is equal to down

Trigger Alert when any of the following apply

Percent Memory availae is less than or equal to 80

CPU Load is greater than or equal to 80

I turned the server off and increased the ram and CPU usage above those measures and this alert did not trigger. Any help would be greatly appreciated.

Find more posts tagged with

Accepted answers

cgregors

I always like examining the sql that the trigger condition created. I've reproduced your trigger condition and this is the sql:

SELECT
    DISTINCT APM_ApplicationAlertsData.ID AS NetObjectID,
    APM_ApplicationAlertsData.Name AS Name
FROM
    Nodes INNER JOIN APM_ApplicationAlertsData
    ON
        (Nodes.NodeID = APM_ApplicationAlertsData.NodeID)
WHERE
(
    (Nodes.Caption = 'mynode') AND
    (
        (Nodes.Status = '2') OR
        (Nodes.Status = '3') OR
        (Nodes.Status = '0') OR
        (APM_ApplicationAlertsData.Availability = 'Down') OR
        (
            (
                (100-NullIf(PercentMemoryUsed,-2)) >= 80) OR
                (Nodes.CPULoad >= 80)
            )
        )
)

Sometimes reading the sql helps in understanding why an alert doesn't trigger.

All comments

byrona

Which server was turned off, your Orion server or the server that you are monitoring?

If this was working before and you haven't changed the alert at all, then it should still work exactly the same as it did before. Are other alerts working properly?

Have you verified that all of your Orion services are running? Try restarting your Orion services if necessary.

dquerry

I turned off the server that I am monitoring. Solarwinds says that the server is down but, it does not trigger any alerts. All of my other alerts are working fine and my Orion serveces are running.

FormerMember

Hasn't this created an 'And' statement rather than an 'Or' so it would only trigger if the server was Down and CPU Load is greater than or equal to 80% ??

dquerry

Doesnt the 'Trigger Alert when all of the following apply' only apply to Node Name is equal to mynode? Then the rest is in an Or statement. It needs to be set up to ware it only triggers if Node Name is equal to mynode and if any of the other conditions happen it triggers.

cgregors

I always like examining the sql that the trigger condition created. I've reproduced your trigger condition and this is the sql:

Sometimes reading the sql helps in understanding why an alert doesn't trigger.

cdoyle

Hi dquerry,

It might help to break this alert up a little, as it seems you are trying to alert on a lot of different conditions here. Also, check if this alert has already been triggered off - with so many objects being monitored in it, it could have been triggered a while back on a different condition to CPU or memory. An alert will only trigger once - in order for it to trigger again, it has to have reset first.

The first thing I would do is split the 'Application Status is equal to Down" into its own alert, and set the "type of property to monitor" for that alert to "APM: Application". This could cause you problems if the type of property to monitor for this alert is set to node, as that condition wouldn't be possible to evaluate properly.

The rest of the trigger condition looks OK, but again, it might help to break it up further.. For example, if your alert has triggered because the device's CPU has gone above 20%, then you wouldn't get a second alert if the device were to go down.

Also, check if there's a supression condition added, as an incorrectly configured supression condition could block the alert from ever triggering.

Petr.Vilem

Are you using simple reset condition (Reset when trigger conditions are no longer true), or manually composed one? I think that simple reset condition will not work in this case.

I would try something like this as reset condition:

Node Name is equal to mynode

Trigger Alert when all of the following apply

Node Status is not equal to down

Node Status is not equal to Warning

Node Status is not equal to Unknown

Application Status is not equal to down

Trigger Alert when all of the following apply

Percent Memory availae is greater than 80

CPU Load is less than 80