dotCMS / dotCMS/core

[FEATURE] Usage Dashboard - Show Real Time Data in the dashboard

Open
#34,571 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale Team : Platform
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem

The data shown in the current dashboard is not real time data, the actual metrics are cached for 5 minutes, so when new workflows, new locales, new content etc are created in the back end, it is not reflected in the report for up to 5 minutes.

As a content operations manager I want to see real time statistics of what content types, content, and sites I have in the system so I can trust the report is accurate. Right now it is confusing to create content or users and not see them reflected in the report, it makes users doubt the report or think there is something broken.

Goal

Ideally we can find a way to provide accurate and updated data in real time, without having the user click refresh, or reload the page after a certain amount of time etc. When the page is loaded the data should be real time.

The page does not have to continually update and refresh when the user is on it though. Only when the user loads the page should the data be updated to real time.

Target Personas
  • Developer teams
  • Content teams
  • DevOps teams
  • System administrators (dotCMS)
Demo Expectations

Should be able to create any one of the items that are tracked on the report, then show the report being updated with the latest data. Both removing items and adding items.

Acceptance Criteria
  • Every metric reflects the actual number of items in real time when the page is loaded (or reloaded)
  • When a user creates a new item, that new item is reflected immediately upon going to the report page
User Stories

No response

Links

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Usage Dashboard and tracing how its metrics are loaded when the page opens. Verify the current five-minute caching behavior and identify the tracked item types. Done means each metric reflects additions and removals immediately after navigating to or reloading the report, without requiring continuous updates.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.