Make different presentation for unavailable metrics

Description

The problem: 

When users trying to change Metric it's usually a lot of values and users need to know e lot about metrics. it's sometimes easy to select metric you  don't  have in the current selection 

 

User Story: 

As PMM user, I  need to see metrics which are not present in the current data set, so that i can easily see what's available for selection  

 

Proposed solution

1) have Metrics in the list sorted by "availability" and next by  A-Z  

2) Use different  "color"  (UX needed ) for presenting Available and unavailable metrics 

 

Suggested implementation:

 -  Extend API with an endpoint that returns a list all metrics with an indication which is available for given time range and selected filters.

 - Implement in qan-api2 method to select available metrics:

 

 

[UI part] UI can cancel the query if it runs longer then 3 sec and shows metrics that they already have with a note:

get only available metrics takes too long - show all queries

Or 

1) Selected metrics taking too long - showing all
2) Slow response from selected metrics - showing all
3) Your selected metrics are slow to respond - showing all instead

How to test

None

How to document

None

Attachments

3

Smart Checklist

Activity

Show:

Andrii Skomorokhov August 5, 2020 at 9:37 AM

>  please make sure that this cancellation signal is passed from frontend via nginx and qan-api2 to ClickHouse, and that the query is actually cancelled in ClickHouse. I'm sure that doesn't work now. We should be able to see that from logs (please add logs if that's not the case) and metrics.

 

ack

Alexey Palazhchenko August 4, 2020 at 11:41 AM

UI can cancel the query if it runs longer then 3 sec and shows metrics that they already have with a note

please make sure that this cancellation signal is passed from frontend via nginx and qan-api2 to ClickHouse, and that the query is actually cancelled in ClickHouse. I'm sure that doesn't work now. We should be able to see that from logs (please add logs if that's not the case) and metrics.

Alexander Blinkov August 3, 2020 at 1:51 PM

2SP for BE, FE part should be estimated in separated ticket

Andrii Skomorokhov July 30, 2020 at 8:28 AM

Added a suggestion for implementation.

Alexander Blinkov July 28, 2020 at 9:14 AM

, please investigate the ticket so it can be estimated

Details

Assignee

Reporter

Priority

Components

Needs QA

Yes

Needs Doc

Yes

Story Points

Smart Checklist

Created June 2, 2020 at 8:51 AM
Updated November 13, 2024 at 8:33 AM