Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-3579

client-side tracing for user events and errors

    • Type: Icon: Story Story
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed

      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

            Assignee:
            Unassigned Unassigned
            Reporter:
            irina.shestak@mongodb.com Irina Shestak (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: