-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
2
-
False
-
-
False
-
Not Selected
-
-
-
Overview:
Backend telemetry events (sent from Central/Go) are mixed with UI events (sent from React frontend) in the same Amplitude project. While this is intentional for correlation purposes, adding a source property would improve filtering and clarity.
Context from Audit:
- ~15 backend event types vs ~50 UI event types in project 418843
- Backend events include: Central Heartbeat, _metrics gathered, Secured Cluster _, roxctl, etc.
- Dedicated dashboards exist for backend telemetry (Centrals Properties, Secured Clusters Properties)
- Current severity: Low - but adding source metadata would help with taxonomy documentation
Implementation Details:
- Add source: "ui" property to all UI analytics events
- Coordinate with backend team to add source: "backend" to their events
- Update analyticsTrack function to include source property automatically
Acceptance Criteria:
- [ ] All UI events include source: "ui" property
- [ ] Property is automatically added by analytics hook/utility
- [ ] Backend team is informed about adding source: "backend" to their events
- [ ] Document source values in analytics taxonomy
Files to Update:
1. src/hooks/useAnalytics.ts - Add source property to track calls
2. src/utils/analyticsEventTracking.ts - Include source in event properties
Related Tickets:
ROX-32641- Amplitude audit (this issue was identified there)