tdanner ✭✭✭✭✭

Oh, I see. I didn't pay attention to what you were trying to do and went straight to fixing the Uri error. The right way to do this is to use the verb Orion.AlertActive.AppendNote. The way the AlertStatus view works, this will have the effect of replacing (not appending to) what shows up in the Orion.AlertStatus.Notes…

If requestb.in is not showing anything, then your request didn't make it there. You will need to modify swisclient.py to be able send the request on the default port instead of 17778.

The error you are getting seems to indicate that SWIS is receiving an HTTP GET request instead of the POST request that should be used for /Create/. Given the set of component you are using, I can't figure out why that would be. I have the same version of Python, Swisclient, and Requests and it can call create just fine…

You can ask SWIS for the set of properties an interface has: SELECT Name FROM Metadata.Property WHERE EntityName = 'Orion.NPM.Interfaces' AND IsNavigable=0 Then use the results from this query to build a query that gets a bunch of interfaces: SELECT a, bunch, of, properties FROM Orion.NPM.Interfaces WHERE my-condition-here…

You can run the Syslog Viewer app to see if Orion is receiving messges correctly.

Responded in other thread. You aren't doing anything wrong - this was inadvertently broken in NPM 12.

I'm glad this story had a happy ending!

The problem might be the empty <CredentialID></CredentialID> element in $CorePluginConfigurationContext. The contents of each <CredentialID> element must be an integer.

You might find it helpful to get this working with a tool like Postman first. Once you have a working request in Postman you can shape the PHP code to match it.

That narrows it down some. Try this: print out $nodeid and make sure it is what you expect.

Metadata.Property has an IsInherited property. You can use this to filter them out. Like this: SELECT EntityName, Name, Type FROM Metadata.Property WHERE IsInherited=False

That might work, but you're on your own for database edits. I strongly recommend you set up a test instance of the product and try it out before doing it in your production system.

That's a tricky one. I believe there may be a way to issue a range query, where you would ask if there are any subnets >= 10.1.0.0 and <= 10.1.255.255. I sent this thread to an IPAM expert in case he can suggest something.

File > New Report > Advanced SQL.

That will pull all the availability data in the database (with no limit), grouped by month. If just want to limit it to last 12 months, add "AND rt.DateTime > ADDYEAR(GETUTCDATE(), -1)" to the WHERE clause. If you need something else, please be specific about what you are looking for in terms of grouping and aggregation.

Have you tried these steps? Exporting Reports as Excel and PDF from the Orion Web Console

Right - in one operation you can set the same properties and values on a set of objects. If you need to set different values then you will have to use a loop. SWIS doesn't have a way to accept different values for different objects in a single operation. (A note on terminology: in SWIS we use the term "verb" to refer to…

Mike, We are able to get the same error you are seeing when we try it with an SNMPv3 node. Does that match what you are seeing? Works for SNMPv1/2 but fails for SNMPv3? Thanks, Tim

Oops! That's my typo. Python object literal syntax is { prop : value} not { prop = value }. I edited my post above to fix the error.

Another way to do it would be to configure Windows authentication for the Orion website and give the kiosk user account rights in Orion. Then you would bypass the login screen entirely.

Like this: SELECT TOP 10 NodeID, ToString(SLA_Sync_Time) from Orion.NodesCustomProperties

This is not available for SWQL queries. In Python you can use a line like this to get all of the connection profiles: profiles = swis.invoke('Cirrus.Nodes', 'GetAllConnectionProfiles') I don't have an example output handy to show, but with python interactive mode it should be easy to explore the return format to find what…

Documentation for the new alerting entities has been posted at https://github.com/solarwinds/OrionSDK/wiki/Alerts. (The SDK is moving to Github - see Orion SDK moving to Github.)

That list comes from the Orion.NodeIPAddresses entity. I wouldn't rely on the order. However that table also lists the InterfaceIndex associated with each IP address. If the Fortinet devices use a consistent interface index for the proxy address, that might be something you can rely on.

I think you might be connecting to the wrong machine. Are you using the hostname of your Orion server or your SQL server?

The verb you are looking for is Cirrus.Nodes.AddNodeToNCM. Just pass the node id (i.e., "2") and it should do what you want.

That all sounds plausible. Pulling the ViewID and column number from custom properties would be a simple change. If you want to use an alert as your automation engine here, you probably don't want to leave the alert active indefinitely and you also want to be careful that it won't re-fire on the same interface repeatedly,…

You can delete resources from a view with a regular delete operation. In PowerShell that's "Remove-SwisObject". In REST it is an HTTP DELETE (actually BulkDelete might be faster since you have a lot - see https://github.com/solarwinds/OrionSDK/wiki/REST#bulkdelete-request ). You just need the SWIS Uri of the resource. We…

This query will give you the row counts for all your tables. From there you can follow up on the big ones and see how much space they are taking up in bytes. Then we can talk about how to tune data retention to meet your needs. select t.table_name, i.rows from sysindexes i, information_schema.tables t WHERE i.id =…

No current plans. What kind of modifications to existing do you want to make programmatically? For context - I see the primary use case for the discovery API being to generate a one-shot discovery profile from a script.