Dynatrace Backend Integration
Introduction
The Dynatrace integration is an extension to Power Platform Monitoring which is based on OpenTelemetry.
The telemetry data will be sent to dynatrace right after being processed by KPI.
For further information and requirements see: https://docs.dynatrace.com/docs
The integration includes traces, logs and metrics:
Introduction Video
Chapter List: 00:00
Welcome and session overview 03:00
In-depth use case: Performance analysis 07:18
In-depth use case: Error Analysis 13:28
- Final thoughts
Open Telemetry
KPI supports the OTel standard to collect and provide telemetry data for dataverse internal executions of plugins, custom apis or any other kind of custom code paths.
See: https://opentelemetry.io/docs/specs/otel/overview/
Integration Setup
Requirements
Dynatrace API Access Token - https://docs.dynatrace.com/docs/extend-dynatrace/opentelemetry
Dataverse System Administrator - Integrations
Install AppSource Solution
Installation guide Install AppSource Solution
After the deployment process a configuration record must be created:
https://[ORG].crm.dynamics.com/main.aspx?forceUCI=1&newWindow=true&pagetype=entityrecord&etn=kpi_telemetryconfiguration
KPI Access Token: Retrieve the token from your KPI Instance. https://insights.kuppsoft.com/go/settings
Save the record.
Configure Integration
Login to https://insights.kuppsoft.com
Ensure Power Platform Monitoring is configured
Configure Dynatrace connection
Test
Trigger any action in dynamics
Review traces
Analyze Traces
Data Mapping
Dynamics | Dynatrace | Description |
---|---|---|
Business Event | Endpoint | e.g. Create Account |
Entity | Business Entity | Records in dataverse (e.g. account) |
Correlationid | TraceId | Unique ID for distributed traces |
Entry Point | Root Span | First action within a trace |
Execution | Trace | A trace contains multiple executions. |
Execution Context | Custom trace attribute | Kpi.Context - Contains all context and business data values |
Distributed Traces
Code spans are connected to other code execution paths, like asynchronous executions of additional workflows.
Arguments and Context specific parameters
Execution-specific arguments are automatically available.
Exceptions
All exceptions will be flagged and directly linked to the span/root cause.
Context propagation
Kpi supports Context propagation, that means a tracing context will be forwarded to external applications called by dataverse code:
Service Monitoring
For each dataverse event (endpoint), like “Update account” an endpoint overview shows all related events and metrics.
Dashboards & Reports
Custom dashboards are fully supported. Any span or custom logs like plugin trace logs are available via DQL.
Supported Components
Plugins
Code Activities
Dataverse Events
Custom API’s
Plugin Trace Logs
System Jobs Logs
Workflows
Cloud Flows
Limited Supported Components
3rd Party Solution
Licensing & Consumption
An enterprise subscription (Licensing ) is needed to use Open Telemetry.
For consumption monitoring see Tenant Settings .
Note: The costs for the Dynatrace Open Telemetry ingest must also be taken into account.
Resources
https://appsource.microsoft.com/en-us/product/dynamics-365/kuppsoft.kpiboservability?tab=Overview
https://www.dynatrace.com/hub/detail/microsoft-power-platform-observability/?query=kupp&filter=all
Troubleshooting / FAQ
This section is currently being updated, some topics may not yet be up to date