-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for HDR percentiles in TSVB visualizations #78306
Conversation
@elasticmachine merge upstream |
Pinging @elastic/kibana-app (Team:KibanaApp) |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...s/vis_type_timeseries/public/application/components/aggs/percentile_rank/multi_value_row.tsx
Outdated
Show resolved
Hide resolved
} | ||
> | ||
<> | ||
{model.values && ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't you add the whole EuiFormRow under model.values check here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, I just moved it from the other place without thinking about it. I see that model.values
are not optional fo this agg and should have a value. I think it was added cause in model it's an optional value....
Fixed
<> | ||
{model.values && ( | ||
<PercentileRankValues | ||
disableAdd={isTablePanel} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stratoula you are not right, on master I see the same issue. But it's not a reason to don't solve it. Will be fixed in that PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My mistake @alexwizp, thank you so much for fixing this
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@cchaos could you please confirm that my fix which found @statula is ok from the design perspective I moved some optional for the Band mode fields into new Panel. As a result all looks fine on all screens. It also seems to me that this is more user friendly @stratoula thank you so much, I forgot about that mode |
@elasticmachine merge upstream |
The problem with the panel visually is that it doesn't encompass the whole setting and so it's not clear where it came from or which line will delete it. My suggestion would be to keep it as a separate line but align it with the above inputs so that the +/delete icons are vertically centered with both lines of forms. Also make sure to use the horizontal form rows to match the above display. |
@cchaos I still think that we should use |
That's fine. I think we've tried to be more condensed in the past in the TSVB forms. Just be sure to continue to test in smaller window sizes. |
@cchaos on mobile it looks like: |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks much better now @alexwizp 🙂 LGTM!
@sulemanof can you also check this please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM, tested locally, works as expected (except the thing when I type value of numberOfSignificantValueDigits
as magic 5
, this breaks my local es snapshot with out of memory exception - not a problem for the PR, but locally should increase the value of memory heap ).
I have only concerns around css here, IMHO it looks strange on different screen sizes.
Screen with high resolution (1920px) - I assume forms should be responsive:
Tablet (790px):
Mobile (the only percentile will take more than screen height):
But this is definitely a question to design team @cchaos
@sulemanof I agree, it's not great. I did emphasize making sure this layout worked well responsively. I'd consider continuing to tweak for all all screen sizes. |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]@kbn/optimizer bundle module count
async chunks size
History
To update your PR or re-run it, just comment with: |
* Add support for HDR percentiles in TSVB visualizations Closes: elastic#64238 * remove extra console.log * fix CI * fix PR comments * fix layout * remove legacy injectI18n * fix localization issues Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
* Add support for HDR percentiles in TSVB visualizations Closes: #64238 * remove extra console.log * fix CI * fix PR comments * fix layout * remove legacy injectI18n * fix localization issues Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
Closes: #64238
Summary
Having access to HDR percentiles can be more performant for some queries, as outlined in the Elasticsearch docs.
Describe a specific use case for the feature:
It would be really nice to have access to build these types of percentile aggregations in the TSVB visualization.
This is related to the more broad request #40612 of getting access to HDR support added to regular visualizations.
Screens
Checklist
Delete any items that are not applicable to this PR.
For maintainers