-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
6
-
We're currently living on Confluence version 7.19.2 and we have access to the Analytics tool (as a space administrator, we primarily use the tool to view page & space analytics).
Over time, we've run into a problem where the Analytics tool is only able to collect and store up to six weeks worth of data. This is the direct result of a scalability issue where our Confluence Wiki instance includes hundreds of spaces and thousands of users, and it's now impacting how much data we can store on our database).
The Analytics tool data has now been essentially rendered useless because without the long term data (e.g., a minimum of six months to one year's worth), we don't have a true sense of page view trends which is important in determining whether or not content should be updated, deleted or archived.
Enhancements needed to help resolve this issue include:
- Allow Confluence Wiki system administrators to assess the impact of enabling the Analytics tool on our database (we're currently running a 300 GB database)
- Ability to enable the tool on a "per space" basis instead of globally for the entire Confluence instance
- Ability to change the tool event retention periods in order to be able to control its impact on our database in terms of storage
Several similar open issues have been posted, but neither specifically calls out scalability and its impact on gathering long term analytics data (nor do they mention the proposed enhancements above):
- Page analytics only available for past one year CONFCLOUD-73401
- As a user I want to store more than 20M of analytics events CONFSERVER-79849