tdanner ✭✭✭✭✭

You can use a query like this to remove a string from all nodes: UPDATE Nodes SET Caption=REPLACE(Caption, '.network.us.bosch.com', '')Just change the string if you want to strip other stuff.

There's a zip with all of the website files in the Orion installation directory.

Good sleuthing, but changing the API key won't fix this. SolarWinds' MapQuest API key is fine and fully paid up. What needs to happen to get the world map resource working again is that we have to adopt MapQuest's plugin for Leaflet.js​ instead of accessing the the map tiles using the generic Leaflet TileLayer component as…

You can use the API to deploy agents. There is not currently an API for controlling what volumes are monitored on systems monitored using the agent.

I can't find an obvious cause of the error within this script, though there are some questionable items such as: * Using fixed string offsets to extract the new NodeID from the return Uri. * Supplying unnecessary properties when creating the node (the minimal set is IPAddress, EngineID, ObjectSubType) And some other things…

That sounds like a very annoying bug. What's the case number?

Here's a PowerShell example: https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/NCM.ExecuteScript.ps1

In PowerShell, it is generally easier to use the SwisPowerShell module (PowerShell · solarwinds/OrionSDK Wiki · GitHub) than to call the REST API. But if you want to stick with calling the REST API from PowerShell, the docs for the request formats are here: REST · solarwinds/OrionSDK Wiki · GitHub . Query is the first…

No update here yet.

The SNMPv3 property issue is addressed in the next version of NPM. Has your support ticket gotten a response?

If you mean SAM Applications, then this should work - could you show your code? If you mean IIS Application Pools monitored by SAM AppInsight for IIS, then we don't support unmanage at that granularity.

Some verbs accept a list of ids to operate on and some don't. Unfortunately, the Unmanage/Remanage verbs work one one node at a time. Fortunately, you can accomplish the same goal using a SWIS "update" operation (unlike in SQL, insert/update/delete are separate operations not part of the query language). In PowerShell that…

This is all correct. If you want to work in C#, you will be targeting the REST API instead of the PowerShell API. They are similar and you can do batch operations that way as well. The REST equivalent to "$uris | Set-SwisObject ..." is a BulkUpdate request. You can see what that looks like on the wiki:…

You need to set objItem.type each time. This should the name of the .NET type stored in value. Like "System.String" or "System.Int32". Refer to the schema to know the correct type for each property.

mesverrum​ is right that you probably want to filter out acknowledged alerts and not based on muting. But if you do want to filter on muting, the way to do it would be to join Orion.Nodes to Orion.AlertSuppression on Nodes.Uri = AlertSuppression.EntityUri and check that "GETUTCDATE()" is between the from and until datetime…

There are three possible values for "Result": 0 = Success 1 = Invalid node. Either the NodeID doesn't exist or it is not an SNMP node (e.g. ICMP, WMI, or Agent polling method). This verb only works for SNMP nodes. 2 = Generic error. Something unexpected went wrong.

Unfortunately, we don't have property-by-property documentation for the schema. You are pretty much limited to exploring and asking questions on this forum. Orion.AlertTriggered is not a table you can query, it's an indication type. The schema documentation doesn't make this very clear, but if you follow the chain of base…

Those kinds of custom pollers are handled separately from these built-in pollers. See https://github.com/solarwinds/OrionSDK/wiki/NPM-Universal-Device-Pollers for how to assign those programmatically.

When you say "There are also several AppendNote functions that do not appear to work", what do you mean? Is an error returned? Is success returned by no note appears?

What version of the product are you using? The Orion.AlertStatus entity relates to an older generation of alerting systems in Orion. That may not be what you want to be using. Orion.AlertActive relates to the current generation alerting system. Documentation for these alert APIs is here:…

Could you change you log level WARN to DEBUG in \Inetpub\Solarwinds\web.config, reload a few pages with the problem, and send your OrionWeb.log file by private message?

That's between you and your boss. If you share your code and the exceptions you are getting, we can help you work through the json parsing issues. There is nothing stopping you from connecting to the Orion database using SqlConnection or any other SQL Server-compatible tool. It's just not something that SolarWinds supports.

NPM 10.6 (currently a release candidate) fixes auditing for custom property changes through the API. Ray, could you list the other operations you are not seeing audit events for? (When the equivalent operation performed through the website does record an audit event, that is.)

There's a bug in the code that generates the audit events for custom property changes. It's recorded as number 240497.

There is currently no API for updating account passwords.

I'm glad you figured it out! I don't know that I would have been able to guess it, but I'll know to look out for that in the future.

Here are the docs: NCM Config Transfer · solarwinds/OrionSDK Wiki · GitHub And here is some sample code in PowerShell: OrionSDK/NCM.ExecuteScript.ps1 at master · solarwinds/OrionSDK · GitHub

One of the changes between PowerOrion 0.0.6 and 0.0.6.1 is removing the call to Add-PSSnapin SwisSnapin. This was done to allow using it only the SwisPowerShell module on machines that do not have SwisSnapin installed. Maybe this is why the SwisSnapin cmdlets are no longer listed as being part of PowerOrion? I see that…

Did you run "Add-PSSnapin SwisSnapin"? Did it yield any errors? Note that Connect-Swis and related cmdlets are also available from the SwisPowerShell module, which is on PowerShellGallery: PowerShell Gallery | SwisPowerShell 2.3.0.108

You are correct - shutdown interfaces should not get the flashing gray box. That's an 8.5 bug that will be fixed in 8.5.1.