Skip to content

Conversation

@dylanjf
Copy link
Contributor

@dylanjf dylanjf commented Jan 14, 2019

hello!

This is hopefully the only followup to #2052 - one of our analysts noticed that the values outputted in the avg spike aggregation alert didn't make sense for percentage values (greater than 1.0).

Indeed, passing aggregated metrics through the spike tracker would only alert based on the total count over the timeframe... this makes sense for sum or value_count aggregations but nothing else. This is an issue for other aggregations if your EA config.yaml timeframe is shorter than the Spike Aggregation's timeframe.

I extended logic in the spike & event handler to support existing Spike alerts while also ferrying average, min, and max calculations over the EventWindow for Spike Aggregation alerts

@nsano-rururu
Copy link
Contributor

Test are failing

@nsano-rururu
Copy link
Contributor

Can you resolve conflicts please :)

@dylanjf
Copy link
Contributor Author

dylanjf commented Jan 22, 2021

@nsano-rururu updated the branch, builds passing.

@nsano-rururu
Copy link
Contributor

Merged into elastalert2.
jertel/elastalert2#45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants