[Lens] Alerting from Lens Visualizations

[VijayDoshi]

As Lens becomes our desired default visualization experience users will inevitably want to author Alerts based on Lens visualizations.

This is a request to evaluate the relative prioritization for enabling Alerting in Lens visualizations, it seems inadvisable to make Lens the default editor without this capability in my opinion. You could imagine building a series of dashboards using lens visualizations and then the user experience is "oh, you want to alert - go rebuild your visualizations in this other tool to do that." - not a great experience.

Alerting is currently built using Elasticsearch DSL, not Expressions. They have a long term goal to support Expressions; however, that is not the current state. Coordination/prioritization may need to occur across teams to ensure alignment of prioritization of Alerts supporting Expressions if that is the expected state for Lens to support Alerts.

@wylieconlon @AlonaNadler @rayafratkina

[elasticmachine]

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

[AlonaNadler]

Alerting in Lens/Dashboard and Discover is high priority. Adding @lukeelmers since he is working on fleshing the details of alerting in Analyze

[lukeelmers]

I've started meta issues to track MVPs for alerting in Discover and on Dashboards (the latter of which would include Lens).

Alerting is currently built using Elasticsearch DSL, not Expressions. They have a long term goal to support Expressions; however, that is not the current state. Coordination/prioritization may need to occur across teams to ensure alignment of prioritization of Alerts supporting Expressions if that is the expected state for Lens to support Alerts.

More details are in the meta issue, but just wanted to mention that the plan we came up with doesn't require first-class support for Expression-based alerts -- rather, we'd only need the Expressions service to be made available to alert executors. This will still involve coordination with the alerting team, but would presumably require less effort.

[ghudgins]

+1 from someone who wants to, post discovery & analysis in lens, create an alert based on the aggregation (in Lens) to speed up the process from discovery to action. CC @bvader

[wylieconlon]

Currently blocked for technical reasons by #97134, but this also needs investigation at the product level to define what the user flow should be.

[ghudgins]

I will start a requirements doc on this

[TailyFair]

Any updates regarding this? Huge priority for our use-case.

[ghudgins]

We're on the precipice of releasing alerts support from discover first in an upcoming minor release. From there we are looking at extending this support into Lens.

If you don't mind, I would love to hear more about your use case--to ensure we aren't missing anything from a requirements standpoint. email me and we can discuss - graham@elastic.co

[jayakrishnamanokaran]

Hi, could you please give an update on when this feature will be released?

[stratoula]

It is not on our immediate roadmap unfortunately, the team is focused on other key areas but it is on our radar. We will update the issue when we will start working on it