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

Testing Advanced Application Alerts

andygreenough

OK this is probably a really simple one but can anyone tell me how to ensure a test of an advanced application alert chooses the correct application monitor?

I have an alert that should fire an email and run an external program but on test it is running against a different application monitor on the node even though I've specified the application name in the trigger conditions

Property Type: APM: Application

Trigger:

All

Node Status is not equal to Down

Application Name is equal to Windows DHCP Server

Any

Application Status is equal to Warning

Application Status is equal to Critical

When testing this the emails generated come from a different application monitor assigned to the same node I'm choosing as the test node. This is causing a problem with the test as I have a lot of custom properties used in the email and external program which are blank on the other monitor and therefore the test fails.

Find more posts tagged with

Accepted answers

HolyGuacamole

Yeah, the test really only checks the trigger actions but I also wanted to make sure the trigger conditions were ok. I share your HO The Alert engine is being moved to the web and completely overhauled. This may already be factored in there. Anyway, the only option is to alter the thresholds etc for a component monitor so that an actual alert is triggered for your application monitor.

All comments

HolyGuacamole

Can you post a screencap of the trigger condition. At least based on the indentation of the conditions you have listed, it is not targeting just the DHCP server.

andygreenough

Hi, thanks for the reply.

I probably didn't explain properly. The trigger is targeting an application and I'm then running the test against a node with that application assigned to it but the test is running against another application monitor on the same node almost as if it just chooses the first it comes to on that node ignoring what's in the trigger condition. I should point out that the trigger works fine if I force a "live issue" on the server by stopping a service or similar it just can't seem to be tested. There should be an application drop down on the test along with interface and volume IMO

Here's the screen shots.

HolyGuacamole

andygreenough

I thought that might be the case but wanted to ensure I wasn't missing something. Thanks!