Resolving as duplicate, Audit logging is now released to Cloud. Please follow the related ticket for updates.

There is some additional/specific use cases identified on this ticket, so please feel free to raise a new suggestion if the current implementation does not cover specific use cases.

For logging admin activity our new Auditor for Confluence add-on (https://marketplace.atlassian.com/plugins/com.enhancera.auditor.confauditor) can be used.

The add-on has been released just now, and we plan to take any user feedback seriously and add missing features quickly.
Your opinion is very important to us.

We definitely would like to see this for the On Demand solutions. Security are keen on more detailed auditing, particularly across Confluence and who is access what from where. The lack of this feature may result in constraints around how we use this solution moving forward, which would be a shame.

Albeit not really a logging tool, the Archiving Plugin addresses some of the use cases mentioned here.

> For confluence content, we'd like to gauge which content hasnt been viewed for a while, so that we can remove stale content.

It definitely tracks and reports on "content hasnt been viewed for a while", please read here.

As for stale content, it also tracks spaces and pages which expire on a user-defined date or within a user-defined period (ex: in 10 weeks after the last update). Even more, it helps you to archive pages that are not needed anymore, but can't just simply be deleted (you said Enterprise, huh? ).

Learn more

Our stats plugin can be used to provide this level of reporting. It tracks pretty much everything that happens, and allows you to correlate to an IP address, etc. For more information contact Dan Hardiker via https://www.adaptavist.com/display/ADAPTAVIST/Contact+Us

from Ben Vaughn (United Airlines):

There's no way to track comments and other edits made to articles inside a space. IE, if Employee A gets a hold of Employee B's password and logs into a space and posts a bunch of porno to a space, we can't track down who did it because there's no IP address logs for edits. Kind of a bummer.

Just logging admin activity would be a good start.

Thanks Nick - we definately see a need for this from a few perspectives.

For confluence content, we'd like to gauge which content hasnt been viewed for a while, so that we can remove stale content.

From a user management perspective we'd like to do the same, and also view the user behaviour so that we can analyse and determine what we are doing correctly and what information in our wiki is useful to the business.

From a 'compliance' perspective - having audits on will help us resell into enterprises that not only love these sort of 'big brother' capabilities - they actually require them.