{"title":"Analyze configuration package telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-configuration-package-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-configuration-package-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-configuration-package-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":"Learn about the telemetry for configuration package telemetry for Azure Application Insights.","date":"2026-09-22","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyze configuration package telemetry","slug":"analyze-configuration-package-telemetry","at":0,"chars":8359},{"level":2,"title":"Common custom dimensions","slug":"common-custom-dimensions","at":695,"chars":1140},{"level":2,"title":"Configuration package export started","slug":"configuration-package-export-started","at":1835,"chars":826},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":1946,"chars":349},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":2295,"chars":366},{"level":2,"title":"Configuration package exported successfully","slug":"configuration-package-exported-successfully","at":2661,"chars":956},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":2791,"chars":356},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":3147,"chars":470},{"level":2,"title":"Configuration package import started","slug":"configuration-package-import-started","at":3617,"chars":684},{"level":3,"title":"General dimensions","slug":"general-dimensions-2","at":3728,"chars":349},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-2","at":4077,"chars":224},{"level":2,"title":"Configuration package imported successfully","slug":"configuration-package-imported-successfully","at":4301,"chars":900},{"level":3,"title":"General dimensions","slug":"general-dimensions-3","at":4431,"chars":356},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-3","at":4787,"chars":414},{"level":2,"title":"Configuration package apply started","slug":"configuration-package-apply-started","at":5201,"chars":821},{"level":3,"title":"General dimensions","slug":"general-dimensions-4","at":5310,"chars":348},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-4","at":5658,"chars":364},{"level":2,"title":"Configuration package applied successfully","slug":"configuration-package-applied-successfully","at":6022,"chars":1282},{"level":3,"title":"General dimensions","slug":"general-dimensions-5","at":6150,"chars":355},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-5","at":6505,"chars":799},{"level":2,"title":"Configuration package deleted successfully","slug":"configuration-package-deleted-successfully","at":7304,"chars":721},{"level":3,"title":"General dimensions","slug":"general-dimensions-6","at":7411,"chars":355},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-6","at":7766,"chars":259},{"level":2,"title":"Related information","slug":"related-information","at":8025,"chars":334}],"text":"# Analyze configuration package telemetry\nAPPLIES TO: Business Central 2020 release wave 2, version 17.2, and later\nConfiguration package telemetry gathers data about the following operations on configuration packages:\n Export\n Import\n Apply\n Delete\nFor information about working with configuration packages, see Prepare a Configuration Package<set-up-standard-company-configuration-packages> in the Business Central Application Help.\nThese 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. See telemetry-event-ids#find-al-event-ids-in-the-application-source.\n## Common custom dimensions\nThe following table explains custom dimensions that are common to all configuration package traces.\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.\nalCategory|RapidStart\nalDataClassification|SystemMetadata\nclientType|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<../developer/methods-auto/clienttype/clienttype-option>. Added in version 20.0.\ncompanyName|The name of the company where the operation is applied. Added in version 20.0.\ncomponent|Dynamics 365 Business Central Server.\ncomponentVersion|Specifies the version number of the component that emits telemetry (see the component dimension.)\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## Configuration package export started\nOccurs when an export operation on a configuration package is started.\n### General dimensions\nDimension|Description or value\nmessage|Configuration package export started: {packageSystemId}\nseverityLevel|1\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\n|Dimension|Description or value|\n|eventId|AL0000E3F|\n|alExecutionId|Specifies the GUID that correlates the start and completion events for the export operation.|\n|alPackageCode|Specifies the system ID (GUID) of the configuration package being exported. The dimension name is retained for compatibility.|\n|See common custom dimensions<#other>||\n## Configuration package exported successfully\nOccurs when an export operation on a configuration package completes successfully.\n### General dimensions\nDimension|Description or value\nmessage|Configuration package exported successfully: {packageSystemId}\nseverityLevel|1\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\n|Dimension|Description or value|\n|eventId|AL0000E3G|\n|alExecutionId|Specifies the GUID that correlates the start and completion events for the export operation.|\n|alExecutionTimeInMs|Specifies the number of milliseconds it took to complete the export operation.|\n|alPackageCode|Specifies the system ID (GUID) of the configuration package that was exported. The dimension name is retained for compatibility.|\n|See common custom dimensions<#other>||\n## Configuration package import started\nOccurs when an import operation on a configuration package is started.\n### General dimensions\nDimension|Description or value\nmessage|Configuration package import started: {packageSystemId}\nseverityLevel|1\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\n|Dimension|Description or value|\n|eventId|AL0000E3H|\n|alExecutionId|Specifies the GUID that correlates the start and completion events for the import operation.|\n|See common custom dimensions<#other>||\n## Configuration package imported successfully\nOccurs when an import operation on a configuration package completes successfully.\n### General dimensions\nDimension|Description or value\nmessage|Configuration package imported successfully: {packageSystemId}\nseverityLevel|1\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\n|Dimension|Description or value|\n|eventId|AL0000E3I|\n|alExecutionTimeInMs|Specifies the number of milliseconds it took to complete the import operation.|\n|alExecutionId|Specifies the GUID that correlates the start and completion events for the import operation.|\n|alFileSizeInBytes|Specifies the approximate size of the imported XML content in bytes.|\n|See common custom dimensions<#other>||\n## Configuration package apply started\nOccurs when an apply operation on a configuration package is started.\n### General dimensions\nDimension|Description or value\nmessage|Configuration package apply started: {packageSystemId}\nseverityLevel|1\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\n|Dimension|Description or value|\n|eventId|AL0000E3N|\n|alExecutionId|Specifies the GUID that correlates the start and completion events for the apply operation.|\n|alPackageCode|Specifies the system ID (GUID) of the configuration package being applied. The dimension name is retained for compatibility.|\n|See common custom dimensions<#other>||\n## Configuration package applied successfully\nOccurs when an apply operation on a configuration package completes successfully.\n### General dimensions\nDimension|Description or value\nmessage|Configuration package applied successfully: {packageSystemId}\nseverityLevel|1\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\n|Dimension|Description or value|\n|eventId|AL0000E3O|\n|alExecutionId|Specifies the GUID that correlates the start and completion events for the apply operation.|\n|alExecutionTimeInMs|Specifies the number of milliseconds it took to complete the apply operation.|\n|alErrorCount|Specifies the number of errors that occurred when applying the configuration package.|\n|alFieldCount|Specifies the number of fields that were included in the migration table of the applied configuration package.|\n|alPackageCode|Specifies the system ID (GUID) of the configuration package that was applied. The dimension name is retained for compatibility.|\n|alRecordCount|Specifies the number of records that were included in the applied configuration package.|\n|See common custom dimensions<#other>||\n## Configuration package deleted successfully\nOccurs when a configuration package is deleted successfully.\n### General dimensions\nDimension|Description or value\nmessage|Configuration package deleted successfully: {packageSystemId}\nseverityLevel|1\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\n|Dimension|Description or value|\n|eventId|AL0000E3P|\n|alPackageCode|Specifies the system ID (GUID) of the configuration package that was deleted. The dimension name is retained for compatibility.|\n|See common custom dimensions<#other>||\n## Related information\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>\nPrepare a Configuration Package<set-up-standard-company-configuration-packages> in the Business Central\nTelemetry event IDs in Application Insights<telemetry-event-ids>"}