This version of the documentation is archived and no longer supported. It will be removed on 01 March 2021. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Host Mappings

Host mappings are based on the data that the Monitoring Agent retrieves on a regular interval. Ops Manager regenerates the entries on the Host Mappings page after each retrieval.

Host mappings are displayed in three-column rows:

Column Content
Host The preferred hostname and port for the deployment.
Alias One alternative hostname or address and port for the deployment.
Last Updated The timestamp when the host mapping was updated.

If a host has multiple aliases, each mapping of host to alias is listed in its own row.

Preferred Hostnames

The preferred hostname also appears in the Name column of the Deployment page. If you want a different preferred hostname than what Ops Manager chose, regenerate the list of mappings in one of the following ways:

  • Specify constraints on how Ops Manager picks a preferred hostname. See Preferred Hostnames in Edit Project Settings for more information.
  • Reset the mapping list. See Reset Duplicates in Edit Project Settings for more information.


Resetting duplicates and setting constraints on the selection of a preferred hostname cause Ops Manager to lose the monitoring history for affected hosts. Chart data based on this history is also lost.


Depending on what Ops Manager obtains from a monitored host, the alias may be in any one of the following forms:

  • Fully qualified domain name (FQDN)
  • Internal hostname
  • External IP address
  • Internal IP address


To prevent naming conflicts, Ops Manager does not use localhost or similiar local designations for new or remapped hosts unless no other hostname option is possible.