Manage trace using the server task trace

Tracing can be activated either through a routing file or through the server task trace command. The server task trace command can be issued through either the pdadmin utility or programmatically through the ISAM Administrative API.

• List all of the available trace points.
• Change the level and destination for specific trace points.
• Retrieve the trace point level for specific trace points.

To list all of the trace components offered by a server, issue the trace list command:

server task server_name trace list

For example.

pdadmin> server task pdwebpi.com trace list
pdwebpi.request
pdwebpi.response
...

To change the level and destination for a specific trace point:

server task server_name trace set component level [file path=file|other-log-agent-config]

Where:

server_name	Name of the server on which we want to collect trace information.
component	Trace component as shown by the list command.
level	Controls the amount of detail to be gathered, in the range of 1 to 9, with 1 collecting the least number of traces, and 9 collecting the most number of traces.
/path/to/trace.output	Location for trace output. If not supplied, trace output is sent to the stdout.

Set the trace level to 9 for the pdwebpi.request component. Output is sent to /tmp/log.txt on the WebPI server.

pdadmin> server task pdwebpi.com trace set pdwebpi.request 9 file path=/tmp/log.txt

To show the names and levels for all enabled trace components:

server task server-name trace show [component]

If the optional component parameter is omitted, the output lists the name and level of all of the enabled trace components.

pdadmin>server task pdwebpi.mydomain.com trace show pdwebpi.request 9

Parent topic: Trace event logs