Skip to content

Commit ba7e016

Browse files
Merge branch 'develop' into 'master'
Improve documentation and add badges See merge request back-end/elastalert!32
2 parents 73501d0 + acc85b4 commit ba7e016

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

README.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,12 @@
1-
# Elastalert Server
2-
**A server that runs [ElastAlert](https://github.com/Yelp/elastalert) and exposes REST API's for manipulating rules and alerts. It works great in combination with our [ElastAlert Kibana plugin](https://github.com/bitsensor/elastalert-kibana-plugin).**
1+
# ElastAlert Server
2+
3+
> A server that runs [ElastAlert](https://github.com/Yelp/elastalert) and exposes REST API's for manipulating rules and alerts. It works great in combination with our [ElastAlert Kibana plugin](https://github.com/bitsensor/elastalert-kibana-plugin).
4+
5+
![GitHub release](https://img.shields.io/github/release/bitsensor/elastalert.svg)
6+
![Docker Pulls](https://img.shields.io/docker/pulls/bitsensor/elastalert.svg)
7+
![GitHub stars](https://img.shields.io/github/stars/bitsensor/elastalert.svg?style=social&label=Stars)
8+
9+
---
310

411
## Installation
512
The most convenient way to run the ElastAlert server is by using our Docker container image. The default configuration uses `localhost:9200` as ElasticSearch host, if this is not the case in your setup please edit `es_host` and `es_port` in both the `elastalert.yaml` and `config.json` configuration files.

0 commit comments

Comments
 (0)