Telemetry Setup Page

The Telemetry Setup page is the central place to configure how telemetry signals are filtered and sent from LS Central and dependent extensions to Azure Application Insights. You can open it by searching for Telemetry Setup in Business Central.

Changes you save on this page take effect immediately for subsequent telemetry events. No restart is required.

In this article

General FastTab

Trace levels and verbosity

See also

General FastTab

Field Description
Default Trace Level Specifies the minimum verbosity level that telemetry events must meet before they are sent to Application Insights. Events with a verbosity below the selected level are silently dropped. The available values are Verbose, Normal, Warning, Error, and Critical. The default value is Normal. Individual extensions may define their own app-specific trace level field on this page; those fields override the default for events coming from that extension only. See Trace levels and verbosity for guidance on choosing a value.

Note: Extensions built on the Telemetry framework can add their own trace-level fields to the Telemetry Setup page using a table extension. When such a field is present, its value overrides the Default Trace Level for events from that specific extension. The Default Trace Level continues to apply to all extensions that do not define their own field.

For example, the LS Central System App adds a System App Trace Level field to this page. Setting it to Warning means that only warning, error, and critical events from the System App are sent, regardless of the Default Trace Level.

Trace levels and verbosity

The telemetry framework maps each event to one of five verbosity levels. When you set a trace level on the Telemetry Setup page, only events at that level or higher are sent. The levels in ascending order of severity are:

Level When to use
Verbose Detailed diagnostic events. Setting the trace level to Verbose sends all events from the affected extension. Use this only in a sandbox or for short-term troubleshooting, as it generates a high volume of telemetry data.
Normal Standard operational events. This is the default level and is appropriate for most production environments.
Warning Events that indicate a potential problem but do not prevent normal operation. Use this level to reduce noise while still catching degraded conditions.
Error Events that record a failure that affects one operation but does not prevent the system from running.
Critical Events that record a severe failure. Setting the trace level to Critical sends the minimum number of telemetry events.

Tip: In production environments, start with Normal or Warning to keep Application Insights costs manageable. Drop to Verbose only when actively diagnosing a problem.

See also

Telemetry Framework for LS Retail Solutions

How to: Add telemetry to your extension