Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
APPLIES TO: Business Central 2020 release wave 2, version 17.2, and later
Configuration package telemetry gathers data about the following operations on configuration packages:
- Export
- Import
- Apply
- Delete
For information about working with configuration packages, see Prepare a Configuration Package in the Business Central Application Help.
These events come from AL application code. The application source uses the event ID without the AL prefix. For example, the source ID 0000E3N appears as AL0000E3N in Application Insights. Learn more in Find AL event IDs in the application source.
Common custom dimensions
The following table explains custom dimensions that are common to all configuration package traces.
| 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. |
| alCategory | RapidStart |
| alDataClassification | SystemMetadata |
| clientType | Specifies the type of client that executed the SQL Statement, such as Background or Web. For a list of the client types, see ClientType Option Type. Added in version 20.0. |
| companyName | The name of the company where the operation is applied. Added in version 20.0. |
| component | Dynamics 365 Business Central Server. |
| componentVersion | Specifies the version number of the component that emits telemetry (see the component dimension.) |
| 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. |
Configuration package export started
Occurs when an export operation on a configuration package is started.
General dimensions
| Dimension | Description or value |
|---|---|
| message | Configuration package export started: {packageSystemId} |
| severityLevel | 1 |
| user_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. Learn more in Assign a telemetry ID to users. |
Custom dimensions
| Dimension | Description or value |
|---|---|
| eventId | AL0000E3F |
| alExecutionId | Specifies the GUID that correlates the start and completion events for the export operation. |
| alPackageCode | Specifies the system ID (GUID) of the configuration package being exported. The dimension name is retained for compatibility. |
| See common custom dimensions |
Configuration package exported successfully
Occurs when an export operation on a configuration package completes successfully.
General dimensions
| Dimension | Description or value |
|---|---|
| message | Configuration package exported successfully: {packageSystemId} |
| severityLevel | 1 |
| user_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. Learn more in Assign a telemetry ID to users. |
Custom dimensions
| Dimension | Description or value |
|---|---|
| eventId | AL0000E3G |
| alExecutionId | Specifies the GUID that correlates the start and completion events for the export operation. |
| alExecutionTimeInMs | Specifies the number of milliseconds it took to complete the export operation. |
| alPackageCode | Specifies the system ID (GUID) of the configuration package that was exported. The dimension name is retained for compatibility. |
| See common custom dimensions |
Configuration package import started
Occurs when an import operation on a configuration package is started.
General dimensions
| Dimension | Description or value |
|---|---|
| message | Configuration package import started: {packageSystemId} |
| severityLevel | 1 |
| user_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. Learn more in Assign a telemetry ID to users. |
Custom dimensions
| Dimension | Description or value |
|---|---|
| eventId | AL0000E3H |
| alExecutionId | Specifies the GUID that correlates the start and completion events for the import operation. |
| See common custom dimensions |
Configuration package imported successfully
Occurs when an import operation on a configuration package completes successfully.
General dimensions
| Dimension | Description or value |
|---|---|
| message | Configuration package imported successfully: {packageSystemId} |
| severityLevel | 1 |
| user_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. Learn more in Assign a telemetry ID to users. |
Custom dimensions
| Dimension | Description or value |
|---|---|
| eventId | AL0000E3I |
| alExecutionTimeInMs | Specifies the number of milliseconds it took to complete the import operation. |
| alExecutionId | Specifies the GUID that correlates the start and completion events for the import operation. |
| alFileSizeInBytes | Specifies the approximate size of the imported XML content in bytes. |
| See common custom dimensions |
Configuration package apply started
Occurs when an apply operation on a configuration package is started.
General dimensions
| Dimension | Description or value |
|---|---|
| message | Configuration package apply started: {packageSystemId} |
| severityLevel | 1 |
| user_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. Learn more in Assign a telemetry ID to users. |
Custom dimensions
| Dimension | Description or value |
|---|---|
| eventId | AL0000E3N |
| alExecutionId | Specifies the GUID that correlates the start and completion events for the apply operation. |
| alPackageCode | Specifies the system ID (GUID) of the configuration package being applied. The dimension name is retained for compatibility. |
| See common custom dimensions |
Configuration package applied successfully
Occurs when an apply operation on a configuration package completes successfully.
General dimensions
| Dimension | Description or value |
|---|---|
| message | Configuration package applied successfully: {packageSystemId} |
| severityLevel | 1 |
| user_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. Learn more in Assign a telemetry ID to users. |
Custom dimensions
| Dimension | Description or value |
|---|---|
| eventId | AL0000E3O |
| alExecutionId | Specifies the GUID that correlates the start and completion events for the apply operation. |
| alExecutionTimeInMs | Specifies the number of milliseconds it took to complete the apply operation. |
| alErrorCount | Specifies the number of errors that occurred when applying the configuration package. |
| alFieldCount | Specifies the number of fields that were included in the migration table of the applied configuration package. |
| alPackageCode | Specifies the system ID (GUID) of the configuration package that was applied. The dimension name is retained for compatibility. |
| alRecordCount | Specifies the number of records that were included in the applied configuration package. |
| See common custom dimensions |
Configuration package deleted successfully
Occurs when a configuration package is deleted successfully.
General dimensions
| Dimension | Description or value |
|---|---|
| message | Configuration package deleted successfully: {packageSystemId} |
| severityLevel | 1 |
| user_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. Learn more in Assign a telemetry ID to users. |
Custom dimensions
| Dimension | Description or value |
|---|---|
| eventId | AL0000E3P |
| alPackageCode | Specifies the system ID (GUID) of the configuration package that was deleted. The dimension name is retained for compatibility. |
| See common custom dimensions |
Related information
Monitoring and Analyzing Telemetry
Enable Sending Telemetry to Application Insights
Prepare a Configuration Package in the Business Central
Telemetry event IDs in Application Insights