Integrate Dynatrace with basic authentication

  • Versão de lançamento: Australia
  • Atualizado 16 de jun. de 2026
  • 2 min. de leitura

    • Integrate Dynatrace with Event Management by adding a standard webhook in the Dynatrace console.

    Antes de Iniciar

    Ensure that the Event Management Connectors (sn_em_connector) plugin is installed on the ServiceNow AI Platform instance.

    Ensure that configuration items for the hosts managed by Dynatrace exist in the ServiceNow AI Platform instance. These CIs can be physical or virtual and can be either manually created or discovered via IP discovery or Cloud Discovery.

    Roles required: evt_mgmt_integration and web_service_admin

    Por Que e Quando Desempenhar Esta Tarefa

    Configure the Event Management environment for the collection of events from Dynatrace by authenticating Dynatrace as a data source. In your Dynatrace console, set your ServiceNow AI Platform instance as the rest endpoint using a standard webhook.

    Procedimento

    1. In your Dynatrace console, define Host Naming rules:
      1. Navigate to Settings > Monitoring > Host Naming.
      2. Define the Host Naming rules for each cloud provider (Azure/AWS/GCP) to uniquely identify a CI from ServiceNow.
      This ensures the ServiceNow CIs can be uniquely identified from the payload received from Dynatrace.
      Nota:
      You do not need to create a Host Naming rule for VMware machines because Dynatrace manages them as physical servers.
    2. Define anomaly detection rules:
      1. Navigate to Settings > Anomaly Detection > Infrastructure.
      2. In the Hosts tab, define rules on when to create alerts on the managed hosts.
    3. Define the integration settings:
      1. Navigate to Settings > Integration > Problem notifications > Add notifications.
      2. In the Set up custom integration form, add the Webhook URL: https://<instance-name>.service-now.com/api/sn_em_connector/em/inbound_event?source=dynatrace
        For basic authentication, select Create basic authorization header. You can see the username and password fields for the user.
      3. Enter the user name and password of the relevant user.
        Nota:
        Ensure the evt_mgmt_integration role is assigned to the selected user. To ensure proper authentication, use the least privileged user with the evt_mgmt_integration role, rather than a high privileged user.
      4. In the Custom payload section, add in the following payload structure for the events that will be generated. 
        { 
  "connectionId": <connections_alias_sys_id>,
  "ImpactedEntities": {ImpactedEntities}, 
  "ImpactedEntity": "{ImpactedEntity}", 
  "PID": "{PID}", 
  "ProblemDetailsHTML": "{ProblemDetailsHTML}", 
  "ProblemDetailsJSONv2": {ProblemDetailsJSONv2},  
  "ProblemDetailsMarkdown": "{ProblemDetailsMarkdown}", 
  "ProblemDetailsText": "{ProblemDetailsText}", 
  "ProblemID": "{ProblemID}", 
  "ProblemImpact": "{ProblemImpact}", 
  "ProblemSeverity": "{ProblemSeverity}", 
  "ProblemTitle": "{ProblemTitle}", 
  "ProblemURL": "{ProblemURL}", 
  "State": "{State}", 
  "Tags": "{Tags}" 
}
        Nota:
        For the <connections_alias_sys_id>:
        1. Navigate to All > IntegrationHub > Connection & Credentials > Connection & Credential Aliases.
        2. Select to open the connector for which you want to get the <connections_alias_sys_id>.
          Dynatrace connection aliases list.
        3. Right-click the context menu (menu icon) and then select Copy sys_id.
          sys_id of the connection.

    Resultado

    Alerts start flowing from the Dynatrace console into the Event Management plugin. The plugin extracts information from the original Dynatrace alert message to populate the required event fields and inserts the event into the database. In your ServiceNow AI Platform instance, navigate to All Events to see the events.

    Nota:
    By default, host binding is enabled for Dynatrace events for all providers (Azure/AWS/Google). If all hosts in the environment are discovered using Cloud Discovery by providing credentials and discovered resources are in the cmdb_ci_vm_object list, then the VM binding may not occur. To resolve this, you must enable the Dynatrace - General event rule. For further information about Event rules, see Event rules.