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

What's Wrong With This Picture?

aLTeReGo

Can anyone explain to me what's wrong with the configuration of the Advanced Alert below? I mean beside being needlessly complicated. It's actually part of a larger trigger condition that worked a while back (8.5 or 8.1 I can't remember) but doesn't work now, even when I remove the rest of the conditions (as pictured below). I got caught with my pants down this week because the alert didn't trigger even though the custom MIB poller value was not "ok". Any help would be greatly appreciated. Thanks.

broken-alert.jpg

Find more posts tagged with

Accepted answers

All comments

Network_Guru

I'm not sure why you are using multiple nested conditions.
I would just use a single condition - Trigger when all the following apply.

Then list the 'not OK' and then the name of the Mib Poller.

aLTeReGo

I'm not sure why you are using multiple nested conditions.
I would just use a single condition - Trigger when all the following apply.

I understand what you're saying but this is part of a larger advanced alert that was working. I copied the alert and removed all the other conditions (pictured above) and the alert still doesn't work which is why I'm posting here looking for answers. Below is a screenshot of the original working trigger condition so you can get an idea of why I need the nested conditions.

originalalert.jpg

acherman

And who caught you in that situation? It's always embarassing when you have your pants down and someone runs in with a network issue. Hope it doesn't get on YouTube! ;-)

I agree. You should be able to get away with using a single "Trigger When [u]all[/u] of the following apply" with the two conditions underneath. Other than that I don't see why it wouldn't fire. Perhaps having the first condition match the MIB and then check it's status? Maybe try matching the Custom Poller Name instead of the MIB?

Aaron

aLTeReGo

And who caught you in that situation?

I don't wanna talk about. Let's just pretend this never happened

acherman

Okay, you posted again just before I did. I would try moving the condition of the MIB status to after the MIB matching. I guess I'm hinting that I'm not sure what order the conditions are checked? On all of your other lines you have the status check AFTER your MIB matching.

Aaron

aLTeReGo

Okay, you posted again just before I did. I would try moving the condition of the MIB status to after the MIB matching. I guess I'm hinting that I'm not sure what order the conditions are checked? On all of your other lines you have the status check AFTER your MIB matching.

Ok, I'm intrigued but how would something like that look and work? Perhaps NG could chime back in since I know he's done a fair amount with Advanced Alerts.

acherman

Also, I'm concerned that when the Trigger occurs for matching the MIB, what is the output/result? Does that show as a "status" for the next rule to match? It might suck, but it might be better to break out each MIB match like the rules below it, so the Status check isn't one level above the MIB match?

Just trying to visualize the flow in my head... Who knows, I may be way off here...

Aaron

aLTeReGo

If you can believe it, the advanced alert below doesn't work either. What now?

StillBroken.jpg

aLTeReGo

Here's the status of the custom MIB poller. As you can see the status clearly is not "ok"

MIBStatus.jpg

acherman

Grasping at straws here. I had a similar issue with monitoring input voltage and battery capacity of our UPS systems. My issue also had to do with how the Custom Poller output the MIB value.

Try this one:

Trigger Alert when [u]all[/u] of the following apply

MIB is equal to .....

field Status is not equal to value ok

Last line is a complex condition, Status is from Custom Node Pollers.

Aaron