[COMPASS-4116] Telemetry for ADL is wrong Created: 28/Jan/20 Updated: 29/Oct/23 Resolved: 05/Aug/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Telemetry Data |
| Affects Version/s: | 1.20.4 |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Massimiliano Marcon | Assignee: | Rhys Howell |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||
| Sprint: | Iteration Icaco | ||||||||||||
| Description |
|
When Compass is connected to ADL it reports the following:
Maybe something has changed since when we first implemented it. |
| Comments |
| Comment by Githook User [ 05/Aug/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: |
| Comment by Rhys Howell [ 27/Jul/20 ] |
|
Looks like the data lake info is publishing in the telemetry event as `is data lake` and `data lake version` Here's the event: Followed how our metrics for the connection event are built and emitted, I think I found it a bit hard to follow the connection event bubbling - maybe in future we can make it work without some of the extra hopping between packages, to make it a bit more straight forward and followable. 1. When a connection is connected to in `compass-connect`, a `data-service-connected` event is emitted: 2. `data-service-connected` listened to in `compass-app-stores` 3. `compass-app-stores` calls to fetch the connection information in `mongodb-instance-model`: Which calls to build the connection info in the data service: 4. `compass-app-stores` emits `instance-refreshed` which `compass-metrics` listens to: 5. `compass-metrics` builds the telemetry event metadata (`is data lake` and `data lake version`) 6. `compass-metrics` calls to track the event in `mongodb-js-metrics` `mongodb-js-metrics` calls the tracker set up in `compass-metrics`, which publishes the event to stitch. |