The Monyog log has detailed records of all sorts of server errors and messages. This can help in tracking down any problems with Monyog.
The Monyog log records these types of events :
- MySQL server errors received.
- MySQL client/API errors.
- SMTP errors.
- SSH server and client errors.
To read the log just click on 'Settings -> Show Log' tab in the Monyog interface. The log is a plain text file 'MONyog.log' which is stored in MONyog folder,
- Location in Windows 2008 :
- Location in Windows Vista/7:
Changing Monyog log path
The MONyog.log path can be changed to a desired directory from the MONyog.ini file. You just need to add the parameter “MONyogLogPath” in the MONyog.ini file and give the path to the MONyog.log file, for e.g: MONyogLogPath=/home/ubuntu/MONyogLog/
Please stop MONyog service before editing the MONyog.ini file.
Enabling log rotation in Monyog
Monyog Linux builds ship with log rotation script to truncate MONyog.log. MONyog-logrotate is availabe in the installation directory and should be copied to /etc/logrotate.d/ directory.
You can edit and configure the log retention time. By default, the log rotation happens every 7 days.
Log rotation is not available for Windows.
The Monyog log has detailed records of all sorts of server errors and messages. Below is the sample log,
How is it helpful?
A user doesn't have to keep his attention fixed to the Monyog interface all the time. While Monyog is collecting statistics as a background service, how will a customer know that something went wrong or not? He can just wake up and have a look at the log.
It basically logs the 'critical places' and 'network interfaces' problems faced by Monyog. Like if for some reason Mail Alert has not been send, or MySQL server is down, etc.