beastroy

Thanks for posting this information, exactly what I needed! I would also like to see this implemented as a feature in Solarwinds. I'd like to add that I had to change up the join conditions in order to prevent multiple alerts: JOIN [dbo].[NPM_SwitchStackMember] ss ON ss.NodeID = nodes.NodeID JOIN…

Netflow is cool I'm no good at Flowetry This helpful tool Doesn't help me with Poetry

No luck for us, instead we had to include the credentials within the script.

I had previously opened Case #1119743 in regards to this issue. The first time I tested the action after following the steps provided by customer support, the action executed successfully. However, the action is now failing with the same error message again. I have confirmed the service is still running under the Local…

We are currently running the Solarwinds Orion Module Engine service under "Local System", which to my understanding includes the SID's of NT_AUTHORITY\SYSTEM and Builtin\Administrators. I have added Builtin\Administrators to the Local Security Policy for "Replace a process level token". (The error message I was receiving…

NPM 12.0.1/SAM 6.3.0

Erik, Looks like you are experiencing issues with negotiating TLS. Which version of SAM are you currently running? Thanks, Troy

Thanks so much tomas.vrabel​! This information was very helpful. I was able to accomplish this in PowerShell using the following code: $coreNodeID = Get-SwisData $swis "SELECT NodeId FROM Cirrus.Nodes WHERE CoreNodeId=$nodeID" Invoke-SwisVerb $swis Cirrus.Nodes RemoveNode $coreNodeID Thank you for your help!!

Does this still work? I'm only seeing the custom property as plain text.

Thanks for the suggestion, we'll modify our query and use this method moving forward.

I have a similar situation in which we would like to use the function as designed.

Enable debug logging on the application monitor with the HTTPS Monitor. Once you've enabled logging, let the test run a few times (you can also test the component if you do not want to wait for the polling cycles). After the test has run, note the Application Monitor ID and log into the polling engine for the node that the…

aLTeReGo​ Thanks for the response. In our case, in the AlertDefinitionsView table the "TriggerQuery" field is null for all of our alerts. I had to use the following query to successfully find all of the alerts using a custom property: SELECT * FROM [AlertConfigurations] WHERE [Trigger] LIKE '%custom property%'

Thanks for the great information mesverrum​ & Seashore​!!

Thanks again tomas.vrabel​! We are using PowerShell and I was able to accomplish this using the following code: $topologyURI = Get-SwisData $swis "SELECT Uri FROM Orion.Pollers WHERE PollerType LIKE '%Topology%' AND NetObjectID=@nodeID" @{ nodeID =$nodeID} Set-SwisObject -SwisConnection $swis -Uri $topologyURI -Properties…

I've noticed whenever we add the node via the API Discovery, the node is also being managed by NCM. Is there a way to unmanage the node from NCM either during the discovery or after it is added? -Troy

Thanks for the information and quick response nick_scott​, tomas.vrabel​ !! This is extremely helpful!!

Hey Steven, Thanks for the quick response. This turned out to be a case-sensitive issue. The rows in the database looks as follows for a node that was manually silenced: 8342 swis://SERVER/Orion/Orion.Nodes/NodeID=3637 2019-04-25 19:20:00.000 2019-06-26 19:20:00.000 8343 swis://SERVER/Orion/Orion.Nodes/NodeID=3638…

FYI... This error still exists in SAM 6.4. We are periodically receiving the error message "Unexpected error occurred. The request was aborted: Could not create SSL/TLS secure channel" on a few HTTPS Monitors. The issue appears to be fixed in SAM 6.4 HF1, which was released on April 18th, 2017. Below are the hotfix details…

aLTeReGo​ Has the table for the alert definitions changed? It appears the alert definitions are now in the "AlertConfigurations" table.

I have this same question. Did anyone find a solution for this?

nick_scott​, tdanner​ Thank you for this post! This information has been extremely helpful! I'm not sure if this has been answered somewhere else, but do you have any recommendations on how to accomplish the following: * Remove "Topology: Layer 3" from the monitored resources (this resource is selected by default) * Modify…

I'm experiencing this same issue. Have you found a solution for this? Thanks, Troy

Hi ccousineau​, Are you able to share any of the responses you've received? I would also like to gain insight into how other people are monitoring their Azure environments.