The following applies to Forum Sentry, Forum STS, and Forum Presidio.
Below is a list of tips/suggestions that can serve as some best practices for production logging and monitoring. More information on the logging options can be found in the Help menu.
1. Sentry has a feature to always log specific error codes, so you can always log particular messages regardless of the log level set.
2. There is a log file size option. If using DEBUG the log might grow quickly and when it reaches this threshold the log is overwritten completely. If you will be downloading log files, after running DEBUG mode, it might be best to set a lower log file size.
3. Sentry allows different download formats. If the log file is very large, set the download format to XML before downloading. If the download format is HTML or plain text, Sentry has to transform the XML log file into these formats. This can be a resource intensive operation on a busy server.
4. Consider using Syslog logging. It is possible to have the local logs use one log level while the Syslog policy uses another. If you frequently notice sluggish performance in the WebAdmin interface while viewing logs, Syslog will help as the logging information is stored off of the system.
5. Use SNMP monitoring to track the CPU, memory, and other statistical information.
6. Sentry monitoring with JMX - With the built in JMX Remote API, JMX provides another broadly accepted option for monitoring the health of the product.
0 comments:
Post a Comment