[overlord-issues] [JBoss JIRA] (RTGOV-564) Discriminate between Service Responsetime and component Responsetime in Kibana dashboard

[Gary Brown (JIRA)]

    [ https://issues.jboss.org/browse/RTGOV-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004333#comment-13004333 ] 

Gary Brown commented on RTGOV-564:
----------------------------------

I'm not entirely clear what representation you are looking for, although I understand the goal of trying to hide component services.

Currently response times associated with promoted services have a 'gateway' property, so would you be able to create a dashboard of the style you are looking for, distinguishing the response information for promoted and component services using 'properties.gateway' field?

If so, can you attach the modified dashboard on this jira and I'll try it out. Thanks.

> Discriminate between Service Responsetime and component Responsetime in Kibana dashboard  
> ------------------------------------------------------------------------------------------
>
>                 Key: RTGOV-564
>                 URL: https://issues.jboss.org/browse/RTGOV-564
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: User Interface
>    Affects Versions: 2.0.0.Final
>            Reporter: ivan mckinley
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> 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 
>  
>    



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)