Problem

Confluence lacks the capability to log detailed request information, such as client IP, username, request ID, session ID, and request URL, directly in the application log (e.g., atlassian-confluence.log). This limits the ability to trace and analyze user activity effectively within the application logs.

Suggested Solution

Implement enhanced Log4j properties in Confluence similar to those available in JIRA. This would include logging detailed request information such as %X{jira.request.ipaddr}, %X{jira.username}, %X{jira.request.id}, %X{jira.request.assession.id}, and %X{jira.request.url} in the log4j.properties file.

Why This Is Important

JIRA's implementation of detailed request logging provides valuable context for troubleshooting and monitoring. By including such details in Confluence, administrators would gain better visibility into user activities, improve the accuracy of issue diagnosis, and enhance overall system monitoring.

Workaround

Currently, the detailed request information can be accessed via the Confluence access logs.