[MAGNOLIA-9209] Expose the number of items in content apps for monitoring Created: 04/Dec/23  Updated: 09/Feb/24

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: dx-core-6.3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MAGNOLIA-9207 Expose the number of pages for monito... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Epic Link: Collect Usage Metrics

 Description   

Questions for discovers

  • How to measure? JCR queries don't provide aggregation functions. Iterating of a result set or the items of the workspace is likely not efficient and adds to much load to the instance. One way is a JCR query:
    QueryResult result = queryManager.createQuery("SELECT * FROM [nt:base]", Query.JCR_SQL2).execute();
    long nodeCount = result.getRows().getSize(); 

    However, this might still have an impact on the instance as it collects all results into a list internally in Jackrabbit.

  • Can and should we track this number separately. Risk of getting out of sync?

Generated at Mon Feb 12 04:39:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.