[COMPASS-3579] client-side tracing for user events and errors Created: 18/Apr/19  Updated: 26/Aug/21  Resolved: 26/Aug/21

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Story Priority: Major - P3
Reporter: Irina Shestak (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to COMPASS-2332 Write to Log File in Production Closed
Documentation Changes: Not Needed

 Description   

I would like to see us have a better idea about how users go about using Compass and what errors they encounter along the way. Without having to resort to using an APM provider, I can see this looking like this:

  1. a simple logger (like pino)
  2. we will likely have to write this ourselves, and this is the bigger chunk of this story: a way to track where a user came from (Documents Tab --> Aggregation Tab). This could be done with async_hooks in node, but we will have to have a browser equivalent.
  3. and then write it all to a db we can view in compass, run aggregations on, etc

This ticket stems from a conversation we were having in https://jira.mongodb.org/browse/COMPASS-2332



 Comments   
Comment by Maurizio Casimirri [ 26/Aug/21 ]

We now have a project to address this: COMPASS-4361

Generated at Wed Feb 07 22:33:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.