-
Notifications
You must be signed in to change notification settings - Fork 471
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
Spike: Plan how to send telemetry data as a content analytics event #31320
Comments
SUMMARYThere are several approaches we might follow with regards to adding the Telemetry Report to our CA infrastructure. So, far, it seems these are the options we have:
I've put together a list of pros and cons for each of them, which must be discussed with the team: Separate columns for each metricPros:
Cons:
Metrics saved as separate eventsPros:
Cons:
Metrics saved in a single event recordNOTES:
We'll need a POC for both options. Pros:
Cons:
Aside from choosing the appropriate way to store the Telemetry data, we need to define what part of the code is going to save it and how it's going to do that. For instance:
|
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
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
The text was updated successfully, but these errors were encountered: