elhannaford ✭✭✭✭✭

Oddly enough, I don't like these. I would rather the "Mute Now" and "Unmanage Now" buttons to default to 24 hours, with that duration possibly settable somewhere. I *do* like the ability to mute or unmanage indefinitely, but I want it to take a bit more effort. It will be all too easy to "Mute Now", perform the maintenance…

Just to tie off this thread, I wound up having to create a custom SWQL query. After a lot of thought, experimentation, and consultation with my DBA, I figured out that I had to base the Alert on Components and perform an Inner Join between the Components table and itself so that I could check on the status of either of the…

Hi Seashore! I considered the Complex Conditions option, but I couldn't think of a way to make it work. That option seems to be designed to allow you to set up conditions on separate objects, which is not what I want. I want to trigger on a single object, an Application, based on conditions of its constituent Components. I…

In English pseudo-SQL, what I'm looking for in a trigger is: When an Application has the name "Monitor A" AND (The Component of Monitor A named "Component 1" is in status "Warning" OR The Component of Monitor A named "Component 2" is in status "Warning") AND The Component of Monitor A named "Component 3" has a value of 2

To answer my own question: SolarWinds Support finally found a KB article that addressed the problem: https://support.solarwinds.com/SuccessCenter/s/article/Truncate-the-SolarWindsOrionLog-tables?language=en_US. Granted, this addressed the problem by wiping out the entire database of Trap and Syslog records, but that was…

The Monitor that this Alert triggers from is binary, not threshold-based. What I'm trying to solve is noise from flapping between Warning and Down/Unreachable, without having false positives because of extended Unreachable events. Thanks for the warning, though!

I hadn't thought of looking at the canned alerts. While it still seems wrong, this does lend credence to your answer. Thanks!

I thought of that, and it's my second-best solution. The problem is, including those conditions in the OR would result in a false positive if (say, due to a network outage) the status went Down or Unreachable for an extended time, which is sub-optimal.

So this Reset Condition would only reset when the item that triggered the alert changed its status to "Up"? That seems wrong, but I'm willing to give it a try.

For those coming to this post for this info: the last 2 lines here are out of date. The correct syntax is: ${Node.Custom.CustomPropertyName} ${Application.Custom.CustomPropertyName} This is based on this link and on working code.

Perfect, thanks a bunch! I had no idea that you could put any kind of "isnull" function in there. That actually worried me a bit; this function solves that problem. Thanks for the help!

I think I got it. Here's what I constructed: ${SQL: SELECT Email FROM AlertConfigurationsCustomProperties WHERE AlertID = '${N=Alerting;M=AlertID}'} Anything there that looks wrong to you?

I wound up doing it the hard way, with my own code. Here are snippets of the Python code I wrote. Take them with a grain of salt; I'm a novice coder. osettings.py: ... base_url = 'https://' + server + ':' + str(port) + '/SolarWinds/InformationService/v3/Json/' query_url = base_url + 'Query' create_url = base_url + 'Create'…

I hadn't thought of licensing constraints. I hate licensing. I had considered database size, but our environment isn't big enough to challenge even a moderate SQL Server. We're using mostly SNMP for our monitoring, so I'm not too concerned about network traffic. Extra components aren't going to add that much to an SNMP…

Any advice on that custom SQL query? I'm a SQL novice, I'm afraid.

Perfect. Thanks, tdanner!

Ah, I see. Rats, I had been hoping that it would validate a proposed value against an existing custom property's restricted list of values, if it had one. Ah, well, I'll have to do without that, I suppose. Thanks for the info!

Hmm, maybe I didn't explain well. I'm not looking for a way to construct the Trigger Condition(s). I'm looking for a way to construct the email address for the Email Alert Action. I have a dozen or so different locations, each with a separate team that's responsible for their own nodes. I can construct, and, up to now, I…