Comments
-
done! Understanding which alerts and nodes are the noisiest and general alert config best practice - Reports - The Orion Platform - THWACK (solarwinds.com)
-
Glad to hear!
-
@"rmeskill", I thought I updated the attached alert file a few months ago but when I downloaded a copy i didn't see my changes in there. I reattached the alert file (file name includes a date stamp). Try importing that alert and see if that fixes any issues that you're having.
-
@"jastake", the formatting would allow me to test it on my end.
-
If you test out the Support article link using PowerShell, does it work? I typically get my API examples from SolarWinds Github site as I've seen those get updated while the support articles tend the lag behind. This is the direct link. OrionSDK/ImportListResources.ps1 at master · solarwinds/OrionSDK · GitHub That would at…
-
That's odd. I would open a support case then and see why the PaloAltoHAState custom property is not populating in the Orion.NodesCustomProperty entity/table.
-
On your Manage Custom Properties page, is the PaloAltoHAState property set to an object type of 'Nodes' with all of the check boxes selected under usage?
-
Nope, nothing needs to be done with the customer property after it is created. Since you're using SWQL Studio, if you find Orion.NodesCustomProperties, right click and 'Generate Select Statement' and then execute the query, do you see the PaloAltoHAState as a column in there?
-
Yes, exactly what i'm talking about. The error Entity Orion.NodesCustomProperties does not contain requested property PaloAltoHAState of navigation property Nodes.CustomProperties." is from SWQL saying the Custom Property doesn't exist. So I would double check it was created correctly. What do you see on your Manage Custom…
-
@"smsegin72", that sounds like you're missing the Custom Property that the alert is using. I would check if a Node Custom Property of PaloAltoHAState (text based) exists.
-
Just fixed the issue and re-uploaded the alert file. The only thing that changed was the Alert Trigger action when changing the custom property.
-
very cool, thanks for the update @"Vinx"
-
There is a requirement to restart all of the Orion services after the ParentID changes in IPAM. Silly but that is what I've found to work. I created this script that i've used to update parentId…
-
The is a requirement to restart all of the Orion services after the ParentID changes in IPAM. Silly but that is what I've found to work. I created this script that i've used to update parentId…
-
Haven't tried going the agent route but there are a handful of other verbs associated with Orion Agents in Orion.AgentManagement.Agent. My Guess you you might have to do a combo of a few APIs calls.
-
Is this request simply for a single user or is this all users? SAM does have the ability to execute PowerShell scripts, though that is not the route that I would take. I would make sure you have sufficient audit levels in place enforced through GPOs first. You want that login event stored in the Windows Event Log. SAM does…
-
So, to answer this we need to first know how IPAM hostname resolution works. https://support.solarwinds.com/SuccessCenter/s/article/How-hostname-resolution-works-in-IPAM?language=en_US IPAM relies 100% on your DNS server to populate the hostname field. So while you can't directly edit the hostname via the API, you can…
-
What you'll want to do is use the Server and Application Monitor (SAM) to monitor URLs. The screenshot you posted shows that the node is already in Orion. Assuming you own SAM, go to Settings > All Settings > SAM Settings > Manage Templates Search for HTTPS and check the box next to "HTTPS Monitor" and click the "Copy"…
-
I've actually asked this same question and unfortunately it is a feature request. The work-around that I had to do, albeit ugly, is to manually edit the subtitle that references which color is for what.
-
There isn't a way to do this that I am aware of. However, something like that would be a really good feature request. Each widget does have an option for a URL link but that has to be statically defined and only 1 URL is allowed.
-
Is it possible to show a screenshot of the full component monitor configuration page? It would be helpful what parameters are being passed into the script. Also, if you copy the contents of the script and run it locally on your linux server (passing in the necessary parameters) does it behave the same? Last, is it possible…
-
Easiest way is to use the SAM Component Monitor Wizard. https://documentation.solarwinds.com/en/success_center/sam/content/sam-use-the-component-monitor-wizard-in-sam.htm Or you can manually add the "Process Monitor" to a template and define the Process Name you wish to monitor.…
-
So short answer is yes, this can be done in SAM. However, you would have to loop through the users and then covert the array of locked out users into a single comma separated string. The SAM PowerShell component monitor would allow for a numeric count of locked out users followed with a single string output message.
-
Well I'll be, great find!
-
The message data is not stored historically, unfortunately. You would have to create an alert and include the statistic and message data as alert variables. An alert action of NetPerfMon could do it as it would show in the event/message center, or sending an email out. Downside is the alert would only trigger when…
-
So if the SAM Template is set to 'Agentless' then Orion will use the ODBC settings on the Orion server. If the template is set to 'agent' then the component monitor is executed on the remote node. You would have to setup the ODBC there for it to work. This is why it is returning 'ODBC library is not found.
-
On line 7 there is a duplicate 'as'. try removing that
-
"After the agent is installed, it runs as a Local System account and does not require administrative permissions to function." https://documentation.solarwinds.com/en/Success_Center/orionplatform/content/core-agent-requirements-sw476.htm and "This the same account used to run virtually all native and non-native Windows…
-
Thresholds are actually set outside of the script itself. It's found just below the script section in the script output area. Looks like default is 5 seconds warning, 10 seconds critical.
-
So the time.nist.gov server is actually found outside of the script in the Component Monitor itself in the 'Script Arguments' section. That eventually gets passed into the script as the first argument/parameter, $time_server = $args[0]; *One item to note here is WHERE the script is executing. If the node is being monitored…