Uploaded image for project: 'Observability UI'
  1. Observability UI
  2. OU-418 TP: Distributed tracing plugin
  3. OU-473

UX Evaluation: Integrate a Gantt chart into the distributed tracing plugin

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • OBSDA-510 - Tech Preview: Integrate Distributed Tracing View / OpenShift Web Console - Admin
    • NEW

      Goal

      Evaluate and provide UI/UX guidance using PatternFly recommended practices to be aligned with the OCP console.

       

      Outcomes

      The user interface should maintain aesthetic cohesion and the user experience should be aligned with client expectations for OCP.

        1. Screen 2.png
          Screen 2.png
          144 kB
        2. Screen 3.png
          Screen 3.png
          75 kB
        3. tempo instance empty state.png
          tempo instance empty state.png
          59 kB

            [OU-473] UX Evaluation: Integrate a Gantt chart into the distributed tracing plugin

            The charts have been implemented, reviewed, and aligned to PatternFly within technical feasibility.

            Foday Kargbo added a comment - The charts have been implemented, reviewed, and aligned to PatternFly within technical feasibility.

            Provided PF-recommended design guidelines/mockups. Discuss UI with the dev.

            Foday Kargbo added a comment - Provided PF-recommended design guidelines/mockups. Discuss UI with the dev.

            Hi agerstma@redhat.com  I've created two mockups with PatternFly guidelines for you. The first screen shows Tracing in the use case with empty states. In other words, no query has been entered. It might be the case that we will never have empty states on this page. To be discussed. The second screen shows the page when a query has been entered. I wasn't sure of the colorful labels so I used plain ones with no numbers inside them, the ones underneath the Traces' names. Also to be discussed. To be discussed: * Empty states for charts and table

            • Labels in the Trace Names column
            • Tooltips for the chart - what we can show when a user hovers over chart items
            • Span column or Status column
            • How does the user return to the main Traces chart after clicking and drilling down into the second view?

            Here's a link to the pages, you can click on the "Run query/s" button to see the next screen. Click on the "X" to return to the first screen, or use your keyboard arrow keys, left + right.
            https://www.figma.com/proto/nu6rKYMxt2VzhNhu5OJoJp/Tracing-Grantt-Chart-UI-Fixes?no[…]ent-scaling=fixed&page-id=0%3A1&starting-point-node-id=4%3A164 (edited) 

            Foday Kargbo added a comment - Hi agerstma@redhat.com   I've created two mockups with PatternFly guidelines for you. The first screen shows Tracing in the use case with empty states. In other words, no query has been entered. It might be the case that we will never have empty states on this page. To be discussed. The second screen shows the page when a query has been entered. I wasn't sure of the colorful labels so I used plain ones with no numbers inside them, the ones underneath the Traces' names. Also to be discussed. To be discussed: * Empty states for charts and table Labels in the Trace Names column Tooltips for the chart - what we can show when a user hovers over chart items Span column or Status column How does the user return to the main Traces chart after clicking and drilling down into the second view? Here's a link to the pages, you can click on the "Run query/s" button to see the next screen. Click on the "X" to return to the first screen, or use your keyboard arrow keys, left + right. https://www.figma.com/proto/nu6rKYMxt2VzhNhu5OJoJp/Tracing-Grantt-Chart-UI-Fixes?no[…]ent-scaling=fixed&page-id=0%3A1&starting-point-node-id=4%3A164  (edited) 

              fkargbo Foday Kargbo
              fkargbo Foday Kargbo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: