[CONTEDIT-462] Add tracking for Usage Metrics (simple) Created: 16/Nov/21  Updated: 26/Aug/22

Status: Open
Project: Content Editor
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Laura Delnevo Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: AuthorX Maintenance
Team: AuthorX

 Description   

We identify 2 Usage Metrics that we would like to start tracking for Stories in order to help PM Process to shift to data-driven analysis.

Usage Metrics:

  1. Active Users - How many users are actively working with Stories App? The current definition of Active Users is "any users on product instances that are modifying content (event track) to show active usage
  2. i18n Stories - Compare no. of i18-ed stories to total no. of stories in the app (e.g. i18n is set to true?  What I would like to see over time is i18n of stories is increasing, decreasing, stable, etc. compared to no. of stories in the app

 

Wiki link https://wiki.magnolia-cms.com/display/PMTEAM/PM+data-driven+analysis



 Comments   
Comment by Maxime Michel [ 16/Nov/21 ]

Here's an example from GraphQL: https://git.magnolia-cms.com/projects/ENTERPRISE/repos/graphql/browse/magnolia-graphql-core/src/main/java/info/magnolia/graphql/core/metrics/GraphQLUsageScanner.java

Comment by Dai Ha [ 22/Nov/21 ]

First insights, CONTEDIT-462 is doable with some cost:

  • Option01: walk thru workspace and extract needed info and set to scanners
  • Option02: walk thru with paging
  • Option03: collect statics gradually into separated workspace?
    This reflect the reality that now data that needed to be collected stays in jcr workspace, not in memory like other current scanners
Generated at Mon Feb 12 00:20:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.