Agents Administration - Tests
 

Configuration of RHEVMEventsTest

This test enables administrators to promptly capture and report the count and details of critical information, error, and warning events that are generated on the RHEV manager.

By default, the test monitors a pre-defined set of events belonging to pre-configured event categories. You can override this default setting by including/excluding specific events from an event category or by adding more categories. To achieve this, do the following:

  • Edit the eg_tests.ini file in the <EG_INSTALL_DIR>\manager\config directory.
  • In the [RhevEvents] section of this file, you will find the event categories that are currently monitored by RHEV Events test, and the individual events of each category. The format of these entries is:
    RHEVEventsTest:<EventCategory>=<Comma-separated list of eventsIDs grouped under this category>
  • To add a new event category to the list, you just need to append a line to the [RhevEvents] section in the format mentioned above. For instance, say, you want to include a category named ImportExportEvents to event categories that pre-exist. In this case, you will have to insert a line in the [RhevEvents] section for this category, as mentioned below:

    RHEVEventsTest:ImportExportEvents=1150,1151,1152,1153


  • Finally, save the file.

The default parameters associated with this test are as follows:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

  • In the PORT text box, specify the port at which the specified HOST listens. The default port is 8443.

  • In the RHEL MGR USER and RHEL MGR PASSWORD text boxes, specify the credentials of the user with read-only access to the Restful API on the RHEV manager. To know how to create a read-only role and assign it to a user, Click here.

  • Confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • Specify the domain to which the RHEV Manager belongs to in the RHEL MANAGER DOMIAN text box. By default, internal is displayed here.

  • If the RHEV manager to which the eG agent should connect is SSL-enabled, then set the SSL flag to Yes. If not, set it to No.

  • The 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.

  • To make diagnosis more efficient and accurate, the eG system 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 against DETAILED DIAGNOSIS. 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:

    • The eG manager license should allow the detailed diagnosis capability

    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the Update button will register the changes made.

When changing the configuration for specific servers, a "*" beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a "$" or contain a series of "*". A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.