eG Administration
 

Generating a test of Custom Test type using Integration Console

Once all the measurements of a Custom test have been specified, the Generate tab will be enabled in the NEW TEST DETAILS page. In this page, you will have to specify the implementation of the test.All Custom tests that are newly added to eG Enterprise have to be implemented in Java.

To generate a new Custom test, do the following:

  • The directory in which the test's implementation exists should be specified in the input box corresponding to the Class file specification. The test implementation must exist in a Java class file with the same name as the test name − e.g., the implementation of MsSqlNetTest must exist in a class file named MsSqlNetTest.class. If the class file is present in a remote location, then you can upload it to the eG manager, by clicking on the Choose button adjacent to the Class file text box. This will invoke a pop-up window using which you can Browse for the class file and specify its location. Finally, click the Upload button in the pop-up window, to upload the class file in the remote location to the eG manager. However, if the class file has already been uploaded to the eG manager, then this procedure can be dispensed with. Instead, just specify the location of the file against the Class file text box.

  • Some class files may require certain ".jar" or ".so" (shared object files) files for their execution. The name of the file along with the directory in which these files exist has to be specified in the Library file specification. Please note that the size of these files should not exceed 0.5MB in order to prevent excessive load while uploading. If the library files is present in a remote location, then you can upload it to the eG manager, by clicking on the Choose button adjacent to the Library file text box. This will invoke a pop-up window using which you can Browse for the library file and specify its location. Finally, click on the Upload button in the pop-up window, to upload the library file in the remote location to the eG manager. However, if the library file has already been uploaded to the eG manager, then this procedure can be dispensed with. Instead, just specify the location of the file against the Library file text box.

    • Note:

    When the class and library files are uploaded to the eG manager for the first time, they would be uploaded to the <EG_INSTALL_DIR>/tmp directory in the manager host. When the Generate button is clicked, they would be moved to the <EG_INSTALL_DIR>/config/tests directory. Therefore, subsequent visits to this page will only have the <EG_INSTALL_DIR>/config/tests location displayed against the Class file and Library file text boxes.

  • The Load class file checkbox should be selected if the class file has to be loaded every time the Custom test is implemented. For the first time when the class file information is provided, it is mandatory to select this box so as to load the class file along with the new measurements.

  • The Load library file check box should be selected if the library file has to be loaded every time the Custom test is implemented. For the first time when the library file information is provided, it is mandatory to select this box so as to load the library file along with the new measurements and the associated class file. Multiple library files can be specified, but each entry should be separated by a comma (,).

  • To make diagnosis more efficient and accurate, the eG Enterprise suite 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. For example, when the CPU usage of a host reaches the threshold, the agent can be configured to provide more details - e.g, the top 10 process that are consuming more CPU resources. Alternatively, these tests can also be run periodically for proactive monitoring purposes.

    The check box Click here to enable detailed diagnosis for this test can be used to define detailed diagnosis capability for a custom test. The option to enable detailed diagnosis for an IC-based test will be available only if the following conditions are fulfilled:

    • The eG license should enable the detailed diagnosis capability.
    • Both the normal and abnormal detailed diagnosis frequencies should not be 0. For more information on configuring these frequencies, refer to Administering eG Enterprise document.

  • Clicking the Generate button will result in the test's implementation being integrated into eG Enterprise.