Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
NetApp Active Discovery is used to discover instances by means of the NetApp OnTAP API. There are two distinct methods of NetApp Active Discovery:
Regardless of the selected method, there are three sections to the NetApp Active Discovery:
Performance Object Active Discovery will return the name field of all the returned objects, as both the instance name and wildcard value. Note that this makes the discovery method not suited for cases where the object cannot be retrieved by name, or where duplicate names can exist. (For example, a cluster controller will return all the managed systems as having the same “name” field (they will all be named “system”) – but they must be queried by the system UUID. For this reason the system performance datasources are not discovered using Performance Object discovery.) An exception to this is that the Performance Object discovery method has special processing to support volume discovery in cluster mode, so it can deal with possibly duplicative volume names, and return the UUID field as the identifier.
To use Performance Object NetApp Discovery, set the Type parameter to ‘Performance Object’. Once you set type to Performance Object you’ll need to specify the NetApp Object (as referred to by the NetApp API) to discover – this is typically an object like a volume, disk, lun, etc.
The filter in the image below filters against ##WILDALIAS## to only discover volumes with the string “vol0” in their name:
The filter in the image below discovers only volumes on a specific aggregate, using ‘VOLUME-ID-ATTRIBUTES.CONTAINING-AGGREGATE-NAME’ as the filter attribute:
The image below shows the Active Discovery section for the NetApp volume performance datasource, modified to only apply to volumes with beta in their name:
XML based NetApp instance discovery is a more powerful (but more complicated) method. It works by specifying an XML request to send to the NetApp, using one of the NetApp SDK API calls, and then specifying how to interpret the results.
To use XML NetApp Discovery, set the Type parameter to XML. Once you’ve set the type to XML, you’ll need to specify:
The XML response that a NetApp will reply to the call may look like this:
The Instance Locator field identifies that the instances are within the array contained within the <attributes-list> XML path. (In this case, that is the array of <instance-info> elements, but these are selected automatically.) The unique identifier, the Instance Value, is set to uuid – so this will return the contents of that element.
Instance Name is set to uuid:(.*?):.* – so this will also return the contents of the UUID field, but only the part that matches the regular expression capture group (the parenthesis.) The regular expression captures the contents of the uuid field before the first colon. So for the UUID field scenariolab-01:kernel:system it will return scenariolab-01.
The Instance Description is set to the contents of the Name field. Thus for the above XML result, the returned instances will be:
In This Article