Jive's application logs include detailed information to allow you to troubleshoot any performance-related issues you may encounter.
This article will explain how to access the application logs and provide details on the information they contain.
Jive On-Prem 8.0+
There are two main application log files which normally reside on the web app servers, under the
These logs can be opened with any standard text editor, or you can also use tools such as grep, awk, or LogMX for more detailed analysis.
- sbs.out - contains startup information such as deployment and initialization, including Tomcat start-up information. It will also contain the log messages that are written to stdout/err.
- sbs.log - contains runtime application messages. Jive uses standard Log4J tagging to categorize log messages based on the level of detail required. e.g. WARNING, INFO, DEBUG, TRACE.
- In Jive On-Premise, sbs.log and sbs.out retain the standard naming convention.
- For Jive Hosted customers, the naming convention for the sbs logs is <instance_name>.log and <instance_name>.out but they are only accessible by Jive Support agents.
Other core Jive services logs:
The following logs also reside under the
eae-service.out & eae.service.log- Enterprise Activity Engine (EAE) logs
cache-service.log- Cache server log
search/sbs-search.log- Search logs (symlinked to