Previous Topic: Log FilesNext Topic: Job Logs


Agent Logs

The agent creates many log files that are useful for troubleshooting or reviewing historical activity. In a standard agent installation, the agent maintains the log files in a directory named log, which resides in the agent installation directory. Two log files of particular interest are receiver.log and transmitter.log.

The log.level parameter in the agentparm.txt file controls the amount of data written to log files.

The log levels are supported are 0 through 5, and 8:

Note: Level 2 is adequate for general, initial testing, and level 0 is adequate for production unless problems arise requiring more details for troubleshooting.

You can change select parameters from CA WA CA 7 Edition using the /AGENT command. Generally, do not make your changes through CA WA CA 7 Edition unless requested by CA Support. One that you can change on request is the log.level property to cause the writing of more messages to the agent logs for problem resolution. Thus, assume that you are executing using log.level 0, 1, or 2, but problems start occurring. You can change the logging temporarily (until the next agent recycle) or permanently (update to the agentparm.txt file). This change permits modification without needing to locate the physical host and modifying there. Some changes do require that you recycle the CA WA Agent, but for log.level, the changes can be immediate.

The following CA WA CA 7 Edition command would change the agent logging from (example) level 2 to level 5.

/AGENT,AGENT=agentname,PROP=log.level=5

If the parameter PERSIST=YES was added, this addition causes a permanent change to the agentparm.txt file.

When reporting problems with agents, generally zip the log directory and make it available to CA Support.

To clear the CA WA Agent log files on the CA WA CA 7 Edition system, enter the following command:

/AGENT,AGENT=agentname,FUNC=CLRFILES

This command resets the log files to start at the beginning, and all previous data is cleared. If your agent has been active for a long time period, and you have encountered a problem that can be easily re-created, clearing the log files sometimes presents a smaller set of log files to CA Support and makes it easier to debug the issue.