Configuring location tagging

Location tagging indicates where each Configuration Item (CI) was created. It enables location-based filtering of configuration items in BIRT reports and API queries.

If you enable location tagging, each discovered object that is stored in the discovery database includes the locationTag attribute (string). Objects such as relationships, aggregation objects, and inheriting objects that are created by topology agents, include location tag data under certain conditions:
  • A one-to-one relationship (such as Dependency or NetworkConnection) includes a location tag if the location is the same for both connected objects.
  • An aggregation object (such as a cluster) includes a location tag if the location is the same for all aggregated objects.
    Note: In case of custom collections, the locationTag attribute is set only when the value of location tag of all custom collection's core CIs is the same. When the custom collection is extended with a core CI that has a different location tag, the locationTag attribute for such custom collection is cleared.
  • A simple object includes the location tag from the object it is based on.

In all other cases, objects that are created by topology agents do not include a location tag value.

To enable location tagging, set the following property in the file:

Location tag values can be either static (specified for a particular server or anchor) or dynamic (specified for a specific discovery or IdML book import). A location tag value is limited to 192 characters. If the specified location tag exceeds 192 characters, it is cut to required length.


When you run a Level L1 discovery, Configuration Items which are already present in the database are not updated. As a result, location tags are assigned only to the newly discovered objects.