Turn Off or Limit Telemetry Trace Events

The application and platform can emit many telemetry trace events, which can be collected using various event trace tools. For example, telemetry trace events are recorded in the Microsoft Dynamics NAV Server channel logs, which you can see in Event Viewer, under Applications and Services Logs > Microsoft > DynamicsNAV > Common > Admin.

The number of events can place a large demand on the logging resources on the computer running the Microsoft Dynamics NAV Server instance. To help eleviate this demand, the Microsoft Dynamics NAV Server instance includes a configuration setting called Diagnostic Trace Level (TraceLevel in the customsettings.config file) that enables you to specify the lowest severity level of customer telemetry trace events that are emitted from the application, or even turn off telemetry events altogether. Custom telemetry trace events have IDs from 700-712.

To configure the Diagnostic Trace Level setting, you can use the Microsoft Dynamics NAV Server Administration tool, modify the Microsoft Dynamics NAV Server instance configuration file (CustomSettings.config) directly, or use the Set-NAVServerConfiguration cmdlet of the Microsoft Dynamics NAV Administration Shell.

Use the Microsoft Dynamics NAV Server Administration tool

1. To start the Microsoft Dynamics NAV Server Administration tool, select Start, and in the Search programs and files box, type Microsoft Dynamics NAV Administration, and then choose the related link.

2. In the left pane, under Console root, select the Microsoft Dynamics NAV Server instance.

3. In the center pane, select the Edit button.

4. Under General, set the Diagnostic Trace Level:

   You use this setting to filter out lower-level events from being emitted. For example, if you set this setting to Error, only Error and Critical events will be emitted.

   Set to Off if you do not want to emit telemetry trace events.

5. Select the Save button, and then select the OK button.

   You must restart the Microsoft Dynamics NAV Server instance for the changes to take effect.

6. To restart, the Microsoft Dynamics NAV Server instance, in the left pane, select the Microsoft Dynamics NAV computer.

   Unless you are administering a remote computer, this is Microsoft Dynamics NAV (local).

7. In the center pane, right-click an instance, and then select Restart.

Modify the CustomSettings.config file

1. Open the CustomSettings.config file for the Microsoft Dynamics NAV Server instance in a text editor, such as Notepad.

   By default, the file is located in the C:\Program Files\Microsoft Dynamics NAV\110\Service folder or C:\Program Files\Microsoft Dynamics NAV\110\Service\Instances\<instancename> folder (for multitenant installations).

2. Set the TraceLevel setting to Critical, Error, Warning, Normal (this corresponds to the Information level), Verbose, or Off.

3. Save the file, and then restart the Microsoft Dynamics NAV Server instance.

Use the Microsoft Dynamics NAV Administration Shell

1. Start the Microsoft Dynamics NAV Administration Shell.

2. At the command prompt, run the following command:

   Set-NAVServerConfiguration -ServerInstance DynamicsNAV -KeyName TraceLevel -KeyValue level -ApplyTo All
   

   Substitute DynamicsNAV with the name of the Microsoft Dynamics NAV Server instance and level with either Critical, Error, Warning, Normal, Verbose, or Off.

For more information about how to use the Microsoft Dynamics NAV Administration Shell, see Microsoft Dynamics NAV Windows PowerShell Cmdlets and Set-NAVServerConfiguration Cmdlet.

See Also

Monitoring Dynamics NAV Server Events Using Event Viewer
Monitoring Microsoft Dynamics NAV Server Events
Configuring Microsoft Dynamics NAV Server