Skip to content
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

Merged
merged 14 commits into from
Jun 17, 2021

Conversation

dej611
Copy link
Contributor

@dej611 dej611 commented Jun 4, 2021

Summary

Fixes #100880

  • Adds some Color continuity explanation

Screenshot 2021-06-04 at 12 48 00

  • Adds some troubleshooting for edge cases when using dynamic coloring

Checklist

Delete any items that are not applicable to this PR.

@dej611 dej611 added Team:Visualizations Visualization editors, elastic-charts and infrastructure v8.0.0 release_note:skip Skip the PR/issue when compiling release notes Feature:Lens v7.14.0 auto-backport Deprecated - use backport:version if exact versions are needed labels Jun 4, 2021
@dej611 dej611 requested review from KOTungseth and a team June 4, 2021 10:52
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)


[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?
Copy link
Contributor

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

Copy link
Contributor Author

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?

Copy link
Contributor

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

@dej611
Copy link
Contributor Author

dej611 commented Jun 7, 2021

@elasticmachine merge upstream

@dej611
Copy link
Contributor Author

dej611 commented Jun 7, 2021

Used the value-based coloring name as for now, as it can also apply to future other visualizations.

@dej611
Copy link
Contributor Author

dej611 commented Jun 9, 2021

@elasticmachine merge upstream

Copy link
Contributor

@KOTungseth KOTungseth left a 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!


[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?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
===== 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 Show resolved Hide resolved
docs/user/dashboard/lens.asciidoc Outdated Show resolved Hide resolved
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".
Copy link
Contributor

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?

Copy link
Contributor Author

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 Show resolved Hide resolved

* 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 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 Show resolved Hide resolved
docs/user/dashboard/lens.asciidoc Outdated Show resolved Hide resolved

** 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
** 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.

dej611 and others added 6 commits June 15, 2021 10:35
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>
@dej611
Copy link
Contributor Author

dej611 commented Jun 15, 2021

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
lens 1.4MB 1.4MB +462.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@dej611 dej611 requested a review from flash1293 June 15, 2021 12:51
@dej611 dej611 enabled auto-merge (squash) June 17, 2021 08:12
@dej611 dej611 disabled auto-merge June 17, 2021 08:12
Copy link
Contributor

@flash1293 flash1293 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dej611 dej611 merged commit 7f62553 into elastic:master Jun 17, 2021
@dej611 dej611 deleted the lens/coloring-more-doc branch June 17, 2021 08:27
kibanamachine added a commit to kibanamachine/kibana that referenced this pull request Jun 17, 2021
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine
Copy link
Contributor

💚 Backport successful

Status Branch Result
7.x

This backport PR will be merged automatically after passing CI.

jloleysens added a commit to jloleysens/kibana that referenced this pull request Jun 17, 2021
…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
kibanamachine added a commit that referenced this pull request Jun 17, 2021
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed Feature:Lens release_note:skip Skip the PR/issue when compiling release notes Team:Visualizations Visualization editors, elastic-charts and infrastructure v7.14.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Lens] Better description of what color continuity is in dynamic coloring
5 participants