This page appears upon clicking the DETAILS button in the Measurements section of the page displaying the layer model, tests, and measurements of a component. The page reveals more information regarding the status of a test, such as:

• The host on which the test executed
• The type of component that was monitored by the test
• The 'IP:port number' of the monitored component
• The name of the test
• If the test takes descriptors, then the name of the descriptor for which measurements are currently being viewed
• Whether the test is an external or an internal test
• How often was the test configured to execute
• The time that had elapsed since the last time the test ran
• The current state of the test
• The name of the problem measure
• The Alarm policy that was assigned to the measure

This page additionally displays the threshold settings that were violated, thereby resulting in an alarm. A review of the current threshold settings is thus made possible, so that changes, if required, can be performed later using the eG administrative interface.

Note:

As stated earlier, this page will display the 'IP:port number' of the monitored component. However, if the problem component had been managed using its host/nick name, then the Component field in this page will display the 'host/nick name:port number' of the component. The IP that maps to the displayed host/nick name will appear adjacent to it, within brackets. For example, if the component 192.168.10.28:10818 had been managed using the nick name 'Nasserver', then the Component field in this page will display the value: Nasserver:10818 (192.168.10.28).

If a maintenance policy is associated with the host/component/test for which details are being viewed in this page, then, during the configured maintenance period, the details of the policy will be displayed in this page. For example, assume that this page displays the details of the Network test of an Oracle Database server - 192.168.10.8:1521:egurkha. Also, say, a maintenance policy has been configured to suppress the alerts related to Network test for the Oracle Database during 15:00 and 16:00 every Friday. In such a case, if the measurement time falls between 15:00 and 16:00, then the Test Measure Status Info page for the Network test of the Oracle Database component, will additionally display the following details:

• The Maintenance Match Criteria: If the maintenance policy applies to the monitored host as a whole, then the host name will be displayed here. If the policy applies to an application on the host, then the component name/IP will be displayed here. Similarly, if the maintenance policy suppresses the alerts related to a particular host-level test, then the test name and host name will be displayed in the format: TestName/HostName. On the other hand, if the maintenance policy hides the alerts pertaining to a particular component-level test, then the test name and component-name will be displayed here in the format:TestName/ComponentName. In the case of our example, the maintenance policy applies to a host-level test - the Network test - of the Oracle host. Therefore, the Maintenance Match Criteria will be: Network/192.168.10.8. If multiple maintenance policies prevail during the same period, then the match criteria will be displayed as a comma-separated list.
• Policy group name: The policy group into which the maintenance policy/policies has been added; multiple groups appear as a comma-separated list.
• Policy name: The name of the maintenance policy; if multiple maintenance policies execute during the measurement time, then the policy names will be displayed as a comma-separated list.
• Policy time: The time specifications associated with the maintenance policy/policies displayed against Policy name; for our example, the time specification would be 15:00-16:00#Friday. Multiple time specifications are displayed as a comma-separated list.

Whenever eG Enterprise fails to generate an alarm that is expected, administrators can switch to this page (by clicking on the DETAILS button) to figure out if a maintenance policy prevails during that period. If so, then they can safely conclude that no threshold reconfiguration is necessary as eG Enterprise has only suppressed the alarm.