This documentation supports the releases of BMC Helix Service Monitoring till September 2021 (21.3.03). Documentation for later versions is available in the BMC Helix AIOps documentation space. To view the documentation, select a version from the Product version menu.

Integrating with Dynatrace to monitor events and services


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, use BMC Helix Intelligent Integrations to add, edit, and delete Dynatrace integrations.

Related topic

Supported-out-of-the-box-integrations-for-BMC-Helix-Intelligent-Integrations

Enabling-disabling-or-deleting-integrations


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

An event message in BMC Helix Operations Management might appear different than the message for the same event in Dynatrace. This happens in case of events that are not sent by third-party tools to Dynatrace. For such events, Dynatrace does not add any 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.

Before you begin

Ensure that you have downloaded and installed the Connector. You must choose the Base Connector connector type while downloading the connector. Without the Connector, you cannot proceed with the integration.

Important
  • Download the script on a docker-enabled Linux server.
  • The Dynatrace host must be accessible from your docker-enabled Linux server.


To integrate with Dynatrace

  1. Go to BMC Helix Intelligent Integrations > Available integrations tab if the tab does not open by default.
  2. On the Dynatrace tile, click Configure.

    dynatrace_tile.png

    On this tile, you can also view the build number of the product and the name of the entity who made the product available for configuration.

  3. Enter the following source details:
    dynatrace_integ.png


    • Integration Name: Provide a name for the integration.
    • Select Connector: Select a Connector. If no Connector is available, click the Add Connector icon add_connector_icon.pngto download and install a Connector.

    • API URL: Enter the URL of the tenant.

      How do I obtain the API URL?

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

      dynatrace_public_endpoint.png

      The highlight in the following image also shows the API URL:

      dynatrace_api_url.png

    • Environment ID: Enter the 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 environment ID is highlighted:

      dynatrace_env_id.png

    • API-Token: Enter the Dynatrace API token. To generate this token, in the Dynatrace console, go to Settings > API tokens and copy the token from the API token field.

      How do I generate the API token?

      In the Dynatrace console, generate an API token:

      1. Navigate to 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 right away. After you navigate away from this page, the token is not visible.

        For more information, see the Dynatrace documentation.

    • Select entities to be registered: Select one or all of the available entities.
  4. In the Customize Entity Configuration section, configure the advanced settings for the entities that you have selected in the previous step. You will see the Configure option for the selected entity types as shown below:
    dynatrace_entity_config.png
    To configure the advanced settings, do the following steps:
    1. Click Configure.
    2. Based on the entity type selected, configure the following settings:
      • Event: Specify the refresh time for events in seconds. By default, the refresh time is set to 60 seconds.
      • CI: Specify the refresh time for CIs in hours. By default, the refresh time is set to 24 hours.
      • Metric: Configure the following settings:
        1. Specify the refresh time for metrics in minutes. By default, the refresh time is set to 10 minutes.

        2. Specify the metric type that you want to monitor. The following section displays a complete list of metric types: 

          Metric types
          • APPLICATION
          • APPLICATION_METHOD
          • APPLICATION_METHOD_GROUP
          • AUTO_SCALING_GROUP
          • AWS_APPLICATION_LOAD_BALANCER
          • AWS_AVAILABILITY_ZONE
          • AWS_CREDENTIALS
          • AWS_LAMBDA_FUNCTION
          • AWS_NETWORK_LOAD_BALANCER
          • AZURE_API_MANAGEMENT_SERVICE
          • AZURE_APPLICATION_GATEWAY
          • AZURE_APP_SERVICE_PLAN
          • AZURE_COSMOS_DB
          • AZURE_CREDENTIALS
          • AZURE_EVENT_HUB
          • AZURE_EVENT_HUB_NAMESPACE
          • AZURE_FUNCTION_APP
          • AZURE_IOT_HUB
          • AZURE_LOAD_BALANCER
          • AZURE_MGMT_GROUP
          • AZURE_REDIS_CACHE
          • AZURE_REGION
          • AZURE_SERVICE_BUS_NAMESPACE
          • AZURE_SERVICE_BUS_QUEUE
          • AZURE_SERVICE_BUS_TOPIC
          • AZURE_SQL_DATABASE
          • AZURE_SQL_ELASTIC_POOL
          • AZURE_SQL_SERVER
          • AZURE_STORAGE_ACCOUNT
          • AZURE_SUBSCRIPTION
          • AZURE_TENANT
          • AZURE_VM
          • AZURE_VM_SCALE_SET
          • AZURE_WEB_APP
          • BOSH_DEPLOYMENT
          • BROWSER
          • CINDER_VOLUME
          • CLOUD_APPLICATION
          • CLOUD_APPLICATION_INSTANCE
          • CLOUD_APPLICATION_NAMESPACE
          • CONTAINER_GROUP
          • CONTAINER_GROUP_INSTANCE
          • CUSTOM_APPLICATION
          • CUSTOM_DEVICE
          • CUSTOM_DEVICE_GROUP
          • DATASTORE
          • DEVICE_APPLICATION_METHOD
          • DEVICE_APPLICATION_METHOD_GROUP
          • DISK
          • DOCKER_CONTAINER_GROUP
          • DOCKER_CONTAINER_GROUP_INSTANCE
          • DYNAMO_DB_TABLE
          • EBS_VOLUME
          • EC2_INSTANCE
          • ELASTIC_LOAD_BALANCER
          • EXTERNAL_SYNTHETIC_TEST
          • EXTERNAL_SYNTHETIC_TEST_STEP
          • GCP_ZONE
          • GEOLOCATION
          • GEOLOC_SITE
          • GOOGLE_COMPUTE_ENGINE
          • HOST
          • HOST_GROUP
          • HTTP_CHECK
          • HTTP_CHECK_STEP
          • HYPERVISOR
          • HYPERVISOR_CLUSTER
          • HYPERVISOR_DISK
          • KUBERNETES_CLUSTER
          • KUBERNETES_NODE
          • MOBILE_APPLICATION
          • NETWORK_INTERFACE
          • NEUTRON_SUBNET
          • OPENSTACK_AVAILABILITY_ZONE
          • OPENSTACK_COMPUTE_NODE
          • OPENSTACK_PROJECT
          • OPENSTACK_REGION
          • OPENSTACK_VM
          • OS
          • PROCESS_GROUP
          • PROCESS_GROUP_INSTANCE
          • QUEUE
          • QUEUE_INSTANCE
          • RELATIONAL_DATABASE_SERVICE
          • S3BUCKET
          • SERVICE
          • SERVICE_INSTANCE
          • SERVICE_METHOD
          • SERVICE_METHOD_GROUP
          • SWIFT_CONTAINER
          • SYNTHETIC_LOCATION
          • SYNTHETIC_TEST
          • SYNTHETIC_TEST_STEP
          • VCENTER
          • VIRTUALMACHINE
          • VMWARE_DATACENTER
    3. Click Save.
  5. Click Configure to configure the integration.
    You can view the added integration from Integrations > Configured Integrations. 
    You can also see the data being received and view the following details on the integration tile:

    dynatrace_connected.png

    • Name of the integration with its build number
    • The incoming data. In this example, 5,046 CIs and 36 events are ingested.
    • 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.


To validate the Dynatrace integration

Perform the following actions to validate the integration:

  • Ensure that the status of the integration is Connected. The following statuses are also valid:
    • Configuring
    • Disabled
    • Disconnected

  • Go to 

    BMC Helix Operations Management

     > Events to ensure that you can see events in BMC Helix Operations Management.
    For more information, see Event monitoring.

  • Ensure that you can see data in the following applications:


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


Dynatrace event slot mapping


Frequently asked questions on the Dynatrace integration

This section provides answers to frequently asked questions.

Why can't I see all the entities in BMC Helix Service Monitoring?

In BMC Helix Service Monitoring, you can see only business services. To view all entities other than business services, go to the BMC Helix Discovery console. You can cross launch to BMC Helix Discovery from the BMC Helix Service Monitoring console. For example, to check the list of imported Configuration Items (CIs), do the following steps:

  1. In the BMC Helix Discovery console, from the main menu, select Explore > Data.
    The Infrastructure page opens. This page lists the total number of each kind of infrastructure item in the system, as well as any infrastructure objects assigned to you. It also displays a list of infrastructure-related reports.

  2. To view a list of CIs, under the Miscellaneous section, click <Count> Import Records.
    A list of CIs is displayed. For more information about how to search or filter these infrastructure items, see Managing your IT infrastructure.

  3. Click any Dynatrace CI from the list to display the View Object page, which lists the attributes of the object and its relationships with other objects. For more information about the attribute mappings, see ImportRecord and for more information on steps to modeling the services, see Start anywhere application modeling.

Why do I see a difference between the number of entities available in the third-party solution and the number of entities fetched in BMC Helix Service Monitoring?

After the specified time interval, BMC Helix Service Monitoring fetches all CIs and event data from the third-party products, even if the data is already fetched in the previous cycle. Therefore, the CIs and events fetched in BMC Helix Service Monitoring appear to be more than the number of CIs and events present in the third-party product. This situation causes no impact on performance.

Why are the Dynatrace events missing if the integration was disabled for more than three days?

By default, the BMC Helix Intelligent Integrations collects the historical event data for the last three days (72 hours) only from Dynatrace. If you disable the Dynatrace integration and enable it after three days, the maximum historical event data collected is available only for the last three days. For example, If you disabled the integration on July 10th, enabled it on July 20th, you will see the historical data is from July 17th to July 20th only (for the last three days or 72 hours). Any historical event data before the last three days is not collected.

Why am I not seeing the host details for the services imported from Dynatrace?

The services imported from the Dynatrace metrics pipeline are not associated with their corresponding host details. Hence, the Dynatrace APIs do not provide the host data associated with the service to BMC Helix Intelligent Integrations.

 

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