-
Home
- Studio Monitors with Content 11
WBEM Query
The WBEM Query Monitor allows you to query a WBEM Provider. Depending on the implementation, the WBEM Provider may also be called CIM Provider, CIM Agent, WBEM server, etc.
To configure the WBEM Query Monitor, you need to:
-
specify a WBEM namespace (or CIM namespace)
-
specify a WQL query such as SELECT DeviceID, Name, OperationalStatus FROM CIM_LogicalDevice).
WQL usually requires the WBEM Provider (or CIM Provider) to implement the executeQuery() method. Because this is rarely the case, Monitoring Studio X converts the WQL query into a regular enumerateInstances()query, which is supported on all platforms.
You will then set the WBEM Connection Settings (port and encryption information) at the Host level, when applying the Template(s) containing the WBEM Query Monitor(s).
Once the WBEM Query Monitor is properly configured, the result of the query is displayed in the Result parameter. Each instance is represented as a separate line and properties are separated with semicolons. Properties of type Array are represented as a pipe-separated list of values. The SELECT DeviceID, Name, OperationalStatus FROM CIM_DiskDrive query will for example return this type of result:
DISK0;Physical Disk Drive 0;2|;
DISK1;Physical Disk Drive 1;2|;
DISK2;RAID A;6|32769|;
The result of the WBEM query can then be analyzed through a wide range of tools (Dynamic Object, Numeric Value Extraction, Text Pre-Processing, String Search, and Value Map).
Refer to the table below to know how to configure the WBEM Query Monitor:
| Property | Description |
|---|---|
| WBEM Query | WBEM query to be run (Example: SELECT DeviceID,OperationalStatus FROM CIM_DiskDrive). |
| Credentials Used to Execute the WBEM Query | Credentials required to execute the WBEM query. By default, System Credentials are used. |
| Display Name | Name to identify the WBEM Monitor instance in TrueSight Operations Management. |
| Internal ID | ID to be used to store the WBEM Monitor configuration in the PATROL Agent configuration. This Internal ID is automatically generated based on the Display Name provided but can be edited if needed. |
| Collect Schedule | How often new data is collected. A new collect can be performed from once every second, to once in a day. By default, the collect schedule is set to 2 minutes. |
| Namespace | Logical group of related monitor types representing a specific technology or area of management (Example: root/cimv2). |
| Timeout After | Time in seconds after which the query will be stopped (Default: 30 seconds). If the query times out, a collection error will be triggered either on the Status parameter or the Template's Collection Error Count parameter. |
Once you are done with the configuration, you can run a Dry Run to simulate the execution of this Monitor on a specific host and therefore verify that the output is conform to the expected result.
Finally, you can define where alerts are reported, the threshold alert values, and the alert severity levels for the Monitor:
-
Indicate if you want Monitoring Studio X to report Monitor Errors in The Monitor's Status Parameter or The Template's Collection Error Count Parameter (default).
-
Then, for each parameter, define up to three alarm ranges (Alarm #1, Alarm #2 and Out-of-range) each with a minimum and a maximum value:
- Use the Alarm #1 and Alarm #2 options to define the range of parameter values that triggers warnings and alarms.
- Use the Out-of-range border conditions to be informed when the collected values are outside the norm (less than or greater than the defined range limits).
Refer to the Configuring Alerts for details and to Studio WBEM Query for more information about the parameters available and the thresholds set by default.