{
	"id": "9396011e-779f-4e6b-924a-7c79fff666f1",
	"created_at": "2026-04-06T00:18:49.902287Z",
	"updated_at": "2026-04-10T03:20:50.609811Z",
	"deleted_at": null,
	"sha1_hash": "084bc6dcc5c0fb55aa4f21df07c04cc37e973c8b",
	"title": "Working with Confluence Logs | Confluence Data Center 10.2",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 210886,
	"plain_text": "Working with Confluence Logs | Confluence Data Center 10.2\r\nArchived: 2026-04-05 15:40:14 UTC\r\nConfluence uses Apache's log4j logging service. This allows administrators to control the logging behavior and\r\nthe log output file. There are six log4j logging levels.\r\nIf you request help from Atlassian Support, we will almost always ask for the Confluence application logs.  The\r\neasiest way to get these logs is to go to Administration menu , then General Configuration \u003e\r\nTroubleshooting and support tools and follow the prompts to create a Support Zip.\r\nApplication log files\r\nBy default, the application log files can be found in the \u003clocal-home\u003e/logs  directory. This location is\r\nconfigurable, so you may need to check the log config for your location.\r\nTo make troubleshooting problems easier, the application log is split into several distinct log files:\r\natlassian-confluence.log\r\nThis is the main application log file, most entries will be written here. When you start Confluence, any log\r\nentries written to the console will also be repeated in this log.\r\natlassian-confluence-index.log\r\nThis file contains entries related to the search index. \r\natlassian-confluence-outgoing-mail.log\r\nThis file contains entries related to outgoing mail, such as notifications. \r\natlassian-confluence-security.log \r\nThis file contains entries related to your users and user directories. \r\natlassian-synchrony.log\r\nThis file contains entries related to Synchrony, which powers collaborative editing. \r\natlassian-diagnostics.log\r\nThis file contains entries for an experimental diagnostics feature which provides alerts for things like low\r\ndisk space and memory.\r\natlassian-confluence-jmx.log\r\nThis file contains entries for Java Management Extensions API metrics which allow you to monitor the\r\nstatus of your instance in real time.\r\natlassian-confluence-app-monitoring.log\r\nThis file contains entries with app-related Management Extensions (JMX) API data that is collected every\r\nminute on schedule.\r\natlassian-confluence-ipd-monitoring.log\r\nThis file contains entries for in-product diagnostics including database connectivity and HTTP connection\r\nmetrics which helps with identifying performance issues in your infrastructure.\r\nhttps://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html\r\nPage 1 of 5\n\natlassian-confluence-migrations.log\r\nThis file contains entries related to migration to Cloud.\r\natlassian-confluence-health-checks.log\r\nThis file contains details about issues and errors detected during the startup of your Confluence instance\r\nthat need to be resolved.\r\nIn our documentation, when we refer to the \"application log\", we are referring to any of these files.\r\nYou can check the exact classes or packages that are logged to each file in the  log4j.properties  file\r\nunder  LOGGING LOCATION AND APPENDER .\r\nChange the log file configuration \r\nThe logging behavior for Confluence and Synchrony is defined in the following properties file:\r\n\u003cCONFLUENCE-INSTALL\u003e/confluence/WEB-INF/classes/log4j.properties\r\nThis file is a standard log4j configuration file, as described in the Apache log4j documentation.\r\nChange the destination of the log files\r\nIn log4j, an output destination is called an “appender”. To change the destination of the log files, you need to stop\r\nConfluence and then change the settings in the 'Logging Location and Appender' section of the\r\nlog4j.properties file. \r\nIn the standard properties file, you will find entries for two appenders:\r\ncom.atlassian.confluence.logging.ConfluenceHomeLogAppender – This is a custom appender which\r\ncontrols the default logging destination. This appender allows the following settings:\r\nMaxFileSize\r\nMaxBackupIndex\r\norg.apache.log4j.RollingFileAppender – If you want to log to a different location, uncomment the\r\nRollingFileAppender line and change the destination file in the line below it. Comment out the previous\r\nlines referring to the ConfluenceHomeLogAppender .\r\nThe Synchrony log destination can also be changed in the same way in file. \r\nConfluence ships with the full suite of appenders offered by log4j. Read more about appenders in the log4j\r\ndocumentation.\r\nFor more detailed information see Configuring log4j in Confluence to send specific entries to a different log file in\r\nour Knowledge Base. \r\nNote: If you change the location of your log files, they will no longer be included when you generate a support\r\nzip. This means you'll need to attach your logs to any support requests manually.\r\nChange the size and number of log files\r\nhttps://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html\r\nPage 2 of 5\n\nBy default, Confluence keeps 5 application log files, which are overwritten as they reach 20 MB. \r\nYou can change the default log size and the number of log files to keep by editing the following values in\r\n\u003cCONFLUENCE-INSTALL\u003e/confluence/WEB-INF/classes/log4j.properties  file. \r\nlog4j.appender.confluencelog.MaxFileSize=20480KB\r\nlog4j.appender.confluencelog.MaxBackupIndex=5\r\nChange the logging levels\r\nThis can be done in the Confluence UI. See Configuring Logging for instructions on how to change the logging\r\nconfiguration of Confluence.\r\nSpecific Confluence logging options\r\nHere's some specific log configurations you may need when troubleshooting. \r\nLog the details of SQL requests made to the database\r\nYou may want to increase Confluence's logging so that it records individual SQL requests sent to the database.\r\nThis is useful for troubleshooting specific problems. See Enabling Detailed SQL Logging.\r\nLog the details of users accessing each Confluence page\r\nAccess logging using Tomcat Valve is enabled by default from Confluence 7.11. These logs are not part of the\r\napplication log, and can be found at  \u003cinstall directory\u003e/logs/conf_access_log.\u003cdate\u003e.log .\r\nYou can however configure the application log to show which users are accessing which pages in Confluence.\r\nSee Internal Only - How to Enable User Access Logging in our Knowledge Base.\r\nScanning log files for known problems\r\nAtlassian Troubleshooting and support tools includes a log analyzer that can check for you Confluence logs for\r\nerrors and match them against known problems in our knowledge base and issue tracker. \r\nSee Troubleshooting Problems and Requesting Technical Support to find out how to set up a periodic scan of your\r\nlog files. \r\nMark logs when troubleshooting issues\r\nWhen troubleshooting it can be useful to mark your log files before and after you attempt to replicate the problem.\r\nThis makes it easier for you to locate the specific part of the log to investigate.  \r\nTo mark the application log files:\r\n1. Go to Administration menu , then General Configuration \u003e Logging and Profiling.\r\nhttps://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html\r\nPage 3 of 5\n\n2. If you run Confluence in a cluster, select a cluster node.\r\n3. Enter a message, for example \"Reproduce directory sync issue\".\r\n4. Select Rollover log files if you want to start a new log file with your mark (this will delete the oldest log\r\nfile). \r\n5. Select Mark.\r\nScreenshot: The logging and profiling screen in a cluster\r\nYour message will be added to all the application log files (such as atlassian-confluence.log, and atlassian-confluence-security.log). You can mark your logs as often as you need to.\r\nHere's an example:\r\n...\r\n2021-01-04 13:21:47,421 INFO [http-nio-8090-exec-5\r\n[impl.admin.actions.MarkAllLogsAction] execute\r\n***********************************************\r\nReproduce directory sync issue\r\n************************************************\r\n2021-01-04 13:25:23,901 ERROR [test error] [atlassian.confluence.test] This\r\nis a sample error java.lang.RuntimeException: Unable to find sample error\r\nfor testuser\r\n...\r\nTomcat logs\r\nThere are some additional logs in your Confluence install directory that can be useful when troubleshooting issues\r\nwith your Confluence site. \r\n\u003cinstall directory\u003e/logs/catalina-\u003cdate\u003e.log\r\nThis log records Tomcat operations, such as starting and stopping application server. \r\n\u003cinstall directory\u003e/logs/conf_access_log.\u003cdate\u003e.log\r\nThis is where you find Confluence's access logs. These logs are configured in the server.xml .\r\nhttps://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html\r\nPage 4 of 5\n\nSee Tomcat Access Log Valve documentation for further configuration options. \r\n\u003cinstall directory\u003e/logs/gc.\u003cdate\u003e.log\r\nThis is where you find the garbage collection logs. These logs provide useful information if you're\r\nexperiencing long GC pauses. \r\nSource: https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html\r\nhttps://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html\r\nPage 5 of 5",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html"
	],
	"report_names": [
		"working-with-confluence-logs-108364721.html"
	],
	"threat_actors": [],
	"ts_created_at": 1775434729,
	"ts_updated_at": 1775791250,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/084bc6dcc5c0fb55aa4f21df07c04cc37e973c8b.pdf",
		"text": "https://archive.orkl.eu/084bc6dcc5c0fb55aa4f21df07c04cc37e973c8b.txt",
		"img": "https://archive.orkl.eu/084bc6dcc5c0fb55aa4f21df07c04cc37e973c8b.jpg"
	}
}