mrxinu

It's inconsistent, but when you're filtering a resource you need to use nodes, plural. If you're using the variable in an alert it's node singular. ${node.contact_email} works, where ${nodes.contact_email} does not.

Clever.

That's what he started with and I came back with "BUT YOU COULD PAY HUNDREDS FOR THIS PLUGIN" (only without obnoxious caps like that). I just installed the tftp client feature and now I'm just redoing his code in PowerShell so we're not having the issue with the impersonation. So, definitely a good idea. =)

Actually that might need to be False or the meaning of the custom property flipped, depending on what you intend. I don't know if you have nodes that you're trying to remove from a node down alert or if you're adding nodes one at a time that need to have the alert sent when they go down.

I tried that too, both c:\script.bat locally as well as on the remote system via psexec. Both failed. =\

I like the idea, but the challenge is going to be maintaining it. When you add a new node, you're given the opportunity to go through the custom properties and give them values. The interface custom properties don't get that kind of attention unless you're logging into the machine and running the Custom Property Manager. I…

It sounds like you need to work with the ServiceNow API more than the SolarWinds API. On the SolarWinds side you just need to keep track of what nodes existed previously and what nodes exist on the next check. When there are more, you have to do the work in ServiceNow. What kind of development are you prepared to do? What…

If you get all four key/value pairs in there it definitely works as advertised:

I was scrolling down and thought "oh I have a query for that!" and then @"dan_jagnow" got it already. 

Uh oh, that's not good. What exception are you getting? What's the inner exception?

You could run it from any system that has access to that path. It would give you the total number of new files. In ipMonitor, I have no idea. I write these scripts for SolarWinds's Server & Application Monitor product.

As you have it, your interface alert will never trigger as long as any node is down. The condition in the Alert Suppression tab will be tested against all nodes in NPM, not just the one that triggered this alert. Remove it from the Alert Suppression tab and add it to the Trigger Condition tab and it'll work great. Agreed.…

Nice one! Thanks for updating the thread with the results.

Nice - worked like a charm. Why does it take time to update on the website? You'd think an old-fashioned shift-refresh would do the trick.

Perfect. Now, the emails you're getting. Are they all coming at the same time? How many are you getting? Are there any differences between them (i.e., trigger verbiage vs. reset verbiage)?

You're very welcome.

Agreed. There are some mysterious joins to the traps & syslog tables during the normal course of using the web console that grind to a halt when there are too many rows there. Going another route with kiwi is definitely the way to go.

I say fork the SolarWinds repo and add a PHP folder to the Samples - I'd contribute too. OrionSDK/Samples at master · solarwinds/OrionSDK · GitHub

Each alert action can have its own delay so you should only need a single alert. If I'm reading this right, you have 3 separate alerts with delays on the trigger conditions?

At that point your options are stashing them on the server somewhere so the script can access them (there are some clever/secure ways we could do this) or pass them as additional arguments on the component argument field alongside the binary path and database name. Is either option palatable? -- Steven W. Klassen…

You don't need that additional join to AlertStatus to get the Acnkowledged state - that's in the AlertActive table. Adjust your query like this: SELECT ao.AlertObjectID,I.InterfaceName,ac.AlertMessage as Message,ao.RelatedNodeCaption as Node,ao.AlertID as AlertID from Orion.NPM.Interfaces I inner join Orion.AlertObjects ao…

Ah, yeah, great point. It's always good be explicit and use 'AS' when you alias. If you don't it definitely can confuse folx.

My apologies. The answer is no.

That's close. You've got the application down alert. You want the component warning/critical alert. -- Steven W. Klassen Programmer Analyst @ Loop1 Systems http://www.loop1systems.com/ http://www.linkedin.com/in/mrxinu

What script did you run?

There would be an hour's worth of development involved if you got a hold of someone with some scripting savvy, but XMPP definitely doesn't fall under "not an option."

Hm, I would have thought it would have resolved the custom poller to its associated node before trying to run that action but apparently not. The only other alternative I can think of would be to have a PowerShell script that effects that change in the node's status but I don't believe that would have the same…

You're running the test in the advanced alert manager? You won't have any previous value that way - you'd need to have it actually trigger against a change in order for ${IOSImage-Previous} to hand you something.

AH, notepager the company, not notepager the software. I misread what you said. =)

Are you using Python or would another language be more convenient?