• Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Core UI
    • False
    • Hide

      None

      Show
      None
    • False

      At recent MOBB-F2F meeting I was demo'ing the OCM UI (production env) and we received a api error when looking at Cluster History.   I simply reloaded the page however, Abhishek's boss, who is constantly in front of customers, really pressed us on what our process is for tracking/handling such errors in the UI.

      I pulled up GlitTip:  https://glitchtip.devshift.net/

      There are errors being reported happening over 10,000 times!

      Granted, some our from our staging enviornment.

      We need to:

      1. Determine which 'Projects' to focus on for OCM UI.
      2. Need to add source-maps in order to trace errors to code
      3. Who monitors GlitchTip?
      4. What is the process for handling/escalating errors?
      5. Can we setup alerts/notifications for critical errors?
      6. Is there a way to get source maps in the GlitchTip logs?

              robertoemanuel Roberto Emanuel
              dtaylor@redhat.com David Taylor
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: