Managing deprecated Dynatrace integrations

Dynatrace is a software intelligence platform based on artificial intelligence to monitor and optimize application performance and development, IT infrastructure, and user experience. 

As a tenant administrator, you can edit a deprecated integration. However, you cannot configure new instances of the integration. We recommend that you use BMC Helix Intelligent Integrations to configure new instances. For more information, see Integrating-with-Dynatrace-via-API.

Related topics

Supported-out-of-the-box-integrations-for-BMC-Helix-Developer-Tools

Enabling-disabling-or-deleting-integrations

Troubleshooting-the-connector-configuration-issues


Important: Event messages in Dynatrace and BMC Helix Operations Management appear different

  • An event message in BMC Helix Operations Management might appear different from the message for the same event in Dynatrace . This situation happens in the case of events that are not sent by third-party tools to Dynatrace . For such events, Dynatrace  does not add a message.
  • In BMC Helix Operations Management , events cannot appear without a message. When a Dynatrace event without a message arrives in BMC Helix Operations Management , the event is appended with an appropriate message in  BMC Helix Operations Management . Therefore, such events appear different in BMC Helix Operations Management and Dynatrace .

As a tenant administrator, perform the following steps to edit and validate the integrations configured with Dynatrace . 

Before you begin

The Dynatrace  host must be accessible from your docker-enabled Linux server.


To edit a Dynatrace integration

  1. From BMC Helix Developer Tools, open the Configured Integrations tab if the tab does not open by default.This tab shows deprecated Dynatrace integrations and all other configured integrations. The following example shows the tile for a deprecated Dynatrace integration:  

    deprecated_dynatrace_integration.png
    The tile shows the following information:

    • The name of the integration with its build number.
    • The incoming data. In this example, 5,046 CIs and 36 events have been received.
    • The name of the user who modified the integration along with the time of the modification. In this example, it is the admin user.
    • The connector status. In this example, the status is Active.
  2. On the deprecated Dynatrace integration that you want to edit, select Edit from the actions menu configuremenu_icon.png.
  3. Optionally, edit the following source details:
    • Integration name

    • API URL

      How do I obtain the API URL?

      To obtain this URL, in the Dynatrace console, select Settings > Public endpoints . You can see the URL as shown in the following image:

      dynatrace_public_endpoint.png
       
      The highlight text in the following image represents the API URL:

      dynatrace_api_url.png

    • Dynatrace environment ID

      How do I obtain the environment ID?

      This is the host ID of the server where you have installed Dynatrace . For example, in the following image, the highlighted text in the following URL represents the environment ID:

      dynatrace_env_id.png

    • Dynatrace API token

      How do I generate the API token?

      In the Dynatrace  console, generate an API token:

      1. Select SaaS-ops-services environment > Settings > Integration > Dynatrace API.
      2. Click Generate token.

      3. Copy the token.

        Important

        You see this token only while you are generating it. Ensure that you copy it immediately. After you navigate away from this page, the token is not visible.

        For more information, see the Dynatrace documentation.

    • Entity types (Events and CIs) to import
  4. In the Customize Entity Configuration section, click Configure  and edit the following advanced settings for the entities that you have selected in the previous step:
    • Events: Specify the refresh time for events in seconds. By default, the refresh time is set to 60 seconds.
    • CIs:  Specify the refresh time for CIs in hours. By default, the refresh time is set to 24 hours.
  5. Click Update.
    On the Configured Integrations  tab, the status of the integration changes to CONFIGURING. After the integration is configured completely, the status changes to CONNECTED .


To validate the Dynatrace integration

  • Ensure that the status of the integration is CONNECTED.

  • From BMC Helix Operations Management, go to Events to ensure that you can see the events in BMC Helix Operations Management.
    For more information, see Monitoring and managing events .

  • From  BMC Helix Discovery, go to Explore > Data, and then click <count> Import Records in the Miscellaneous section to ensure that you can see the records from the source (host) in BMC Helix Discovery. Use these records further to create a business service model for the source depending on your use case requirements in BMC Helix AIOps . For more information, see Managing models .


Dynatrace event class

The following event class is created in BMC Helix Operations Management to display the Dynatrace data:

  • DynatraceEvent
    • Parent class name: EVENT

    • Attributes

      The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.


Dynatrace event slot mappings

The following table shows the event slot mappings between Dynatrace and BMC Helix Operations Management .

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*