# Analyzing field monitoring telemetry
> APPLIES TO: Business Central 2020 release wave 2 (update 17.1) and later
Keeping sensitive data secure and private is a core concern for most businesses. To add a layer of security, you can monitor important fields when someone changes a value. For example, you might want to know if someone changes your company's IBAN number.
To gather this data, you'll have to start field monitoring and specify the fields that you want to monitor. See Auditing Changes in Business Central - Monitoring Sensitive Fields</across-log-changes#monitoring-sensitive-fields> in the Application help.
Telemetry is then logged for the following operations:
 When field monitoring is stopped or started
 When a field is added or removed for monitoring (only in version 18.0 and later)
 When a field value is changed
These events use normal verbosity (severityLevel 1) and `TelemetryScope::All`.
## Sensitive field monitor status changed
Occurs when the field monitor feature is started or stopped in the company.
### General dimensions
Dimension|Description or value
message|Sensitive field monitor status has changed to {alMonitorStatus}
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. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
Dimension|Description or value
eventId|AL0000DD3
alMonitorStatus|Yes - the field monitor feature was started.<br /><br /> No the field monitor feature was stopped. This dimension is called "almonitorStatus" before version 18.0.
Common custom dimensions
The following table explains other custom dimensions that are common to all field monitoring 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.
environmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.
environmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.
## Sensitive field value has changed
Occurs when the value of a monitored field has changed in the company.
### General dimensions
Dimension|Description or value
message|Sensitive field value has changed: {alFieldCaption} ({alFieldNumber}) in table {alTableCaption} ({alTableNumber})
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. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
|Dimension|Description or value|
|eventId|AL0000CTE|
|alFieldCaption|Specifies the name of the field that was changed. This dimension is called "alfieldCaption" before version 18.0.|
|alFieldNumber|Specifies the ID of the field that was changed. This dimension was introduced in version 18.0.|
|alTableCaption|Specifies the name of the table that includes the changed field. This dimension is called "altableCaption" before version 18.0.|
|alTableNumber|Specifies the ID of the table that includes the changed field. This dimension was introduced in version 18.0.|
|See common custom dimensions<#other>||
> NOTE
> Changes to fields in the following tables are always logged:
 > Fields in the `Field Monitoring Setup` table, except `Notification Count`. Many of the fields are included on the Field Monitoring Setup page.
 > Fields in the `Change Log Setup (Field)` table. For monitored fields, only changes to `Table No.`, `Field No.`, and Notify are logged. Many of the fields are included on the Field Monitoring Worksheet page.
 > The Contact Email field in the User table.
## Sensitive field added to or removed from monitor
Occurs when a field has been added to or removed from monitoring. This event was introduced in version 18.0.
### General dimensions
Dimension|Description or value
message|Sensitive field added to monitor: {alFieldCaption} ({alFieldNumber}) in table {alTableCaption} ({alTableNumber})<br />or<br />Sensitive field removed from monitor: {alFieldCaption} ({alFieldNumber}) in table {alTableCaption} ({alTableNumber})
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. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.
### Custom dimensions
|Dimension|Description or value|
|eventId|AL0000EMW|
|alFieldCaption|Specifies the name of the field that was added or removed.|
|alFieldNumber|Specifies the ID of the field that was added or removed.|
|alTableNumber|Specifies the ID of the table that includes the added or removed field.|
|alTableCaption|Specifies the name of the table that includes the added or removed field.|
|See common custom dimensions<#other>||
## Related information
telemetry-changelog-configuration-trace
Monitoring and Analyzing Telemetry<telemetry-overview>
Enable Sending Telemetry to Application Insights<telemetry-enable-application-insights>
telemetry-alert

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-field-monitoring-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. https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-field-monitoring-trace/
