Uploaded image for project: 'RTGov (Run Time Governance)'
  1. RTGov (Run Time Governance)
  2. RTGOV-564

Discriminate between Service Responsetime and component Responsetime in Kibana dashboard

    Details

      Description

      Kibana ui
      The current kibana dashboard shows the response times for all component response times. It was observed that this is not optimal and clear to end-users. Endusers would initially be most interested in the response times on the promoted interface “soap binding” for example. Independent to the switchyard world, this would mean only displaying the response time for the entire serviceTX (and ignoring the components response times) or as its know the activityUnit

      Proposal,
      that the landing kibana dashboard shows the response times for the entire serviceTX in a dedicated table and the response times for the components in another.
      View the response of components could be another widget. i would not suggest another dashboard as this would mean users could not drill down into a service’s components

      Example, in the default dashboard, the table LIST OF SERVICES TABLE.
      This table displays the service tx response time but also the component response time. to the end user this not exactly clear

      {urn:switchyard-quickstart-demo:orders:0.1.0}

      OrderService

      {urn:switchyard-quickstart-demo:orders:0.1.0}

      OrderService/FundsService

      {urn:switchyard-quickstart-demo:orders:0.1.0}

      OrderService/InventoryService

      {urn:switchyard-quickstart-demo:orders:0.1.0}

      OrderService/LogisticsService

      howto,
      Perhaps a flag will be required on the response time object to discriminate component response time and service tx response times

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                objectiser Gary Brown
                Reporter:
                imckinle ivan mckinley
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: