{"title":"Analyzing verbose telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-verbose-logging-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-verbose-logging-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-verbose-logging-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 verbose logging telemetry in Business Central to see when additional logging starts and ends for a session while troubleshooting user problems.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyzing verbose telemetry","slug":"analyzing-verbose-telemetry","at":0,"chars":3631},{"level":2,"title":"Verbose telemetry enabled for session","slug":"verbose-telemetry-enabled-for-session","at":660,"chars":1371},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":836,"chars":274},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":1110,"chars":921},{"level":2,"title":"Verbose telemetry disabled for session","slug":"verbose-telemetry-disabled-for-session","at":2031,"chars":1435},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":2270,"chars":275},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":2545,"chars":921},{"level":2,"title":"Related information","slug":"related-information","at":3466,"chars":165}],"text":"# Analyzing verbose telemetry\n> APPLIES TO: Business Central 2022 release wave 1 and later\nBusiness Central users can temporarily set up their session to emit more verbose telemetry by going to the Help and Support page in the client and selecting Additional Logging. They'll typically only do this when asked by a partner or support representative to help troubleshoot problems. This additional logging applies to the current session for 15 minutes. It doesn't enable verbose logging for other users.\nA telemetry trace is recorded whenever additional logging is turned on or off.\nSee Resources for Help and Support</product-help-and-support#troubleshooting>.\n## Verbose telemetry enabled for session\nOccurs when additional logging is turned on from the Help and Support page in the client or by an AL call to enable verbose telemetry.\n### General dimensions\nThe following table explains the general dimensions included in the trace. The table lists the dimensions that are specific to Business Central.\nDimension|Description or value\nmessage|Verbose telemetry enabled for session: {sessionId}\nseverityLevel|1\n### Custom dimensions\nThe following table explains the custom dimensions included in the trace.\nDimension|Description or value\naadTenantId|Specifies the Microsoft Entra tenant ID 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|Specifies the version number of the component that emits telemetry (see the component dimension.)\nenvironmentName|Specifies the name of the tenant environment. This dimension is only for traces from Business Central online. See Managing environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production, Sandbox, Trial. See tenant-admin-center-environments#types-of-environments.\neventId|RT0023\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Verbose telemetry disabled for session\nOccurs when the session's temporary verbose logging override is reset, including when its duration expires. This event doesn't specifically indicate that the user closed the browser or signed out.\n### General dimensions\nThe following table explains the general dimensions included in the trace. The table lists the dimensions that are specific to Business Central.\nDimension|Description or value\nmessage|Verbose telemetry disabled for session: {sessionId}\nseverityLevel|1\n### Custom dimensions\nThe following table explains the custom dimensions included in the trace.\nDimension|Description or value\neventId|RT0024\naadTenantId|Specifies the Microsoft Entra tenant ID 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|Specifies the version number of the component that emits telemetry (see the component dimension.)\nenvironmentName|Specifies the name of the tenant environment. This dimension is only for traces from Business Central online. See Managing environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production, Sandbox, Trial. See tenant-admin-center-environments#types-of-environments.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Related information\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>"}