You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+50-62Lines changed: 50 additions & 62 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,11 @@
1
1
# Elastalert Server
2
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).**
3
3
4
-
## Docker installation
5
-
The default configuration uses localhost as ES host. You will want to mount the volumes for configuration and rule files to keep them after container updates. In order to do that conviniently, please do a `git clone https://github.com/bitsensor/elastalert.git; cd elastalert`
4
+
## Installation
5
+
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 `config.yaml` and `config.json` configuration files.
6
+
7
+
To run the Docker image you will want to mount the volumes for configuration and rule files to keep them after container updates. In order to do that conveniently, please do: `git clone https://github.com/bitsensor/elastalert.git; cd elastalert`
ElastAlert supports additional arguments, that can be passed in the `config.json` file. An example is given in `config/config-historic-data-example.json`.
31
-
32
-
## Installation using npm and manual ElastAlert setup
33
-
34
-
### Requirements
35
-
-[ElastAlert v0.0.96](https://github.com/Yelp/elastalert/tree/v0.0.96). We don't support other versions of ElastAlert, use them at your own risk.
36
-
-[NodeJS 4.5.0](https://nodejs.org/en/download/) with NPM & NVM.
And run `pip install -r requirements.txt` or read the installation guide of ElastAlert.
87
-
88
-
### Config
47
+
## Configuration
89
48
In `config/config.example.json` you'll find the default config. You can make a `config.json` file in the same folder that overrides the default config. When forking this repository it is recommended to remove `config.json` from the `.gitignore` file. For local testing purposes you can then use a `config.dev.json` file which overrides `config.json`.
90
49
91
50
You can use the following config options:
@@ -117,6 +76,35 @@ You can use the following config options:
117
76
"writeback_index":"elastalert_status"// Writeback index to examine for /metadata endpoint
118
77
}
119
78
```
79
+
80
+
ElastAlert also expects a `config.yaml` with at least the following options.
81
+
```yaml
82
+
# The elasticsearch hostname for metadata writeback
83
+
# Note that every rule can have its own elasticsearch host
84
+
es_host: localhost
85
+
86
+
# The elasticsearch port
87
+
es_port: 9200
88
+
89
+
# The index on es_host which is used for metadata storage
90
+
# This can be a unmapped index, but it is recommended that you run
91
+
# elastalert-create-index to set a mapping
92
+
writeback_index: elastalert_status
93
+
94
+
# This is the folder that contains the rule yaml files
95
+
# Any .yaml file will be loaded as a rule
96
+
rules_folder: rules
97
+
98
+
# How often ElastAlert will query elasticsearch
99
+
# The unit can be anything from weeks to seconds
100
+
run_every:
101
+
seconds: 5
102
+
103
+
# ElastAlert will buffer results from the most recent
104
+
# period of time, in case some log sources are not in real time
0 commit comments