eG Administration
 

DISCOVERY - COMMON SETTINGS - GENERAL

Using this page, you can define the discovery settings that are common to both the eG manager and eG agent-based discovery processes.

To access this page, click on the General option under the Settings sub-node of the Discovery node in the DISCOVERY tree structure in the left panel that appears when you click the Discovery option from the Infrastructure tile. Then, specify the following in the COMMON SETTINGS - GENERAL page that appear in the right panel:

  1. Select an option from the Discover components using list to indicate what you want to set as the nick name of the discovered components - the IP address of the components or the Host name? In DHCP environments typically, you may want the host name to be set as the nick name of the components, as the IP address may keep changing. Therefore, Host name option is chosen as default from this list.

  2. In eG Enterprise, priorities are pre-assigned to different applications for the purpose of auto-discovery. By default, the eG manager/agent discovers applications based on the priorities/weightages that have been pre-configured for them. This is because, the Discover multiple components on a system flag is set to No by default. In this case, the discovery process first looks for high priority applications on a host. As soon as high priority applications are discovered on a host, discovery will stop; this means that all low priority applications on that host will be ignored by the discovery process. However, if no high priority applications are discovered on a host, then the discovery process will look for low priority applications on that host. Weights are pre-assigned to low priority applications based on how important it is to monitor them. If only low priority applications are available on a host, then the eG manager will auto-discover only that application on the host that has been assigned the highest weightage; all other low priority applications on that host will hence be ignored. This capability ensures that eG Enterprise's discovery process only discovers the key components that administrators are likely to be interested in monitoring.

    However, if the Discover multiple components on a system flag is set to Yes, then eG manager will auto-discover all applications on a host, regardless of the priorities/weights assigned to them.

    Note:

    The high priority and low priority applications are pre-configured in the eg_services.ini file in the <EG_INSTALL_DIR>\manager\config directory. While the high priority applications are pre-defined in the [HIGH_PRIORITY_COMPONENTS] section of the file, the low priority applications are pre-defined in the [low_priority_applications] section. If you want to add a component to the list of high priority applications, then append an entry of the following format in the [HIGH_PRIORITY_COMPONENTS] section of the file.

    InternalName_of_ComponentType=HIGH

    For instance, if you want the Citrix XenDesktop Director component to be set as a high priority component during discovery, then append the following entry to the [HIGH_PRIORITY_COMPONENTS] section:

    Citrix_XcXenDesktop_Director=HIGH

    Likewise, to set a component as a low priority component, append an entry of the following format to the [low_priority_applications] section of the eg_services.ini file:

    InternalName_of_ComponentType=Weightage_Assigned

    The Weightage_Assigned should be a value between 1 and 10, where 1 is the lowest and 10 is the highest. For instance, if you want the Citrix XenDesktop Director component to be set as a low priority component with the weightage 10, then the entry in the [low_priority_applications] section should be as follows:

    Citrix_XcXenDesktop_Director=10

    Finally, save the eg_services.ini file.

  3. Next, indicate whether/not the target environment is DHCP-enabled. By default, the Is your environment DHCP-enabled? flag is set to No. If the environment is DHCP-enabled, then set this flag to Yes. Doing so ensures that discovery is performed using the host names of applications and not their IP addresses.

    Note:

    If the Is your environment DHCP-enabled? flag is set to Yes, then the Discover components using flag will automatically change to Host name, if it had been set to IP address earlier.

  4. The Show discovered components in flag becomes relevant only if the Host name option is chosen from the Discover components using list. In this case, from the Show discovered components in drop-down, select the case to be applied to host/nick names during discovery. If you want host/nick names of discovered components to be in lower case only, then select the Lowercase option. If this is done, even if a host/nick name is in upper case during discovery, it will be automatically changed to the lower case. Select the Uppercase option if you want the host/nick names of discovered components to be in upper case only. By selecting this option, you can make sure that even host/nick names that are in lower case during discovery are automatically changed to the upper case. Select the Any case option, if you want discovery to dynamically decide at runtime which case to apply. If this option is selected, then the very first time discovery runs post the selection, it will automatically determine whether the host/nick names discovered are in upper case/lower case. The case so determined will be automatically applied to all host/nick names that are discovered subsequently. For instance, if, soon after selecting the Any case option, discovery runs and discovers a host/nick name in the upper case, the case of all host/nick names discovered subsequently will automatically change to uppercase.

  5. Then, proceed to select the types of components that you want the discovery process to auto-discover. The component types selected by default will be listed in the Component types chosen for discovery section. To override this default selection, click the icon available at the far end of the section. The DISCOVERY - SELECT/DESELECT COMPONENT TYPES page will then appear. Click here to view the steps on how to choose a component type for discovery.

  6. In the same way, you can configure components from more categories for discovery.

  7. To allow you to quickly search for a component-type in the Component types chosen for discovery section, a Search text box has been included where you can specify the whole/part of the component-type. The results of your search will be displayed as and when you type the search string in the Search text box.

  8. Finally click the Update button in the to register the changes made.