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.

Sign up for GitHub

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

Jump to bottom

[Lens] When field metadata indicates a metric_type: counter, default to suggesting counter rate #82347

Open
wylieconlon opened this issue Nov 2, 2020 · 1 comment
Open

[Lens] When field metadata indicates a metric_type: counter, default to suggesting counter rate #82347

wylieconlon opened this issue Nov 2, 2020 · 1 comment
Labels
enhancement New value added to drive a business result Feature:Lens impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
Lens

Comments

@wylieconlon
Copy link
Contributor

Lens should use the standard metadata that is defined across the stack in a few ways. For numbers that we know are counters, the simplest option is to change our suggestion logic to always recommend a counter rate.

This issue depends on:

  1. Storing meta in the index pattern
  2. Implementing counter rate in Lens
@wylieconlon wylieconlon added enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Nov 2, 2020
@wylieconlon wylieconlon added this to Long-term goals in Lens via automation Nov 2, 2020
@elasticmachine
Copy link
Contributor

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

@flash1293 flash1293 mentioned this issue Nov 3, 2020
Closed
@stratoula stratoula added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Jun 6, 2023
@stratoula stratoula added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jan 30, 2024
@timductive timductive removed the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result Feature:Lens impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
No open projects
Lens
  
Long-term goals
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wylieconlon @timductive @elasticmachine @stratoula