Device Events Test
In most environments where the ADC appliance is deployed, administrators may want to figure out the performance and efficiency of the ADC device. If the status of the ADC device is up, then they can figure out that the device is operating without a glitch! If the ADC device experiences any issues, then the environment may also get affected and administrators may find it diffuclt to load balance the servers sitting in the backend. For an environment to operate without any technical issues, it is the onus of the administrators to continuously monitor the ADC device. The Device Events test helps administrators in this regard!
This test scans the syslog file for the events related to the target ADC device and reports the number of times the status of the device was up/down/out of service. In addition, this test also helps administrators to identify the number of times the ADC system was started/stopped, the number of times the Route6 was up/down and the number of times the ns.conf file was read for configuration information by the ADC device. Using this test, administrators can identify if the performance of the ADC device is maintained consistently or if any performance degradation is noticed.
For this test to run and report metrics, the ADC appliance should be configured to create a Syslog file in a remote Syslog server, where the details of all interactions with the ADC appliance will be logged. To know how to configure a remote Syslog server for the use of the ADC appliance, refer to Creating a Syslog file in a remote Syslog server topic.
This test is disabled by default. To enable the test, follow the Agents -> Tests -> Enable/Disable menu sequence in the eG administrative interface, pick Citrix ADC VPX/MPX as the Component type, select Performance as the Test type, choose this test from the list of disabled tests list, and click on the < button.
Target of the test : An ADC VPX/MPX
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the ADC appliance being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The IP address of the host for which the test is being configured. |
Port |
The port at which the host listens. By default, this is NULL. |
Log File Path |
This test reports metrics by parsing a Syslog file. Specify the full path to the Syslog file here. |
Search String |
By default, the Syslog file may contain information relating to a number of servers that are inter linked with the target ADC appliance. In order to obtain the metrics of the target ADC appliance alone, specify the hostname or the IP address of the target ADC appliance for which the logs are to be read from the syslog file, in the Search String text box. Using this search string the information in the Syslog file may be parsed and metrics may be collected. |
Search String Index |
Here, specify the cursor position after which the eG agent should search for the specified Search String (or the position up to which the eG agent should ignore while searching for the specified Search String) in the syslog file. For example, if the specified Search String appears in the syslog file at the 17th position, then you may need to specify the Search String as 16. |
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Device down events |
Indicates the number of times the ADC device was down. |
Number |
Ideally, the value of this measure should be zero. |
Device out of service events |
Indicates the number of times the status of the ADC device was Out of Service. |
Number |
|
Device up events |
Indicates the number of times the ADC device was up. |
Number |
|
ADC system stopped events |
Indicates the number of times the ADC system was stopped. |
Number |
|
ADC system started events: |
Indicates the number of times the ADC system was started. |
Number |
|
CPU started events |
Indicates the number of times the CPU of the ADC device was started. |
Number |
|
Route6 down events |
Indicates the number of times Route6 was down. |
Number |
|
Route6 up events |
Indicates the number of times Route6 was up. |
Number |
|
SNMP module started an alarm: |
Indicates the number of times an SNMP module started an alert. |
Number |
An alert will be generally raised when the value of a monitored attribute crosses the threshold value. |
SNMP module stopped an alarm |
Indicates number of times an SNMP module stopped an alarm. |
Number |
|
ADC started reading configuration Events |
Indicates the number of times the ADC device has started reading the configuration from ns.conf file (during boot up). |
Number |
A high value for this measure is a cause of concern as this may indicate that the ADC device is either corrupted or is often restarting. |
ADC completed reading configuration Events |
Indicates the number of times the ADC device has completed reading the configuration from ns.conf file (during boot up). |
Number |
|