mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-07 05:28:34 +00:00
uboness
aae6ff834f
[client] reorganized tests and added alert source builder
The `AlertSourceBuilder` along with a set of source builder for all the different constructs that make an alert (condition, input, transform and action), provides a structured approach for building an alert from the client side (instead of forcing the clients to use xcontent directory) - fixed some of the tests to already use these builders (I reckon there are still quite a few that need to be converted.. but we'll do that over time). - moved all integration tests under `test/integration` package. - changed the `AlertsTests` to **not** be an integration test... it randomizes the alert structure and makes sure that it can serialize & deserialize itself to/from xcontent. - fixed small bugs found by the tests Original commit: elastic/x-pack-elasticsearch@94b76b6fc7
= Elasticsearch Alerts Plugin This plugins adds alerting features to elasticsearch You can build the plugin with `mvn package`. The documentation is put in the `docs/` directory. == Core Concepts Alert :: a tuple of: *Schedule*, *Condition* and a list of *Action*s, where the schedule defines when the alert is checked (see below), the condition checks whether the alert should be executed and the actions define what happens when the alert is executed. Schedule :: defines when and how often should the alert be checked (e.g. every 5 minutes, every first wednesday of the month at noon, etc..) Input :: defines the source of a payload that can be associated with an alert and is loaded prior to condition check. The condition can then be checked agaist this data Condition :: represents a condition based on which a decision is made to execute the alert or not Action :: defines the actions that are taken when the alert executes == Alert Events `checked` :: the `Scheduler` fired an event that caused the condition of the alert to be evaluated `throttled` :: the alert's condition was checked and met, but a decision was made **not** to **execute* the alert. This can be based on the throttle period that is associated with the alert, or based on the fact that the alert was `acked` `executed` :: the alert's condition was checked and met and no throttling took place - the actions were executed. `acked` :: the user acked the alert, causing it to stop executing its action until it's condition is not met anymore == Alert Run Process image:docs/alert-run.png[]
Description
Languages
Java
99.5%
Groovy
0.4%