-
Notifications
You must be signed in to change notification settings - Fork 1
Trace
Sometimes deep support insights are needed to investigate issues.
For this reason, the drm-cli has tracing extension that provides dipper information of the drm-cli execution.
The tracing information includes technical info, such as call stuck, for the supported team to get dipper information on what's going on.
Note!!! tracing enabling can affect the host performance & the execution itself.
Hence, it is best advised to enable it when requested by the support team.
Enabling basic tracing is very easy to do, since all of the drm-cli utilities (install.py, drm_deploy.py, drm_crypto.py & uninstall.py) come with a built-in "--trace" option flag.
To see all optional parameters, use the -help option.
When the tracing option flag is used, a trace file is created, in trace folder inside the utility's log folder.
The trace log file naming convention is:
{yyyy}{MM}{dd}{HH}{mm}_{ss}{utility name}.log.
In this version, the specific tracing flags feature is not yet developed. To see the full list of version features, See Features list.
Adding trace flag is very easy.
Each utility's trace flags are configured within its configuration file.
Note!!! some entities share the configuration with other utilities.
Such as install.py & uninstall.py, which share install.config.
Also, drm_deploy.py & drm_crypto.py are sharing drm_deploy.conig.
To enable specific trace flag, add the following section to the utility trace file, under the root:
"trace_flags": []
python3 ./drm_crypto.py --encrypt -t "Hello" --traceIn the following example, the --trace flag option is turned on.
{
"trace_flags": [123, 456]
}