Troubleshooting custom scripting

Standard KBB_RAS1 variable applies to the OS agent and to the fcp_daemon processes. To apply a specific trace setting to fcp_daemon only, use the KXX_FCP_KBB_RAS1 variable; when KXX_FCP_KBB_RAS1 is set, the value that is specified by KBB_RAS1 is ignored by fcp_daemon.

To trace the operations logged by the OS agent core threads of the feature:

KBB_RAS1=ERROR (UNIT:factory ALL)

To trace scripting queries from the APM server and events sent to the server, add the entries:

On the Monitoring Agent for Linux® OS

(UNIT:klz34 ALL) (UNIT:klz36 ALL)

On the Monitoring Agent for UNIX OS

(UNIT:kux48 ALL) (UNIT:kux50 ALL)

On the Monitoring Agent for Windows OS

(UNIT:knt84 ALL) (UNIT:knt86 ALL)

To view TEMA traces to verify private situation execution, add the entries:

(UNIT:kraavp all) (UNIT:kraapv all)

To see the execution of the scripts and how the data from the scripts is being parsed set:

KXX_FCP_KBB_RAS1=Error (UNIT:command ALL)

To troubleshoot problems in the communication between the os agent and fcp_daemon, add this trace level to both KBB_RAS1 and KXX_FCP_KBB_RAS1:

(UNIT:cps_socket FLOW) (UNIT:cpci FLOW)

To see the interaction between the OS agent process and the fcp_daemon in detail add to both KBB_RAS1 and KXX_FCP_KBB_RAS1:

(UNIT:cps_socket ALL) (UNIT:cpci ALL)