eG Administration
 

EXPORT/IMPORT CONFIGURATION - IMPORT CONFIGURATION

Multiple eG managers are common in many IT infrastructures. Using industry-standard best practices, administrators of such environments may have fine-tuned the configuration (tests, thresholds, data cleanup frequencies, etc.) of one of the eG managers, and may want to apply the same settings to the other managers. To achieve this, administrators may have to painstakingly document the ‘ideal’ configuration and then manually login to each manager to apply the documented settings one by one. To reduce the manual effort and time involved in this exercise, eG Enterprise enables administrators to quickly apply the configuration of one manager to other managers at one go, using a simple export-import routine. With this capability, administrators can use the eG management interface to quickly export and import the following configurations between managers:

  • Default test configurations
  • List of enabled/disabled tests for component type
  • Default threshold configurations
  • Global threshold settings
  • Alarm policies
  • Descriptor default thresholds
  • Data management settings
  • Monitor settings
  • Manager settings
  • Discovery settings such as Common, Manager discovery and Agent discovery

To enable a manager - say, Manager B - to import the configuration that was exported by another manager - say, Manager A, follow the steps below:

  1. First, copy the zip file that was exported by Manager A from the default download destination to any folder on Manager B's host.

  2. Then, login to Manager B's administrative interface and select the Export/Import Configuration option from the Miscellaneous menu of the Admin tile.

  3. From the Export/Import Configuration page, click on the Import configuration tab page.

  4. Using the Browse button in the Import configuration tab page, browse Manager B's host to locate the zip file that contains the configurations to be imported.

  5. Then, click on the Upload button to upload the file to Manager B.

  6. Once the file is uploaded, all the configuration settings that were exported by Manager A will then appear. With the help of this page, you can choose the specific configuration settings you want to import. To select a configuration, click on the check box corresponding to it. Since some configurations have been grouped under a head, selecting a group head automatically selects all configurations under that head. For instance, selecting the Tests group, automatically selects the Default configuration and Enabling / Disabling tests for component type options. To deselect all displayed configuration settings, click on the Deselect button. To select all displayed configuration settings, click on the Select all check box.

  7. To begin the import of the selected settings, click on the Import button.

  8. If import is successful, a message stating “Configuration has been imported successfully” will appear in this page.

Note:

  • The default configuration of host-level tests in Manager A will overwrite the default configuration of the same tests in Manager B post the import, regardless of the component-type to which the tests are mapped.

  • On the other hand, changes made to an application-level test's default configuration in Manager A, can be viewed in Manager B post the import, only if one/more applications of the same type are managed in Manager B.

  • In case of default threshold configurations, post the import, all default threshold specifications related to host-level tests in Manager A will overwrite the default threshold settings of the same tests in Manager B, regardless of component-type. However, the default threshold settings of application-level tests in Manager A will be applied to Manager B post the import, only if one/more applications of the same type are managed in Manager B.

  • Alarm policies and data management settings configured in Manager A will overwrite the existing configurations in Manager B after a successful import. On the other hand, the fix history maintained by Manager A will be appended to the fix history that pre-exists in Manager B, post the import. Accordingly, if you access the Knowledge Base Search page in the eG monitoring console of Manager B and click the Submit button, the complete history of fixes maintained by that manager and the fix history imported from Manager A will be displayed therein. This is why, you will find the Knowledge Base Search page display the details of even those fixes that pertain to components that are not managed by Manager B.