Edit

Share via

Available telemetry

Microsoft Dynamics 365 Finance and Microsoft Dynamics 365 Supply Chain Management include robust, out-of-box telemetry capabilities when Application Insights is enabled. These capabilities provide critical insights into various aspects of the system and help customers monitor performance, diagnose issues, and optimize operations. This article provides an overview of the types of telemetry that are available and corresponding resources.

Form run telemetry

Form run telemetry captures detailed information about application forms. It provides insights into the following details:

  • Opened forms
  • Users who accessed the forms
  • Form load times

Use this data to:

  • Analyze average load times, P90 values, and other performance metrics to improve user experience.
  • Identify frequently accessed forms and optimize them for better usability.
  • Detect patterns in user behavior to enhance form design and navigation.
  • Monitor trends in form usage to prioritize resources and updates effectively.

Resources

X++ exceptions

The platform captures and logs all X++ layer exceptions to Application Insights. Use this telemetry to:

  • Monitor and diagnose errors to keep the app stable.
  • Track exception trends to spot recurring issues.
  • Prioritize fixes based on exception frequency and severity.
  • Analyze exception impact on user tasks and workflows.
  • Set alerts for specific exceptions in critical processes and spikes in overall exception trends for quick response.

Resources

Warehouse telemetry

The warehouse module generates telemetry data. The data shows the following telemetry:

  • Warehouse operations and workflows
  • Performance metrics to identify and fix bottlenecks

Use the provided Power BI dashboards to visualize the telemetry.

Resources

DMF errors

The Data Management Framework (DMF) logs errors to the Custom Events table in Application Insights. Exceptions that bubble up to the X++ layer go to the Exceptions table. Each logged error has an associated error code. For error code details, see Data management error descriptions and known limitations.

  • Identify and fix integration issues
  • Monitor data pipeline health

Batch telemetry (preview)

[This section is prerelease documentation and is subject to change.]

Important

  • This is a preview feature.
  • Preview features aren’t meant for production use and might have restricted functionality. These features are subject to supplemental terms of use, and are available before an official release so that customers can get early access and provide feedback.

Telemetry from the batch framework is logged to the CustomEvents table in your Azure Monitor Application Insights instance.

Note

  • This feature is in PU69/10.0.45 (build >= 7.0.7690.21) and backported to PU68/10.0.44 (build >= 7.0.7606.126).

To enable Batch telemetry, activate the following flights:

  • BatchTelemetryConfigurationFlight
  • BatchThreadInfoTelemetryFlight
  • BatchTelemetryCallstackFlight

After you enable the flights, new telemetry signals appear under the Configure tab:

  • Batch Start Time - Logs when a batch job starts.
  • Batch Stop Time - Logs when a batch job completes. Support duration tracking.
  • Batch Throttling - Captures throttling events and related system metrics (CPU, memory, SQL DTU).
  • Batch Failure - Adds diagnostic details when a batch job or task can't schedule. It complements existing Infolog errors by correlating telemetry with the originating batch job.
  • Batch Queue - Shows queue sizes for different queues in the priority-based scheduling framework.
  • Batch Threads - Shows active threads to help diagnose thread availability issues.

With batch telemetry, you can:

  • Diagnose performance and scheduling bottlenecks
  • Enable proactive monitoring through alerts and dashboards
  • Accelerate resolution of operational issues

Resources