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] ML predictive layers #104816

Closed
Tracked by #184459
flash1293 opened this issue Jul 8, 2021 · 4 comments
Closed
Tracked by #184459

[Lens] ML predictive layers #104816

flash1293 opened this issue Jul 8, 2021 · 4 comments
Labels
enhancement New value added to drive a business result Feature:Lens 🧊 iceboxed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects

Comments

@flash1293
Copy link
Contributor

The Elastic stack ML integration provides functionality to predict a time series. Right now these ML jobs have to be configured in the ML app, separate from the often used Dashboard/Lens/Discover apps. Adding a separate "predictive" layer type in Lens would be a nice and intuitive integration of these capabilities in a prominent spot.

@flash1293 flash1293 added enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Jul 8, 2021
@flash1293 flash1293 added this to Long-term goals in Lens via automation Jul 8, 2021
@elasticmachine
Copy link
Contributor

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

@wylieconlon
Copy link
Contributor

wylieconlon commented Jul 8, 2021

@flash1293 Are you referring to anomaly detection and forecasting as "predictive layers"? I think both of them fall into the category of solution-specific datasources. It is technically possible for a user to work around this if:

  1. They have defined an ML index pattern, which is not usually done
  2. They are able to filter to a specific model's results using KQL, for example result_type: model_plot instead of result_type: model_forecast.
  3. They are able to select the date histogram + min/max aggregation to create a "bounded" prediction for each time range.

But I think that overall users would be happier if they could follow a simpler set of steps, for example:

  1. Select from a dropdown of existing ML jobs
  2. Select the type of data to load, for example "anomalies", "predicted trends" or "forecast"

@flash1293
Copy link
Contributor Author

@wylieconlon I was focused on the forecasting, but it makes sense to broaden the scope.

@drewdaemon drewdaemon added loe:needs-research This issue requires some research before it can be worked on or estimated impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Feb 9, 2023
@timductive timductive added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Sep 20, 2023
@markov00
Copy link
Member

markov00 commented Jun 3, 2024

In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed.

Tracking request in Lens general improvements ice box #184459

@markov00 markov00 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Lens 🧊 iceboxed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
No open projects
Lens
  
Long-term goals
Development

No branches or pull requests

6 participants