{"title":"Analyzing changelog configuration changes telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-changelog-configuration-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-changelog-configuration-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-changelog-configuration-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 changelog configuration telemetry in Business Central to identify fields added to tracking, logging changes, and fields removed from tracking.","date":"2026-11-17","meta":{"topic":"reference"},"outline":[{"level":1,"title":"Analyzing changelog configuration changes telemetry","slug":"analyzing-changelog-configuration-changes-telemetry","at":0,"chars":9786},{"level":2,"title":"Field added to changelog configuration","slug":"field-added-to-changelog-configuration","at":860,"chars":2536},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":963,"chars":316},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":1279,"chars":975},{"level":3,"title":"Sample KQL code (field added)","slug":"sample-kql-code-field-added","at":2254,"chars":1142},{"level":2,"title":"Field logging changed in changelog configuration","slug":"field-logging-changed-in-changelog-configuration","at":3396,"chars":2954},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":3508,"chars":326},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":3834,"chars":1167},{"level":3,"title":"Sample KQL code (field logging changed)","slug":"sample-kql-code-field-logging-changed","at":5001,"chars":1349},{"level":2,"title":"Field removed from changelog configuration","slug":"field-removed-from-changelog-configuration","at":6350,"chars":2448},{"level":3,"title":"General dimensions","slug":"general-dimensions-2","at":6459,"chars":320},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-2","at":6779,"chars":1064},{"level":3,"title":"Sample KQL code (field removed)","slug":"sample-kql-code-field-removed","at":7843,"chars":955},{"level":2,"title":"Performance effect of enabling change logging on a table","slug":"performance-effect-of-enabling-change-logging-on-a-table","at":8798,"chars":716},{"level":2,"title":"Related information","slug":"related-information","at":9514,"chars":272}],"text":"# Analyzing changelog configuration changes telemetry\nINTRODUCED IN: Business Central 2023 release wave 2, version 23.0.\nThe Business Central changelog feature lets you track direct modifications a user makes to data in the database. You specify each table and field that you want the system to log, and then you activate the changelog. The changelog is based on changes that are made to data in the tables that you track.\nSee Auditing changes in Business Central</across-log-changes>.\nTelemetry is logged for the following changes to the configuration of the changelog:\n When a field is added to be tracked in the changelog.\n When changelog configuration for a field is changed.\n When a field is removed from tracking in the changelog.\nThese events use normal verbosity (severityLevel 1) and `TelemetryScope::All`. Their alCategory dimension is `Change Log`.\n## Field added to changelog configuration\nOccurs when a field is added to be tracked in the changelog.\n### General dimensions\nDimension|Description or value\nmessage|Field added to changelog configuration\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\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.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000LA2\nalTableNumber|Specifies the ID of the table where the changed field is included.\nalTableCaption|Specifies the name of the table where the changed field is included.\nalFieldNumber|Specifies the ID of the field to be logged.\nalFieldCaption|Specifies the name of the field to be logged.\nalLogInsertion|Are insertions logged? (Yes or No)\nalLogModification|Are data modifications logged? (Yes or No)\nalLogDeletion|Are deletions logged? (Yes or No)\n### Sample KQL code (field added)\nThis KQL code can help you get started analyzing change log telemetry for added fields or if you want to alert on these changes.\n```kql\n// Field added to change log configuration\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000LA2' // for performance\n| where customDimensions.eventId == 'AL0000LA2'\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// on which field in which table\n, alTableNumber = customDimensions.alTableNumber\n, alTableCaption = customDimensions.alTableCaption\n, alFieldNumber = customDimensions.alFieldNumber\n, alFieldCaption = customDimensions.alFieldCaption\n// what was the configuration change\n, alLogInsertion = customDimensions.alLogInsertion\n, alLogModification = customDimensions.alLogModification\n, alLogDeletion = customDimensions.alLogDeletion\n// which user made the configuration change\n, UsertelemetryId = user_Id\n```\n## Field logging changed in changelog configuration\nOccurs when changelog configuration for a field is changed.\n### General dimensions\nDimension|Description or value\nmessage|Field logging changed in changelog configuration\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\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.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000LA1\nalTableNumber|Specifies the ID of the table where the changed field is included.\nalTableCaption|Specifies the name of the table where the changed field is included.\nalFieldNumber|Specifies the ID of the field to be logged.\nalFieldCaption|Specifies the name of the field to be logged.\nalLogInsertion|Are insertions logged? (Yes or No)\nalLogInsertionOld|Were insertions logged before? (Yes or No)\nalLogModification|Are data modifications logged? (Yes or No)\nalLogModificationOld|Were data modifications logged before? (Yes or No)\nalLogDeletion|Are deletions logged? (Yes or No)\nalLogDeletionOld|Were deletions logged before? (Yes or No)\n### Sample KQL code (field logging changed)\nThis KQL code can help you get started analyzing change log telemetry for changed logging of fields or if you want to alert on these changes.\n```kql\n// Field logging changed in changelog configuration\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000LA1' // for performance\n| where customDimensions.eventId == 'AL0000LA1'\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// on which field in which table\n, alTableNumber = customDimensions.alTableNumber\n, alTableCaption = customDimensions.alTableCaption\n, alFieldNumber = customDimensions.alFieldNumber\n, alFieldCaption = customDimensions.alFieldCaption\n// what was the configuration change\n, alLogDeletion = customDimensions.alLogDeletion\n, alLogInsertionOld = customDimensions.alLogInsertionOld\n, alLogInsertion = customDimensions.alLogInsertion\n, alLogDeletionOld = customDimensions.alLogDeletionOld\n, alLogModification = customDimensions.alLogModification\n, alLogModificationOld = customDimensions.alLogModificationOld\n// which user made the configuration change\n, UsertelemetryId = user_Id\n```\n## Field removed from changelog configuration\nOccurs when a field is removed from tracking in the changelog.\n### General dimensions\nDimension|Description or value\nmessage|Field removed from changelog configuration\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\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.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|AL0000LA3\nalTableNumber|Specifies the ID of the table where the changed field is included.\nalTableCaption|Specifies the name of the table where the changed field is included.\nalFieldNumber|Specifies the ID of the field to no longer be logged.\nalFieldCaption|Specifies the name of the field to no longer be logged.\nalLogInsertion|Were insertions logged for the removed field? (Yes or No)\nalLogModification|Were data modifications logged for the removed field? (Yes or No)\nalLogDeletion|Were deletions logged for the removed field? (Yes or No)\n### Sample KQL code (field removed)\nThis KQL code can help you get started analyzing change log telemetry for removed fields or if you want to alert on these changes.\n```kql\n// Field removed from changelog configuration\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions has 'AL0000LA3' // for performance\n| where customDimensions.eventId == 'AL0000LA3'\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// on which field in which table\n, alTableNumber = customDimensions.alTableNumber\n, alTableCaption = customDimensions.alTableCaption\n, alFieldNumber = customDimensions.alFieldNumber\n, alFieldCaption = customDimensions.alFieldCaption\n// which user made the configuration change\n, UsertelemetryId = user_Id\n```\n## Performance effect of enabling change logging on a table\nThere's a performance overhead involved in having change log enabled on a table. First, there are extra writes to the database when inserting, modifying, or deleting data. Each of these operations triggers an insert statement per field that's enabled change logging. Second, the size of the change log table can impact the performance of admin operations such as copy company, export, and backup/restore of environments.\nIt's recommended to critically evaluate what fields should be tracked in the change log and also to do extra testing with realistic data before rolling out configuration changes to the setup of the change log.\nSee /across-log-changes.\n## Related information\nAuditing Changes in Business Central</across-log-changes>\ntelemetry-field-monitoring-trace\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>\ntelemetry-alert"}