Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add telemetry customer category, customer name & environment name to content analytics events #31319

Open
john-thomas-dotcms opened this issue Feb 6, 2025 · 0 comments

Comments

@john-thomas-dotcms
Copy link
Contributor

Parent Issue

No response

Task

For telemetry, we currently record information on the customer category, customer name, environment name, and environment version with each report record. This information is critical for providing automated reports that revenue teams can use without needing to lookup customer IDs.

We need to record all 3 of these pieces of information in the content analytics event records. These can not be selected or changed by users; this means they can not be supplied as arguments to the endpoints or velocity methods, and instead will be inserted automatically by the endpoints and methods.

Proposed Objective

Same as Parent Issue

Proposed Priority

Priority 2 - Important

Acceptance Criteria

  1. All new content analytics records include the following pieces of information, as determined by the current telemetry code:
    • customer category
    • customer name
    • environment name
    • environment version
  2. This information is recorded automatically when new custom analytics events are recorded from all possible sources:
    • Java code
    • analytics endpoint
    • Rules
    • Workflow (Fire analytics event)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Next 1-3 Sprints
Development

No branches or pull requests

1 participant