Conversation
f39d3a8 to
fa576d4
Compare
7aabc47 to
5c5ecb5
Compare
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
I'll summary all the pending issues in follow ups in this list:
|
MichaelMarcialis
left a comment
There was a problem hiding this comment.
Thanks for making those last changes. Along with the list of follow-up issues, this looks good to me.
|
@elasticmachine merge upstream |
|
merge conflict between base and head |
|
Failed jest tests look not related to this PR, nor Lens. Will try to rerun the CI. |
|
jenkins, test this |
|
I don't think we have to address these on the PR, but we should address them before the release. So if we want to merge without a fix for them, we should create follow-up bug issues to fix in separate PRs. Otherwise this looks great to me - extremely useful feature! |
Fixed this in the PR as it was very localized and only few lines changed. |
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
History
To update your PR or re-run it, just comment with: |
flash1293
left a comment
There was a problem hiding this comment.
The fix works fine for me, approving as long as we create follow-up issues for the stuff we know we want to adjust.
Co-authored-by: Marta Bondyra <marta.bondyra@gmail.com> Co-authored-by: dej611 <dej611@gmail.com> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Co-authored-by: Marta Bondyra <marta.bondyra@gmail.com> Co-authored-by: dej611 <dej611@gmail.com> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Marta Bondyra <marta.bondyra@gmail.com> Co-authored-by: dej611 <dej611@gmail.com> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
|
@mbondyra this looks and works great, do we have any plans to allow additing text annotation to the thresholds lines? Specifically i am looking to recreate something like this in lens |
|
@shahzad31 while not originally planned, it makes sense to consider it. Will open a new enhancement issue for that. |
monfera
left a comment
There was a problem hiding this comment.
Please, in a follow-up PR, consider replacing "Threshold" on the UI with a truthful word such as "Reference value" or "Reference line" or [subject to discussion], we shouldn't be so inaccurate with our terms on the UI as it leads to poor user experience, see #87548 (comment) cc @dej611 @flash1293 (The code internals are not my concern, though it's good practice to reflect the proper words of the domain, not random words)



Summary
Built from @dej611 PR
Fixes #87551
Threshold as new layer type

Thresholds can be line or area
Tasks:
ThresholdDuplicatedimension on threshold layer does not work properlyhttps://user-images.githubusercontent.com/4283304/132191929-8bca0ba2-5b19-4642-8d73-be209c8b685c.mp4
Notes
hackto force a rerender (forceRender) on top of anotherhackwe use to delay the rendering in some circumstances. I tried to investigated various routes, but they all leads to some UI flickering due to theupdateDatasourceAsyncfunction: the new flag forces a sync update for the redux store rather than async.Checklist
Delete any items that are not applicable to this PR.