Monitoring and Logging
Monitoring and Logging
Monitoring
Monitoring of PoolParty may happen on two different layers, on the application server layer or the the underlying operating system layer.
Monitoring on Application Server Layer
PoolParty comes deployed on Tomcat which provides a JMX management interface described in the Tomcat JMX Guide. Use any JMX compatible console or monitoring agent with it.
As an alternative you may also deploy a monitoring webapp like psi Probe to watch system parameters from within the appserver container. Here you can find the latest release.
Monitoring on Operating System Layer
On OS layer the PoolParty system will seamlessly integrate into such monitoring systems used like Nagios or any commercial alternatives. Typically you will want to use plugins of that systems designed to monitor JEE compliant app servers like Tomcat. Or you can of course also implement monitoring based on system logfiles like for example Splunk does. Please Contact us for further consulting on this matter.
Logging
PoolParty log files are placed per default in the following directories respectively:
GNU/Linux: /opt/poolparty/tomcat/logs
Windows: C:\Program Files\Apache Software Foundation\Tomcat 7.0\logs
Initially the log level is set to WARN, to avoid too verbose output of the system. PoolParty is using log4j as a logging framework, which allows high customization of log output. The configuration of the log output is done in the log4j.properties file that can be found in the following directories respectively:
Linux: /opt/poolparty/tomcat/lib
Windows: C:\Program Files\Apache Software Foundation\Tomcat 7.0\lib
Log File Management and Rotation
Log files keep growing over time and tend to waste disk space if left unmonitored and unmanaged. Please use the tools provided by your operating system, for example the logrotate deamon available on Debian like systems.