Analyzing Verbose Telemetry
APPLIES TO: Business Central 2022 release wave 1 and later
Note
Azure Active Directory is now Microsoft Entra ID. Learn more
Business Central users can temporarily set up their environment 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 will continue for 15 minutes or until the user closes the browser or signs out of Business Central—then it's turned off
A telemetry trace is recorded whenever additional logging is turned on or off.
For information about enabling additional logging, see Resources for Help and Support.
Verbose telemetry enabled for session
Occurs when additional logging is turned on from the Help and Support page in the client.
General dimensions
The following table explains the general dimensions included in the trace. The table lists the dimensions that are specific to Business Central.
| Dimension | Description or value |
|---|---|
| message | Verbose telemetry enabled for session: {sessionId} |
| severityLevel | 3 |
Custom dimensions
The following table explains the custom dimensions included in the trace.
| Dimension | Description or value |
|---|---|
| aadTenantId | 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. |
| component | Dynamics 365 Business Central Server |
| componentVersion | Specifies the version number of the component that emits telemetry (see the component dimension.) |
| environmentName | Specifies the name of the tenant environment. See Managing Environments. This dimension is only for traces from Business Central online. |
| environmentType | Specifies the environment type for the tenant, such as Production, Sandbox, Trial. See Environment Types |
| eventId | RT0023 |
| telemetrySchemaVersion | Specifies the version of the Business Central telemetry schema. |
Verbose telemetry disabled for session
Occurs when additional logging is turned off because a user closed the browser in which Business Central was running or they signed out of Business Central.
General dimensions
The following table explains the general dimensions included in the trace. The table lists the dimensions that are specific to Business Central.
| Dimension | Description or value |
|---|---|
| message | Verbose telemetry disabled for session: {sessionId} |
| severityLevel | 3 |
Custom dimensions
The following table explains the custom dimensions included in the trace.
| Dimension | Description or value |
|---|---|
| eventId | RT0024 |
| aadTenantId | 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. |
| component | Dynamics 365 Business Central Server |
| componentVersion | Specifies the version number of the component that emits telemetry (see the component dimension.) |
| environmentName | Specifies the name of the tenant environment. See Managing Environments. This dimension is only for traces from Business Central online. |
| environmentType | Specifies the environment type for the tenant, such as Production, Sandbox, Trial. See Environment Types |
| telemetrySchemaVersion | Specifies the version of the Business Central telemetry schema. |
See also
Monitoring and Analyzing Telemetry
Enable Sending Telemetry to Application Insights