Open Telemetry & Dynatrace

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

Configure

1. Login to https://insights.kuppsoft.com

2. Ensure Power Platform Monitoring is configured

3. Configure Dynatrace connection

3. Test

4. Trigger any action in dynamics

5. Review traces

Analyze Traces

Data Mapping

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 “create 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.

Roadmap

Resources

Troubleshooting / FAQ