Access logs are also one of the most useful ones to obtain based on the type of issue you are using. However, use your discretion if pulling them will be useful in your current use case.
This article provides information about the logs' navigation path as well as the different types of access log files that are most relevant in troubleshooting.
Some important access logs are:
- Jive-httpd-ssl-access.log (on-premise sites might need to terminate SSL so the name will be different than access log.)
HTTPD access logs are a great way of seeing patterns in the usage of an instance. For example, it can be a good way of finding if a particular REST endpoint is being heavily accessed, or if there is some automation causing too many requests.
By default, the Jive access log is called jive-httpd-access.log (it rotates daily) and is located under
<JIVE_HOME>/var/logs. On-premise instances may be terminating SSL at the Apache level, therefore the access log will be called jive-httpd-ssl-access.log.
In addition to the access log, it can also be useful to capture httpd-error.log which logs errors pertaining to the HTTPD service including communication issues with Tomcat.
When it comes to opening either application or access logs, you can use any standard text editor to open and parse these such as Notepad++ or Glogg. You can also use other text parsers via command line/linux/unix as well, like grep and awk, depending on your preference.