nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

NPM Advanced Alert Issue

mcalpinj

I am trying to monitor the Application and Componant status within a Group of nodes. Below is the alert.

Trigger Alert when all of the following apply

Group Name is equal to Exchanhge

Node Status is not equal to down

Trigger Alert when any of the following apply

Application Status is not equal to Up

Componant Status is not equal to Up

Looks simple enough. But it won't save. I either get an error that says that "Please specify a complete Trigger Condition Field not specified or invalid". Or, it actually changes the first condition to "IOS Image is equal to Exchange" when it's saved.

Since, when it actually changed part of the Condition for me (thanks <grin>), I am going to guess that it doesn't like joining "Type of Property to Monitor" groups together. In my case I take conditions from the Group Member and APM: Componant. Is there a way to do this without using a custom field? I'd like to use the groups that I've already implemented.

Thanks, John

Find more posts tagged with

Accepted answers

All comments

macnugetz

John,

We moved your post to the Alert Lab. Our resident Alert expert (Andy) suggested the following:

The line “node status not equal to down” is unnecessary since there is a implicit dependency that implements that. Remove that line and try again.

HTH,

Craig

mcalpinj

Removing the Node Status condition did not help. I am still getting the error. Thanks for the note though. aybe the Alert group can help. John

mcbridea

Can you post a screen shot of the alert trigger?

mcalpinj

Thanks for looking into it... John