Content

Introduction

The Monitoring feature provides obervability during actions within the D365 systems. Individual components can be analysed for their runtime performance to identify any parts that may slow down the system.

Enable Tracing

Step 1: In order to start tracing, select a component and press the start button.

Step 2: After a few seconds, KPI will start listening.

Step 3: Now trigger any actions that should be traced. For example - create an account.

Step 4: KPI will now show results of the tracing. The results include every code line executed, bottlenecks in the code base (highlighted by bold font), time of execution and execution statistics.

Step 5: Click on a single entry point to view the detailed stack.

The source code of a selected line can be viewed by clicking on the icon.

Step 6: Open the execution statistics () to view the details of single entry points.

Step 7: Click on pause to stop tracing.

Code Signing

In order to be able to execute the Performance Profiling, a code signing certificate must be uploaded to KPI. To do that, the button “Upload Code Signing“ must be clicked. A file selection dialog will open.

Select the certificate that is used to sign the assemblies.

The used certificate types are SNK files (*.snk). Based on the signing algorithm used when creating the assembly files, the type of the certificate might change.

Clear Traces

The clear traces button clears the history of all traced lines in the Performance Profiling section.

Filter

The option “Skip fast calls“ excludes operations that were faster than 100 milliseconds in execution time.

The option “Own code only“ excludes lines of code that are not directly written as custom code in a plugin.

The option “Collect arguments“ enables KPI to collect execution arguments and shows them at each line.

The “Custom filter“ lets the user narrow down which lines should be shown during the tracing.

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/

Dynatrace

Dynatrace could be used as a storage location for telemetry data. For further information and requirements see: https://docs.dynatrace.com/docs

Configuration: Integrations

Distributed Traces

Code spans are connected to other code exection paths, like asynchronous executions of addtional workflows.

Context

Execution specific arguments are automatically available.

Exceptions

All exceptions will be flaged and directly linked to the span/root cause.

Service Monitoring

For each dataverse event (endpoint), like “create account” an endpoint overview shows all related events and metrics.

Dashboards & Reports

Custom dashboard are fully supported. Any span or custom logs like plugin trace logs are available via DQL.