Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

Service, module and task assignments

Monitoring ► Service, module and task

Use this screen to add a reporting hierarchy definition or edit an existing hierarchy definition.

Access alternatives:

  • Click the dashboard icon at the top of the NAM Console screen
    NAM Console dashboard
    and click the Technical hierarchy tile
    NAM Console dashboard Technical Hierarchy
  • Open the NAM Console menu

    and select Monitoring ► Service, module and task.
  • On the NAM Server, in the Settings section, open APM model and select Services, modules and tasks


Before adding or editing a reporting hierarchy definition, you should be familiar with the Dynatrace reporting hierarchy concept. For more information, see Multi-level hierarchy reporting.

By default, the mapping definitions for several analyzers are already part of the NAM installation. They are uploaded to the NAM Server immediately after it is added to the NAM Console (provided you add a freshly installed NAM Server). Hierarchy definitions uploaded by the NAM Console always take precedence over the configuration existing on the report server.

You can edit the reporting hierarchy by importing it again and changing the mapping.

For a given application available in the deployment (based either on an analyzer group or a specific software service level), you can define only one reporting hierarchy.

Adding a reporting hierarchy definition

  1. In the NAM Console menu, select Monitoring ► Service, module and task.
  2. Click Add Reporting Hierarchy Definition.
  3. Use the Analyzer Group or Software Service radio button to choose whether to map the hierarchy for a specific software service or for an analyzer.
  4. Continue with Applying the new or modified definition.

Editing an existing reporting hierarchy definition

  1. In the NAM Console menu, select Monitoring ► Service, module and task.
  2. Click Edit in the row you want to edit.
  3. Review the Reporting Hierarchy Preview screen.
  4. Click the Modify Hierarchy button.
    When you are modifying an existing hierarchy, you cannot change the Analyzer Group or Software Service fields defined previously. The new mappings are automatically suggested to you based on the structures of currently and previously imported files.
  5. Continue with Applying the new or modified definition.

Applying the new or modified definition

  1. Browse for the file containing the reporting hierarchy of your application.
    The file has to be in CSV format.

  2. Select the delimiter type.

  3. Click Import to import the hierarchy.

  4. Click Next to proceed to mapping of the hierarchy.
    On the screen there is a preview of the imported file and a table where you map table headers from the file with operations, tasks, modules, and services.

  5. To map a specific column to a given hierarchy level, click the New Mapping table cell for that level and select the column from a list.

    • One application hierarchy level can be mapped to only one NAM level.
    • Mapping definitions for the operation name and task name levels are obligatory. The task step level is optional.
    • If you define mapping for a specific NAM level, you also have to provide mappings for all of its parent levels in the NAM hierarchy tree.
    • The columns that are not mapped to any level will not be included in NAM Server configuration.
    • If there is no named entity for a given level, it appears as an “All other” aggregate on the NAM Server reports.
  6. Click Next and review the results of the configuration.

  7. Click Next to define the automatic import settings.
    The automated reporting hierarchy import directory is located in the following NAM Console installation subdirectory:

    This directory is periodically scanned for changes. Automatic import of a hierarchy file is initiated if any change in the modification date is observed or if a new file with the name matching any of names declared in reporting hierarchy definitions is detected.

    The file format, CSV file delimiting character, and, for the SAP reporting hierarchy, the SAP hierarchy node types are those you specified in the edited reporting hierarchy configuration.

    If the current mapping contains application-specific hierarchy levels with identical names, or duplicated column names are detected in the imported file, the import operation is successful only if the required levels are found in the same positions (columns) as in the last manually imported file. If all currently mapped application-specific hierarchy level names are unique and the imported file also does not contain duplicate column names, the required levels can be in different positions (columns) than those in the last manually imported file.

  8. Click Finish.

The defined reporting hierarchy is automatically published on the master NAM Server if any of following events occurs:

  • A new reporting hierarchy definition is added.
  • The existing reporting hierarchy definition is modified or deleted.
  • The reporting hierarchy file is successfully imported as a result of automatic import.
  • The master NAM Server device changes.