The management console of a product has separate menus allowing you to view both system and application logs. You can also download and view log files according to your preferences, in the following ways:
- If syslog-ng is configured, download log files from the remote location where the log files are hosted using syslog-ng server.
- If syslog-ng is not configured, download log files from the local file system (super-tenant or multi-tenant mode).
System logs display all events of a running product instance. While system logs display log events of the entire system, the application logs allow you to select a particular application or a program and view its logs only. Application logs give a fine-grained view of system logs.
- To access system logs, log in to the product's management console and select Monitor -> System Logs .
The System Logs page appears, displaying logs in a bottom-up manner. For example,
To access application logs, log in to the product's management console and select Monitor -> Application Logs .
The Application Logs page appears. This page displays logs of a selected application in a bottoms-up manner. For example,
In the View list, select the category of logs you want to view. The available categories are:
- TRACE - Trace messages
- DEBUG - Debug messages
- INFO - Information messages
- WARN - Warning messages
- ERROR - Error messages
- FATAL - Fatal error messages
You can also find a certain log using the search function. Enter a keyword (or part of a keyword) and click Search. When a search criteria is given, the View drop-down list is given the value
Custom.
INFO: The log messages are obtained from a memory appender. Therefore, the severity (log level) of the displayed log messages is equal to or higher than the threshold of the memory appender. For more information on appenders, loggers, their log levels and logging, see http://logging.apache.org/log4j.
INFO: The location of the log files on disk is specified in the log4j.configuration file.