-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Lens] Add some more documentation for dynamic coloring #101369
Conversation
Pinging @elastic/kibana-app (Team:KibanaApp) |
docs/user/dashboard/lens.asciidoc
Outdated
|
||
[float] | ||
[[why-my-value-is-not-of-the-right-color-using-dynamic-coloring]] | ||
===== Why mt value is not of the right color when using dynamic coloring? |
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.
Are we using the term "dynamic coloring" anywhere else? I don't think it's self-explanatory
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.
Fair point. I assumed here it will be in the release notes.
Probably I'd suggest then datatable coloring
, wdyt?
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.
Sounds good to me. Other things that would work IMHO:
- conditional coloring
- value-based coloring
- table cell coloring
@elasticmachine merge upstream |
Used the |
@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.
I made a few grammatical and structure suggestions, but otherwise, LGTM!
docs/user/dashboard/lens.asciidoc
Outdated
|
||
[float] | ||
[[why-my-value-is-not-of-the-right-color-using-value-based-coloring]] | ||
===== Why mt value is not of the right color when using value-based coloring? |
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 mt value is not of the right color when using value-based coloring? | |
===== Why is my value the incorrect color when using value-based coloring? |
docs/user/dashboard/lens.asciidoc
Outdated
There could be various reason for a specific value in the table to have a different color than expected. | ||
|
||
Here's a short list of few different aspects to check: | ||
* Make sure the value falls within the desidered color stop value defined in the panel. Color stop values are "inclusive". |
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.
I'm a little out of my realm here. Do users know what "inclusive" means when it comes to color stop 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.
Inclusivity, in this context refers to "ranges", so I would expect they are. I do not have a strong opinion here on the terminology, so if anything better comes I'm open.
docs/user/dashboard/lens.asciidoc
Outdated
|
||
* Make sure to have the right value precision setup: value formatters could round up or down numeric values. | ||
|
||
* Make sure the right color continuity option is selected: if the number is below the first color stop value a continuity of type `Below` or `Above and below range` is required |
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.
* Make sure the right color continuity option is selected: if the number is below the first color stop value a continuity of type `Below` or `Above and below range` is required | |
* Make sure the right color continuity option is selected: if the number is below the first color stop value, a continuity of type `Below` or `Above and below range` is required. |
docs/user/dashboard/lens.asciidoc
Outdated
|
||
** If a `Number` custom configuration is used, check the color stops value are covering the current data range. | ||
|
||
** If a `Percent` configuration is used, when the data range changes this has an effect on colors displayed. |
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.
** If a `Percent` configuration is used, when the data range changes this has an effect on colors displayed. | |
** If a `Percent` configuration is used, and the data range changes, the colors displayed are affected. |
x-pack/plugins/lens/public/shared_components/coloring/palette_configuration.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
…configuration.tsx Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
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.
LGTM
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…egrations-to-global-search * 'master' of github.com:elastic/kibana: (46 commits) [Lens] Add some more documentation for dynamic coloring (elastic#101369) hide not searchable results when no term (elastic#102401) [Lens] Fix Formula functional test with multiple suggestions (elastic#102378) Fix trusted apps modified by field displayed as a date field (elastic#102377) [Lens] Docs for time shift (elastic#102048) update readme of logs-metrics-ui (elastic#101968) Refactor observability plugin breadcrumbs (elastic#102290) [Index Patterns] Move rollup config to index pattern management v2 (elastic#102285) [Security Solution][Endpoint] Isolate Action should only be available to Platinum+ licenses (elastic#102374) [build] Updates Ironbank templates (elastic#102407) Update security best practices document (elastic#100814) [Enterprise Search] Set up initial KibanaPageTemplate (elastic#102170) [Reporting/Docs] Add section to troubleshooting guide to explain the StatusCodeError logs (elastic#102278) [DOCS] Updating Elastic Security Overview topic (elastic#101922) [Uptime] refactor Synthetics Integration package UI (elastic#102080) [Task Manager] Log at different levels based on the state (elastic#101751) [APM] Fixing time comparison types (elastic#101423) [RAC] Update alert documents in lifecycle rule type helper (elastic#101598) [ML] Functional tests - fix and re-activate alerting flyout test (elastic#102368) [Reporting] remove unused reference to path.data config (elastic#102267) ... # Conflicts: # x-pack/plugins/fleet/kibana.json
…02470) Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Summary
Fixes #100880
Checklist
Delete any items that are not applicable to this PR.