The current analytics event data definition (which I believe is shared with some analytics tools hosted by OPS) doesn't include the nodeId where the UI event occurred. This story will look at adding nodeId to analytics events. Whoever works on this task should check with OPS to find out whether adding this new field will cause any issues with their downstream analytics tools.
- should we also look at versioning the analytics data definition?
- does the local sequence counter provide much value in HA?
- existing records should leave the nodeId unspecified