Using the Application Logs

Jive logs messages containing application information, warnings, and errors in several different log files. You can view the log files in the Admin Console for troubleshooting purposes. (You can also log information about database queries, as described in Examining Database Queries.) The logs are built using Apache's log4J system. For more information about the log4J API, see http://logging.apache.org/log4j/1.2/manual.html. Typically, you would only use the Logging Management pages when working through an issue with a Jive support person.

Fastpath: Admin Console: System > Management > Logging Management

Configuring Logging Settings

On the Configuration tab, you can:

Set the logging level for the application. This should be set to Error unless you are working through an issue with a Jive support person.
View and apply overrides to logging levels. For example, if a user is experiencing unexpected behavior in the application, a Jive support person may ask you to adjust the logging levels for troubleshooting purposes.

Using the Log Files

On the Log Viewer page, you can:

Insert a mark in a log file. This allows you to mark the problem spot and then monitor what happens after you reproduce the behavior.
Force a log file roll. This is useful when you're looking for something specific in the log but the file is very long. Forcing a roll restarts the log file at the beginning.
View the log files.

Log File	Description
[name].log	The main log file where almost all logging is sent.
[name]-session.log	Contains some logging information regarding when users log in and the number of active user sessions.
[name]-profiling.log [name]-latency.log	Some profiling options in Jive log to these files. However, the settings must be enabled, so typically, these files are empty.
[name]-docverse.log	Contains logging related to the document conversion process.
[name]-appmarket-poll.log [name]-appmarket-pull.log	Contains logging information related to communication with the apps market.