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

Params inclusion affects chart #60203

Closed
arisonl opened this issue Mar 14, 2020 · 3 comments · Fixed by #60666
Closed

Params inclusion affects chart #60203

arisonl opened this issue Mar 14, 2020 · 3 comments · Fixed by #60666
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.7.0

Comments

@arisonl
Copy link
Contributor

arisonl commented Mar 14, 2020

Inclusion of context parameters in the action impacts the condition chart:

params

@arisonl arisonl added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Mar 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@arisonl arisonl added the bug Fixes for quality problems that affect the customer experience label Mar 14, 2020
@peterschretlen
Copy link
Contributor

It looks like this is happening because the x-axis range is only about 30 seconds.

It's hard to tell from the screenshot but likely the "check every" value is a low value like 1 second, and so this is by design. With a higher check interval, the graph will be more stable.

Maybe when "check every" is very small, we'd want to increase the x-axis range to make it appear more stable.

@pmuellr
Copy link
Member

pmuellr commented Mar 18, 2020

I've seen this sort of thing also if you change the interval up or down. Didn't investigate, but that one was a little understandable, as changing the interval is the only way the date range scale will change in the viz graph (currently) - the longer the interval, the greater the date range (we show ~30 intervals worth of time in the graph). I suspected the time range start/stop was somehow being sticky, or getting updated independently of the returned graph data.

For this one, it seems like the date range in the graph is changing, but new data isn't being retrieved. I wonder if it's going to seem "jumpy" that as you edit the action params, the graph will jump around.

In general, I like seeing the graph data "live", was thinking we could update it every 5 seconds or something, independent of everything else.

@gmmorris gmmorris self-assigned this Mar 19, 2020
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.7.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants