{"title":"Analyzing error method telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-error-method-trace/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-error-method-trace, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-error-method-trace","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Analyze error dialog telemetry in Business Central to investigate AL errors, inspect stack traces and failure reasons, and identify problems affecting users.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyzing error method telemetry","slug":"analyzing-error-method-telemetry","at":0,"chars":5889},{"level":2,"title":"Error dialog displayed","slug":"error-dialog-displayed","at":488,"chars":4754},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":638,"chars":329},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":967,"chars":2825},{"level":3,"title":"Sample KQL code (error dialogs)","slug":"sample-kql-code-error-dialogs","at":3792,"chars":1450},{"level":2,"title":"Understanding the error dialog","slug":"understanding-the-error-dialog","at":5242,"chars":288},{"level":2,"title":"Related information","slug":"related-information","at":5530,"chars":359}],"text":"# Analyzing error method telemetry\n> APPLIES TO: Business Central 2022 release wave 1 and later\nWhen a user gets an error dialog while working in Business Central, a telemetry signal is emitted, which can be logged in an Azure Application Insights resource.\nThis telemetry data lets you identify and analyze calls to the Error method from AL code and errors raised by the platform. You can also set up alerts in Azure Application Insights to get notified if many users experience errors.\n## Error dialog displayed\nOccurs when an error is sent to the client for display, including errors raised by the AL Error method and by the platform.\n### General dimensions\nDimension|Description or value\nmessage|Error dialog shown: {failureReason}\nseverityLevel|3\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\nDimension|Description or value\neventId|RT0030\nalErrorMessage|The error message, with private information removed.<br><br>For calls to `Error(String)`, the error string from AL code is shown only if the string is a Label or TextConst data type. For other nonempty strings, `Use ERROR with a text constant to improve telemetry details` is shown instead. Substitution values aren't included in the diagnostic text.<br><br>Messages from `Error(ErrorInfo)` are also subject to privacy filtering. Some messages can contain customer data. As a precaution, Business Central only emits information that's classified as SystemMetadata<../developer/devenv-instrument-application-for-telemetry-app-insights#using-dataclassification-for-privacy>. Information that belongs to other data classifications, like customer data, isn't shown. A redaction message is shown instead.\nalDetailedErrorMessage|The detailed error message, with private information removed.\nalEnglishLanguageDiagnosticsMessage|The error message in English, regardless of the user's client language.<br /><br />This dimension is available in version 22.0 and was backported to version 21.4.\nalObjectId|Specifies the ID of the AL object.\nalObjectType|Specifies the type of the AL object.\nalStackTrace|The stack trace in AL.\nclientType|Specifies the type of client that opened the session, such as Background or Web. For a list of the client types, see ClientType Option Type<../developer/methods-auto/clienttype/clienttype-option>.\ncompanyName|The current company name.\nfailureReason|Dialog means the error was the result of an error method call in AL. Errors thrown by the platform have other reasons, like MetadataNotFound.\nCommon custom dimensions\nThe following table explains other custom dimensions that are common to all error telemetry.\nDimension|Description or value\naadTenantId|The Microsoft Entra tenant ID that's used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|The version number of the component that emits telemetry (see the component dimension)\nenvironmentName|The name of the tenant environment. This dimension isn't included for Business Central on-premises environments. See Managing environments<tenant-admin-center-environments>.\nenvironmentType|The environment type for the tenant, such as Production, Sandbox, Trial. See tenant-admin-center-environments#types-of-environments.\nextensionName|Specifies the name of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\nextensionId|Specifies the ID of the extension/app.\ntelemetrySchemaVersion|The version of the Business Central telemetry schema\n### Sample KQL code (error dialogs)\nThis KQL code can help you get started analyzing which error dialogs users see:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions.eventId == 'RT0030'\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// in which extension/app\n, extensionId = customDimensions.extensionId\n, extensionName = customDimensions.extensionName\n, extensionVersion = customDimensions.extensionVersion\n, extensionPublisher = customDimensions.extensionPublisher\n// in which object\n, alObjectId = customDimensions.alObjectId\n, alObjectName = customDimensions.alObjectName\n, alObjectType = customDimensions.alObjectType\n// which user got the error\n, usertelemetryId = case(\n  toint( substring(customDimensions.componentVersion,0,2)) >= 20, user_Id // user telemetry id was introduced in the platform in version 20.0\n, 'N/A'\n)\n// error information\n, clientType = customDimensions.clientType\n, errorMessageInUsersLanguage = customDimensions.alErrorMessage\n, errorMessageInEnglish = customDimensions.alEnglishLanguageDiagnosticsMessage // Available in version 22.0 and backported to version 21.4.\n, alStackTrace = customDimensions.alStackTrace\n, failureReason = customDimensions.failureReason\n```\n## Understanding the error dialog\nTo effectively help users mitigate any issues they might encounter, we recommend learning about the different parts of the error dialog, including how to interpret the AL stack trace. See Understanding the error dialog<../developer/devenv-error-dialog>.\n## Related information\n../developer/methods-auto/dialog/dialog-error-errorinfo-method\n../developer/methods-auto/dialog/dialog-error-string-joker-method\nUnderstanding the error dialog<../developer/devenv-error-dialog>\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>"}