• Skip to primary navigation
  • Skip to main content
  • Skip to footer
  • Skip to custom navigation
HaloPSA

HaloPSA

  • Features
  • Pricing
  • Integrations
  • Resources
    • Demo On Demand
    • Roadmap
    • ITIL Alignment
    • Guides
    • HaloPSA Academy
    • Onboarding Partners
    • Distributors
  • Compare Us
    • ConnectWise
    • Datto Autotask
  • Solutions
    • I Need To…
      • Run My Business More Effectively

        Find out which customers and services are profitable and gain the confidence to act on this data.

      • Improve My Customer Experience

        Make all interactions as smooth as possible with a fully thought out end to end experience for your customers.

      • Streamline My Sales Process

        Remove unnecessary processes from your sales and account management and let them focus on their customer relationships.

      • Gain Control Of My Projects

        Visualise your workload and forecast your required budgets to ensure you can deliver on your projects.

    • We Are A…
      • Managed Service Provider
      • Telecommunications Provider
      • Cloud Solution Provider
      • Software Company
      • Consultancy Firm
    • Case Studies
      • nGeneration
      • Centrality
      • Commercial Managed IT
  • Start trial
  • Book demo

HaloPSA Guides

Documentation to assist with the setup and configuration of the HaloPSA platform

Guides > Dynatrace Integration

Dynatrace Integration


In this guide we will cover:

- Connecting to Dynatrace

- Site Mappings

- Host and Service Imports

- Alerting



The Dynatrace integration can be integrated with your Halo to allow the import of hosts and services, as well as for tickets to be created in Halo from Dynatrace alerts.


Connecting to Dynatrace

To use this integration you must generate an access token in Dynatrace with permission to read and write entities, and read and write problems. Please be aware that the URL you need to enter is not the same as the URL of your Dynatrace instance. 


Fig 1. Setup.


Site Mappings

Dynatrace does not have a concept of sites or customers, so to determine which site an asset should be created against you can use site rules. These rules are based on field values, and if matched will assign an asset to the site of the mapping.


Host and Service Imports

Most of the configuration is shared between the host and service imports. They use the same asset type mappings and matching field 

The asset types can either use a fixed type for all assets, be determined from one of the fields, or use asset type mappings that are determined using rules based on the values of the mapped asset fields.


If none of the rules are matched, a default asset type will be used, which can also be configured to not allow the import of any assets that don't match any of the rules, allowing for certain assets to be excluded from the import.


Fig 2. Host and service field mappings.


The field mappings are different between hosts and services, as they have different fields in Dynatrace.

Hosts and Services can be imported separately both manually and automatically via the integrator.


Additionally there are settings to deactivate assets deleted from Dynatrace, to not create new assets, to not update existing asset types, and to not change the site of existing assets.


Alerting

You can enable alert processing for the integration. This allows you to generate a username and password to use as basic authentication for the alert webhook.


The content of the webhook can be copied from the integration configuration. The values of some of the properties, like the title and details can be changed, but the default values should provide all the required information. 


Fig 3. Alert webhook.


The alerts are configured as problem notifications in Dynatrace with the type 'custom integration'. Alerts for problems with Hosts and Services will generate tickets in Halo.


If the problem is resolved in Dynatrace, then the ticket in Halo will be closed. Similarly, if the ticket in Halo is closed, then it will resolve the problem in Dynatrace, adding the closing note as a comment on the problem.


You can also specify the default user and ticket type for the tickets created from alerts.

Popular Guides

  • Asset Import - CSV/XLS/Spreadsheet Method
  • Call Management
  • Creating a New Application for API Connections
  • Creating Agents and Editing Agent Details
  • Departments and Teams
  • Halo Integrator
  • Importing Data
  • Multiple New Portals with different branding for one customer [Hosted]
  • NHServer Deprecation User Guide
  • Organisation Basics
  • Organising Teams of Agents
  • Step-by-Step Configuration Walk Through

Footer

Products

Company

  • Contact us
  • Events
  • Channel Partners
  • Technology Partners
  • Distributors
  • Referral Program

HaloPSA

  • Features
  • Integrations
  • Mobile Apps
  • Blog
  • Pricing

Key Features

  • Service Desk
  • Sales CRM
  • Billable Time Tracking
  • Reporting
  • Contracts
  • Billing
  • Stock Management
  • Projects

Compare PSA

  • ConnectWise
  • Datto Autotask
  • Accelo
  • Harmony PSA
  • Naverisk
  • Top Desk
  • Kaseya BMS
  • Atera
  • Freshservice

Social

  • Terms and Conditions
  • Privacy Policy
  • Security
  • GDPR
  • Modern Slavery Statement
We've moved!

Please visit our new website at USEHALO.COM/HALOPSA