I would like to know what each system has for monitored volumes. And at that how do I use SWIS to monitor every disk it has detected, except the A: and CDROM...
Any thoughts are much appreciated.
You can use this technique: Triggering discovery of SNMPV2 device through JSON API to add a node with all volumes. To avoid monitoring removable drives, you would need to wait for the discovery to complete and then delete the unwanted volume monitors.
tdanner - Thank you for the response. This seems like more work than it's worth but how do I get a list of what volumes are being monitored on a node? I would like to generate a report showing the monitored volumes
To get the list of volumes Orion is already monitoring on a given node, you can use a query like this:
SELECT VolumeID, Caption, TypeFROM Orion.VolumesWHERE NodeID=123
(Replace 123 with the actual NodeID you want to check, of course).
Thank you soo much!!! I would like to add the nodename to this query. I notice from wathing some SW videos on the API there is a way to avoid JOINS... How do I do this and is there info avail I can lookup?
The way to avoid explicit joins is called navigation properties. To add the node name to the query, you can do this:
SELECT VolumeID, Volumes.Node.NodeName, Caption, TypeFROM Orion.Volumes WHERE NodeID=123
As it turns out the autoupdate of the agent has really messed up my SW monitored nodes. 96 of them say reboot required, when in fact what actually needs to happen is that the new agent needs to be installed MANUALLY! I recently upgraded from SAM 6.2 to 6.2.1 which does include a new agent so maybe that is where things went south on me.
Is anyone else having this problem?
Wrong post worry about that ... I meant to post this is another discussion!
I am trying to look up information that explaines this... I am not much of a DBA so this does not really make sense to me. What is the convention here so I can apply navigational properties to other queries? Is there any clear doc on this?
In general, anywhere you can refer to a property in SWQL, you can refer to a chain of navigation properties - the SELECT clause, WHERE clause, the ON clause of an explicit JOIN, etc. The syntax looks C-family languages accessing a property on an object.
To see what navigation properties are available from what entity types, you can use SWQL Studio and expand the tree on the left. Navigation properties are listed with the regular properties and marked with a "chain" icon. You can also browse the generated HTML documentation - https://solarwinds.github.io/OrionSDK/schema/ - to see the available navigation properties.
I have been looking at the schema doc. I get it for the most part but using your example:
How do I get to Volumes.Node.NodeName and where is that illustrated in the doc you showed me?
Start with the property list for Orion.Volumes: https://solarwinds.github.io/OrionSDK/schema/Orion.Volumes.html. At the bottom of that page is the list of navigation properties supported by Orion.Volumes. That's where you'll see the "Node" property listed. Since "Node" is a navigation propertly, it is linked to the page for the target entity type. In this case, that's Orion.Nodes.
I do not see how you get Volumes.Node.NodeName though. This is where I am confused.
Node is a navigation property of Volumes, and it leads to the associated instance of Orion.Nodes. NodeName is a property of Orion.Nodes, so you can access it there.
