To run a Monitored Subjects Detail Report, select Tools > Monitored Subjects Detail Report from the Live Exceptions Browser menu.
The report lists the elements in the selected group or group list that is being monitored by rules in a profile. The name of the subject being monitored and its technology type appear at the top of the report (for example, Subject: Myservers (Server Group)). The report shows the elements in a group or group list, the rules that apply to each element, any rules that do not apply, and any rules that are disabled. For group lists, the report lists the information for each group in the group list.
The report consists of five columns which are:
Reading of the LE Monitored Subjects Detail Report can be broken down and defined in three steps or parts.
Part 1 - Elements with no rules that appear in either the "Rules That Apply" or "Rules That Do Not Apply" columns
When creating an LE Alarm Rule, one of the first steps is specifying an Element Type that the rule should apply to. If this choice is different than the element being reviewed, then this is how it will appear in the Monitored Subjects Detail Report. For instance, a rule with an Element Type of "Disk Partition" would not apply to a servers ethernet port element. To resolve this, take the target rule that is not appearing as applicable to the target element and modify it's Element Type value to something that is a closer match to the elements Element Type. This may take a small amount of trial and error as the Element Types defined in an elements Poller Configuration Modify UI do not match the list presented in the LE Rule Modify UI. An easy way to get a good idea of what Element Type to use for a target element is to see which Element Type would need to be selected to make that element available to run a report against via the eHealth web. Sometimes there is only one option, for instance Router/Switch. In the LE Rule Modify UI Element Type selection field, there might be a longer list of options. I.n this field, in the Router/Switch example in LE, the options are:
Router/Switch with CPU
Winphoria Active Directory
Winphoria Control Switch
In this case, while the Router in question might have a CPU, the better choice would be to start simple at the top level "Router/Switch", get the rule in either the Rules That Do or Don't Apply columns. Once the Element Type has been properly selected, and the rule is showing in the Rules That Do or Don't Apply columns, now we can move on to parts 2 and 3.
Part 2 - Elements with rules that appear in the "Rules That Do Not Apply" column
When a rule appears in this column for an element, it is there for one of two reasons.
The first one is the simplest to check and resolve. When a rule has been disabled, when it appears in this column, it will specifically state "(Disabled)". To resolve this, simply go into the particular rules LE Rule Modify UI and Enable the rule.
The second one requires the understanding that not all elements of the same Technology Type are going to support the same statistics and variables. For instance, the variables available for reporting are going to be different for a Unix System when compared against a Windows System. When creating an LE Rule, it is not yet associated to an element type, so when choosing a variable after selecting an Element Type during rule creation, the user is presented with a full list of all possible variables. In the example of Unix vs. Windows Systems, you would get both full sets of variables. To resolve this, we need to utilize a feature of the eHealth Web UI Run Reports interface. Take the particular element in question, and choose it within the setup of a Standard Trend Report via the eHealth Web UI. Now the variable list will appear as the same as that seen in LE. To narrow the list down to only variables applicable to the target element, select the "Validate Variables" button. This is the list of supported variables for the target element. Note that the variable listed in the "Rules That Do Not Apply" column is not present. Change the variable in the rule that is appearing as not applicable, to one that is applicable. In the end, when it states that this is due to the variable being undefined, this is stating that the variable does not have data collected from this element for one reason or another (some of these would be the device does not support it, or the eHealth is not polling the data for that variable).
Part 3 - Elements with rules that appear in the "Rules That Apply" column
If a rule appears in this column for a target element the Element Type selected is correct for the target element and the variable selected is available to the element.
Release: LHBASC99000-6.2-eHealth-Live Health Upgrade Elements