-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
2
-
False
-
-
False
-
-
-
Overview:
Standardize the analytics event naming convention by removing inconsistent colon prefixes from Network Graph events to match the established pattern used by other features.
Problem:
Network Graph events use a colon prefix pattern (Network Graph: ...) while all other features use space-separated prefixes (Workload CVE ..., Compliance ..., etc.). Additionally, two Network Graph-related events (External IPs Side Panel Opened, External Flows Toggle Clicked) don't follow any prefix pattern.
Implementation Details:
Option 1 (Minimal - recommended):
- Remove colons from 4 Network Graph events
- Network Graph: Cluster Level Simulator Opened -> Network Graph Cluster Level Simulator Opened
Option 2 (Comprehensive):
- Also add prefix to orphan events:
- External IPs Side Panel Opened -> Network Graph External IPs Side Panel Opened
- External Flows Toggle Clicked -> Network Graph External Flows Toggle Clicked
Acceptance Criteria:
- [ ] All event prefixes use consistent space-separated format (no colons)
- [ ] Related events within a feature share the same prefix
- [ ] Update event names in Amplitude Data Governance to match
Files to Update:
- apps/platform/src/hooks/useAnalytics.ts:21-26 - Update event constants
Related Tickets:
ROX-32641- Discovery: Conduct Amplitude audit (identified this issue)