C.2.3 Agent Log and pid Files

The locations of the agent log files are as follows:

On any platform, you can change the name and location of the agent log file. To confirm the location and the name, check the settings in the mysql-monitor-agent.ini file.

The maximum size of a log file may be limited to 2GB. If MySQL Enterprise Monitor Agent cannot add information to the configured logfile, information is sent to the standard output instead.

Because the log files can become quite large, you can use a tool such as logrotate (Unix/Linux) or logadm (Solaris) to automatically rotate the logs. The following example shows a sample logrotate definition:

/opt/mysql/enterprise/agent/mysql-monitor-agent.log {
    rotate 5
    daily
    minsize 1G
    postrotate
        /usr/bin/killall -HUP mysql-monitor-agent
    endscript
}

The above rotates the log before it reaches 1GB in size, keeping up to 5 files at a time.

To use your own system, you can copy the log file, flush the contents, and then send the SIGHUP signal to the agent process. On Windows, shut down before copying the log, then restart the agent afterward.

The locations of the agent pid files are as follows:

On any platform, you can change the name and location of the agent log file. To confirm the location and the name, check the settings in the mysql-monitor-agent.ini file.