ioan_bucsa ✭✭✭✭✭

Very briefly: Basically all the resources for a node are pollers. To list pollers assigned to a specific node: $currentPollers = Get-SwisData $swis -Query 'SELECT PollerId,PollerType,Enabled FROM Orion.Pollers WHERE NetObjectId=@n' -Parameters @{n= $NodeID} And to assign pollers for a node the code is: $poller = @{…

Deduplication should resolve the duplicate result, but I would advise you do some testing so that you do not end up with multiple alerts for the same issue.

I'm not that familiar with python, but the SDK wiki provides examples in PowerShell (what you are looking for is Create new subnet for Hierarchy group): https://github.com/solarwinds/OrionSDK/wiki/IPAM-2019.4-and-higher-versions-API 

You just need to make sure that the certificate is applied to each web server and to the load balancer as well. We are running a similar setup without any issue: HA, 1 AWS, a VIP that contains the two main polling engine and the AWS that uses port 17777 to determine which server is currently active and the certificate is…

Are you generating the JSON from code? If so, you could replace the '\' in the drive variable with '\\' in order to escape it before constructing the JSON.

NPM/Orion cannot do that out of the box. You would need to make use of the API and/or some custom scripting.

@"ashley.orr" If it's not too late, sign me up as well!

Depends on how many rows you would like to generate. You could use multiple SUBSTRING expressions if the complexity not that high.

You can do that from the UI without SQL. I'm curious as to why you would require a SQL trigger...

Not really sure that some these are to be directed at the developer, but rather at the development/product team. Here goes: - Why is it that you cannot assign your own API Poller templates to nodes (rather it is just out-of-the box templates)? - Could we please make error messages more intuitive/informative? Today I got…

VNQM can help you with that and much more (IPSLA, CDRs, call statistics etc.).

You could create a discovery job via the API and then set custom properties, pollers, resources afterwards. I started working on something similar a while ago but did not get the chance to finish it.

@"houston" This stylesheet contains the definitions for the icons : <link rel="stylesheet" href="">cdnjs.cloudflare.com/.../font-awesome.min.css"> Make sure that your browser is not blocking the URL. 

This is the error I am seeing in Orion.Web.log when running the query: It's odd that SWQL queries work differently from Studio than from the web application. I always tested my queries in SWQL Studio first and was under the impression that the back-end mechanism is identical.

I'm not really familiar with Python, but I created a Powershell script based on the solution @"mesverrum" provided here : https://thwack.solarwinds.com/t5/Systems-Management-Discussions/Create-Groups-using-SQL/m-p/275531 Might help.

The proper syntax for the Invoke-Verb statements would be the following: Invoke-SwisVerb $swis Orion.Nodes Unmanage @("N:$nodeId", $now, $later, "false") (exactly how you have used it) Invoke-SwisVerb $swis Orion.Nodes Remanage @("N: $nodeid ") (no need for other parameters besides NodeId; also, no need for Set-SwisObject…

You would definitely need a custom SQL/SWQL trigger. Off the top of my head it would be on the Nodes table joining the AlertHistory table and then you evaluate the COUNT(alerts) and filter by ActionID to only pick up the alert trigger. 

A Powershell monitor could be a bit more flexible. 

In order to investigate application errors you would need SAM (or DPA to deep-dive into the inner workings of SQL Server). NTA & NPM are really not the proper tools for the job. 

It could be that your alert is set up to be triggered X minutes after the node went down (i.e. the 'Node stopped responding event') and the node does not remain down long enough to meet the requirement. Check your alert definition (trigger condition) and the event history (node up/down events and the time between…

A possible solution would be to duplicate the default Node details summary view and edit that (add/remove tabs and widgets).

@"keegen" Are you running 2020.2? I haven't upgrade yet and it runs on 2019.4 without any issues. Maybe check the browser debug console to see the error message that you are getting.

@"KMSigma.SWI" I was on the Virtual SWUG the other day and I thought this was very cool. I started working on it right after the session was over and then bumped onto your post when trying to figure out why my css was not being interpreted properly Long story short: 

I was very excited about the template API pollers, but then I noticed that you cannot assign the pollers that you have created, just out of the box ones. Is this intended behavior or is it some sort of bug? Just a few weeks ago I had to go through the pain of creating an API poller with 24 metrics and then replicating it…

Don't believe that is quite possible... Are you interested in displaying something outside the Orion DB? I'm trying to understand your use-case to see why an equivalent SWQL query would not be suitable. 

You should be seeing NetFlow coming from all interfaces that have it enabled. The newer NetFlow sources view will show you all interfaces that are discovered on a node, but only the ones sending NetFlow are marked as Enabled and have a "Last received" timestamp.

If I understand correctly you are alerting on node statuses including 'Critical'. Like @"mesverrum" pointed out, node status is affected by the statuses of all its child objects. My recommendation is that you fine-tune the alerts and trigger on hardware sensors, interface utilization or resource utilization (CPU, memory,…

@"Deltona" Code is attached. Just paste it in a Custom HTML widget and you should be go.

Cool stuff. You could probably get a widget looking pretty much identical to the default Node details by using a Custom HTML + CSS + AJAX + SWQL. Will post the code if I get around to working on it.

Tried this in NPM 12 and it does not seem to work.