Enabling the collection of diagnostics data by using the configdc command

Edit online

You can also enable or disable the collection of diagnostics data by using the configdc command. This process is optional.

Before you begin

Ensure that you have registered the data collector. For details, see Registering the data collector.
Ensure that you have completed the process at Enabling collection of transaction tracking and diagnostics data.
Ensure that the qe_custom.properties file is processed by the APM server at <APM_Home>\localconfig\qe and has following properties:
- transaction_tracking=ENABLED
- diagnostic_mode=LEVEL2

Procedure

Run the following command:
```
cd install_dir\qe\bin configdc deepdivedc -tracelevel trace_level
```
Where,

install_dir

The installation directory of the Microsoft .NET agent.

trace_level

The trace level that indicates the amount of diagnostics data that the .NET Data Collector collects. Specify one of the following values:

0

The collection of the diagnostics data is disabled.

1

The collection of the diagnostics data is enabled. The HTTP module collects the request summary and request instance data.

2

The collection of the diagnostics data is enabled. The HTTP module collects the request summary and request instance data. The profiler collects method data and stack trace data.

Tip: When you set the trace level by using the configdc.exe deepdivedc -tracelevel command, the value of the bci_dc.diagnose.level parameter is set in the dotNetDcConfig.properties file.
Activate the configuration changes.
For information about activation of changes, see Activating the configuration updates.

What to do next

Log in to the Cloud APM console to view the diagnostics data that is collected by the agent in the dashboards. For information about using the Cloud APM console, see Starting the Cloud APM console.