[JBoss JIRA] (SRAMP-557) "No artifacts found" shown erroneously when artifact type suggestion is clicked
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-557:
---------------------------------
Summary: "No artifacts found" shown erroneously when artifact type suggestion is clicked
Key: SRAMP-557
URL: https://issues.jboss.org/browse/SRAMP-557
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: UI
Reporter: Brett Meyer
Assignee: Brett Meyer
Priority: Minor
In the UI, upload an xsd. Then, on the left, search for the "XsdDocumen" type (leave off the "t"), then click the suggestion. The display shows results, but also shows "No artifacts found." in addition. Logic off? Note that this *only* happens when the suggestion is clicked.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (RTGOV-564) Discriminate between Service Responsetime and component Responsetime in Kibana dashboard
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-564?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-564:
-----------------------------
Fix Version/s: 2.0.0.Final
> 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
> Security Level: Public(Everyone can see)
> 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)
10 years, 4 months
[JBoss JIRA] (SRAMP-554) Improve the UI search capabilities and query syntax support
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-554?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-554:
------------------------------
Description:
Ideas:
- Completely replace the top "Search" bar with a field explicitly for S-RAMP queries.
- When left sidebar search is used, automatically add the equivalent query in the new bar.
- Include a link to the S-RAMP query docs.
- Add "name" and "uuid" fields to the search sidebar.
- Also on the sidebar, differentiate between search fields that are encompassed by the query language and ones that extend it (literally use a linebreak, etc.).
This would gain us both more powerful search capabilities, as well as "teaching" users the query language as they go.
> Improve the UI search capabilities and query syntax support
> -----------------------------------------------------------
>
> Key: SRAMP-554
> URL: https://issues.jboss.org/browse/SRAMP-554
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Priority: Critical
>
> Ideas:
> - Completely replace the top "Search" bar with a field explicitly for S-RAMP queries.
> - When left sidebar search is used, automatically add the equivalent query in the new bar.
> - Include a link to the S-RAMP query docs.
> - Add "name" and "uuid" fields to the search sidebar.
> - Also on the sidebar, differentiate between search fields that are encompassed by the query language and ones that extend it (literally use a linebreak, etc.).
> This would gain us both more powerful search capabilities, as well as "teaching" users the query language as they go.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months