eG Administration 
 

Specific test configuration page

This page allows you to pick the specific component for which a particular test is to be configured. To access this page, click on the icon available in the Admin tab. Then, select the Specific Configuration option from the Tests sub-menu in the Agents tile. Do the following using this page:

  • First, from the Component type list, choose the type of component.

  • All managed components of the chosen type will then populate the Component name list. Pick the component for which a test is to be configured. If you want to see only the component that are yet to be configured, then select the check box near the Show Components yet to be Configured for Monitoring option. Doing so, will populate only the components that are not yet configured in the Component Type list box. In large environments where a multitude of components have been managed, the Component name list will naturally be populated with too many components. Choosing a component from this list could be a time-consuming process. To filter the Component name list so that you have less number of components to choose from, use the Component Search option. You can then pick the component for which a test is to be configured from this list.

  • Then, select the type of test to be configured - i.e., whether a Performance test or a Configuration test. The Configuration option will be available only if the eG license enables the Configuration Management capability. Then, by selecting an option from the Test type list, indicate whether the you want to configure the component-specific parameters of a Performance test or a Configuration test. While a test of type Performance typically reports useful performance statistics pertaining to a component, a test of type Configuration, simply reports the current configuration of a component and captures configuration changes (if any).

  • Doing so will invoke an Agent Summary section, using which you can instantly determine which internal agent and external agent is monitoring the chosen Component.

  • Below the Agent Summary, you will find a list of Unconfigured Tests, Configured Tests, and Excluded Tests for the chosen Component. The Unconfigured Tests list displays those tests that have been enabled for the chosen component-type, but are yet to be configured. To configure any of the listed tests, select the test of interest from the Unconfigured Tests list, and click the Configure button. The parameters of the test will then be displayed, so that you can configure them.

  • Here again, the parameters prefixed by a * (asterisk) denote those parameters that require manual configuration. Once the parameters are configured, click the Update button to save the chages to the test configuration.

    • Note:

    When changing default configurations of tests, the values with “$” indicate variables that will be replaced by eG Enterprise according to the specific component being managed (e.g., if the URL is “http://$hostName:$port”, for a specific web server running on the host www.abc.com on port 80, the URL parameter will be set to “http://www.abc.com:80”).

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

  • Clicking on the Update button, will register the component configuration. If the Apply to other Components check box was enabled earlier, then Agent - Tests - Apply Configuration page will appear. Using this page, you can choose the Parameters that are to be applied. To apply all the Parameters, select the check box that precedes the column name Param Name. Then, select the components to which the chosen parameters are to be applied from the Existing Component list, and click << button to transfer the selection to the Components to be Configured list. Finally, click the Apply button. This ensures that the values passed to the selected parameters are automatically applied to the components in the Components to be Configured list. This saves the time and labor involved in repeating the same set of configurations for every component of a particular component type.

  • The Configured Tests section on the other hand, displays those tests that have already been configured - such tests are typically of two types - tests that take the default configuration, and tests that have been specifically configured for the chosen Component. Accordingly, the Configured Tests list box will list tests under two categories - Tests with specific configuration and Tests with default configuration. If required, you can reconfigure any of these tests, by picking the test of interest from the Configured Tests list and clicking the Reconfigure button. This will once again display the parameters of the chosen test, allowing you to edit the values of any of the parameters.

  • While reconfiguring, test parameters that are more than 20 characters in length will be accompanied by a View button. For example, consider the OracleAlerts test. One of the parameters of this test is the Searchpattern, which takes a comma-separated list of alert patterns in the Oracle alert log file that require monitoring. If the value of this parameter exceeds 20 characters, then, while attempting to reconfigure this parameter, a View button will appear alongside it. Clicking on this button will display the value of that parameter in a separate pop-up window. This display will help you view the value of that parameter completely, and make changes to it comfortably. After making the required changes, click on the Apply button to register the changes.

  • The Excluded Tests list displays tests that have been excluded for a specific component - i.e., tests that will not execute for a selected Component. To exclude a test that has not yet been configured, pick the test from the Unconfigured Tests list, and click on the Exclude button. To exclude a test that has already been configured, pick the test from the Configured Tests list, and cick the Exclude button. If more than one component of the chosen type has been managed, then, clicking on the Exclude button will lead you to Agent - Tests - Specific Configuration page, using which you can exclude the selected test for the other components of that type as well.

  • At any given point in time, you can make sure that an excluded test starts executing on a component, by including that test. For that, select the test from the Excluded Tests list, and click the Include button.

    • Note:

    • If a specific test configuration has been applied to a component, the default parameter values will no longer apply. The user has to change the parameters manually. By excluding and then including the component, the user can re-ensure that the default parameters apply for a component.

    • Normally, a few/all the tests associated with a component share the same set of parameters. To ensure that administrators do not perform the redundant task of configuring each such test separately, you can configure the eG Enterprise system in such a way that if one of these tests is configured, the other related tests get configured automatically. For instance, take the case of the FnSessionTest and the FnHaStatusTest that the eG external agent executes on a Fortigate Firewall. These two tests support the same parameters as the FnSystemTest. To ensure that these two tests are automatically configured, as soon as the FnSystemTest is configured, do the following:

      • Navigate to the directory <EG_INSTALL_DIR>\manager\config directory and edit the eg_testparam.ini file.
      • Go to the [TEST_RELATIONS] section, where entries for tests that are related to one another pre-exist.
      • To set a relationship between the Fortigate Firewall tests in our example, append the following entry to the [TEST_RELATIONS] section:
        FnSystemTest=FnSessionTest, FnHaStatusTest

      This ensures that, once you configure the FnSystemTest in the administrative console, values provided for the FnSystemTest parameters, are automatically applied to the FnSessionTest and FnHaStatusTest, configuring those two tests as well. However, such a test relationship will not affect the TestPeriod parameter. If for some reason, different tests executing on a component are set to execute at a different Testperiod, then, even if an entry exists for such tests in the [TEST_RELATIONS] section, the Testperiod for the tests will continue to be different. On the contrary, if you also want the Testperiod of one test to be automatically applied to the other tests executing on the same component, you will have to follow the steps given below:

      • Edit the eg_testparam.ini file.
      • In the [COMMON_TEST_RELATIONS] section of the file, provide an entry for all the tests that will share the same set of parameters, including the Testperiod. This specification should be in the following format.

        <Comma-separated list of related tests>=None

        For instance, for the Fortigate Firewall example above, the entry would be:

        FnSessionTest,FnSystemTest,FnHaStatusTest=None

        This means that if any one of the three tests specified is configured, then all the parameters (including Testperiod) of the configured test will be automatically applied to the other two tests, thereby configuring those two tests also.