Troubleshooting with telemetry

Path: Development > Troubleshooting > Troubleshooting with telemetry · tier official · system platform · narrative reviewed (checked by Opus)

Overview

This section explains how to collect and use Business Central telemetry stored in Azure Application Insights. It covers online and on-premises deployments, and the steps run from enabling telemetry to analyzing it and acting on it.

Start with “Monitoring and Analyzing Telemetry” for the overview, then “Turn sending telemetry to application insights on or off” to configure connection strings or instrumentation keys for the server, admin center, or individual tenants. “Available Telemetry” lists events by event ID (application, client, lifecycle, runtime), so you know what data you can query.

To analyze data, use the free Power BI apps (usage, error, performance, administration reports) or write KQL queries against Application Insights. “Alert on Telemetry” shows how to raise alerts, and “How to work with a performance problem” puts telemetry next to profilers and database analysis tools in a measure, locate, eliminate process.

Key points

• Telemetry is sent to Azure Application Insights, configured with a connection string or instrumentation key for the server, admin center, or individual tenants; on-premises setup is supported.
• Available Telemetry lists events by event ID in four groups: application, client, lifecycle, and runtime.
• Power BI apps for telemetry are free and open source, with usage, error, performance, and administration reports and sample data.
• KQL queries run against Application Insights tables such as traces and pageViews, using custom dimensions; examples cover report usage, session tracking, user activity, and timezone conversion.
• Alerts on telemetry can be built with Power BI Metrics, Application Insights alerts, Logic Apps, or Power Automate using KQL queries.
• Performance troubleshooting follows measure, locate bottlenecks, eliminate; tools include the scheduled and in-client performance profilers, AL Profiler, telemetry, missing indexes, and wait statistics.
• Telemetry can be enabled at environment level and app level, and apps can emit custom telemetry.

Learn pages

• Alert on Telemetry: Learn how to alert on Business Central telemetry.
• Analyze and monitor telemetry with KQL: Learn how to query Business Central telemetry with KQL.
• Analyze and monitor telemetry with Power BI: Learn how to install, configure, and use the Power BI app on Business Central telemetry data.
• Available Telemetry: Get an overview of available telemetry in Business Central
• How to work with a performance problem: Troubleshooting process that can help to guide you to find the root cause slow performance.
• Monitoring and Analyzing Telemetry: Learn how Business Central provides telemetry for each environment, both for online and on-premises environments.
• Turn sending telemetry to application insights on or off: Learn how you can get richer telemetry by connecting your Business Central with Application Insights for telemetry.

Videos and posts

Linked by a Haiku matcher with a grounding quote from the item’s summary (link/topics.ts); machine-generated.

• Client Crash? Check Error Dialog signal (community post): “telemetry is the way to investigate client crashes. Start from the operation id shown at the crash”
• Dynamics 365 Business Central Online Wait Statistics in Telemetry: the AI boost (community post): “AI can analyze exported wait statistics telemetry to provide performance insights”
• Use sqlServerSessionId to spot on blocking sessions in Dynamics 365 Business Central 2026 Wave 1 (community post): “Investigation workflow involves isolating lock timeouts, filtering lock snapshots”
• Analyzing BC Telemetry with AI with the “BC Telemetry Buddy” (community post): “BC Telemetry Buddy is a VSCode extension and Model Context Protocol tool”

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.