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

Send telemetry data as a content analytics event #31320

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

Send telemetry data as a content analytics event #31320

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

Comments

@john-thomas-dotcms
Copy link
Contributor

Parent Issue

No response

Task

We currently send a static telemetry data on a schedule, inserting it into the telemetry postgres database. The analytics database records activity data in a separate clickhouse database.

We need to merge the static telemetry data with the analytics activity database. To do this, every time we send the telemetry data packet to the telemetry DB, we will also send the same data to the analytics database as an analytics event. So, the telemetry data will be sent on the same schedule, and each time the schedule hits, the data will be sent to both the telemetry DB and the analytics DB in parallel.

Note: We will eventually remove the telemetry DB. However, to avoid breaking existing existing telemetry reports, we'll send the data in parallel to both DBs until the existing reports can be modified to pull the data from the analytics DB.

Proposed Objective

Same as Parent Issue

Proposed Priority

Priority 2 - Important

Acceptance Criteria

  1. All data in the telemetry DB is mirrored exactly in the analytics DB.

Note: There is no requirement for which telemetry data is stored together in a single analytics event. So, the telemetry data can be stored in a single analytics event, or broken into multiple analytics events.

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