I'm bundling these two together, as the docs seem to indicate they work in much the same way.
We need extensive logging of user activity on our ticketing and collaboration sites.
It seems that
Are the above correct? Any suggestions would be much appreciated.
Reads in Jira simply aren't logged unless you make some code changes. Reads in Confluence can be, there is a plugin that does it built into the system, but it's disabled by default because the load it imposes can end up crippliing it.
Almost all changes are logged in both systems - that is in fact what they are for - tracking changes. This data all shows up in the history of the issue/page (Minor things not directly related to the issue or page data are not logged though. Stuff like users being added/removed as watchers, votes etc)
You are right in that you can use Tomcat logging to trap the urls accessed. That's pretty much your only real option here for read access logging. Almost all writes are logged by definition inside the apps though.
My suggestion would be to consider exactly what you need to log and then use Tomcat / Apache logging for analysing read access and the application reporting for writes.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs