dotCMS / dotCMS/core

[FEAT] CD: Add Telemetry Tracking

Open
#32,358 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Goal

Gather anonymized usage data within the Content Drive to better understand user behavior, identify areas for improvement, and inform future development decisions. This will allow us to optimize the Content Drive to better meet user needs.

Success Criteria
  • Telemetry tracking is implemented for the following user actions:
    • Base & Content Type Filter Selection
    • Folder Selection
    • Drag-and-drop File Upload
    • Drag-and-drop File Reorganization
    • Content Preview Panel Open/Close
    • CRUD operations on folders (create, rename, delete)
  • Track the amount of files and folders that are being tracked
  • Track each click inside the screen
  • Telemetry data is anonymized and does not contain personally identifiable information (PII).
  • Collected telemetry data is stored securely and used only for internal analysis and product improvement.
Demo Expectations
  • Explain and demonstrate that the tracking is enabled.
  • Show telemetry tracking is logging information.
  • Briefly describe the process used to collect and analyze telemetry data.
  • Demonstrate that only important events are being tracked (no personally identifiable information PII).

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

The issue names no files, tests, or telemetry entry point. Start by locating the Content Drive implementation and any existing telemetry mechanism, then determine how each listed action and file/folder count can be tracked without PII. Done means all success criteria are demonstrated, including secure collection and internal analysis.

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
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.