Releases: bitsensor/elastalert
Releases · bitsensor/elastalert
3.0.0-beta.0
Breaking Changes
- Run ElastAlert server as
node
user. Thank you @jbdelpech (#81).
Changes
- Updated ElastAlert to v0.2.0b2 for ElasticSearch 7.0.0 support.
- Fix error when starting ElastAlert (#67).
Note
This is a beta pre-release with ElasticSearch 7 support. As such there will be bugs, testing rules for example is currently broken in ElastAlert v0.2.0b2 (Yelp/elastalert#2204 (comment)).
Installation
You can use this release by using bitsensor/elastalert:3.0.0-beta.0 in you Docker command.
2.0.1
2.0.0
Breaking Changes
- The ElastAlert server/container will now exit when it cannot connect to ElasticSearch successfully. Thank you @film42 (#79).
- Implemented websocket support to test rules and search route for doing ES searches. Note: This requires a change to your configuration (add
"wsport": 3333
to yourconfig.json
). Thank you @johnsusek (#50).
Changes
- Updated ElastAlert to v0.1.39.
- Now uses the configured
writeback_index
upon index creation. Thank you @alvarolmedo (#74).
1.0.0
Breaking Changes
- A different config file (
elastalert-test.yaml
) is used now when you test a rule using the API. Since the API will fail when this config is not available this is a breaking change. Documentation has been updated to reflect this change.
Changes
- Improved the documentation.
0.0.15
Changes
- Updates ElastAlert to v0.1.38
0.0.14
Breaking Changes
es_host
,es_port
andwriteback_index
must now be configured in bothelastalert.yaml
andconfig.json
. This configuration will be simplified in a future release.
Changes
- Improved the documentation.