We have identified several areas for improvement in the telemetry feature. They are listed below:
The LAST_LOGIN is a Metric what is supposed to return the date of the LAST LOGIN on dotCMS, right now this Metric is not included on the Snapshot even when this is list on the Code as one of the Current Metric to be calculated, Maybe the reason why this Metric is not included on the Snapshot is because the SQL Query query used to calculate it is not getting any result.
Some Metric need a Rename, We have the follows Metrics:
Metric
Feature
SITES_NON_DEFAULT_TAGS_STORAGE_COUNT
SITES
CONTENTS_RECENTLY_EDITED
CONTENTLETS
SITES_RUN_DAHBOARD_COUNT
SITES
SITES_RUN_DAHBOARD_COUNT
SITES
Right now we va a VIEW that create a column for each Metric something like:
client_name
client_env
metric_1
metric_2
...
metric_n
...
...
The name of each column is: [FEATURENAME][METRIC_NAME]
So the names for the column on these Metrics are going to be:
Parent Issue
No response
Problem Statement
We have identified several areas for improvement in the telemetry feature. They are listed below:
The LAST_LOGIN is a Metric what is supposed to return the date of the LAST LOGIN on dotCMS, right now this Metric is not included on the Snapshot even when this is list on the Code as one of the Current Metric to be calculated, Maybe the reason why this Metric is not included on the Snapshot is because the SQL Query query used to calculate it is not getting any result.
Some Metric need a Rename, We have the follows Metrics:
Right now we va a VIEW that create a column for each Metric something like:
The name of each column is: [FEATURENAME][METRIC_NAME]
So the names for the column on these Metrics are going to be:
It is not a big problem but is weird
So I think we should rename this Metric as:
Remember each Metric has a feature attribute so the Scope of it is goint to be set be the Feature not by the name
Steps to Reproduce
Acceptance Criteria
Must be renamed
dotCMS Version
latest telemetry version
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response