Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add alert handler to create Datadog Events #3164

Closed
wants to merge 192 commits into from

Conversation

3vanlock
Copy link

@3vanlock 3vanlock commented Apr 2, 2021

Create a new alerter that sends Datadog Events via their API.

dylanjf and others added 30 commits January 11, 2019 18:34
Add new page in documentation specifying the Elasticsearch Security Privileges required for ElastAlert
You just need to specify the images dir  and the mapping between images keys and values.
Example:
assets_dir: "/opt/elastalert/email_images"
email_image_keys: ["img1"]
email_image_values: ["my_logo.png"]


alert_text_args:
- "winlog.event_data.TargetDomainName"
- "winlog.event_data.TargetUserName"
- "starttime"

alert_text_args:
- "winlog.event_data.TargetDomainName"
- "winlog.event_data.TargetUserName"
- "starttime"

alert_text: |
    <p>L'utente {0}\{1} ha superato il numero massimo di tentativi di login al minuto (check-time: {2}).</p>
    <br><img src="cid:img1"><br>
…'append_middle' take into account the scenario whereby an event is None
…'append_middle' take into account the scenario whereby an event is None
Added options:
- http_post_ca_certs
- http_post_ignore_ssl_errors
This enables the user to silence a rule only for a specific query_key value and
not only the whole rule.
See Issue Yelp#2777
The Stride service was shutdown on February 15th, 2019.
jertel and others added 24 commits March 14, 2021 09:36
Remove unused items in alerta from schema.yaml
This brings in a change that's been applied on other forks (and opened on the
main Elastalert repo but not merged):

skillz#1
Yelp#2038

Without this fix, syntax errors are generated when document IDs that contain '-'
characters are seen by alerts that use the `aggregation` field.
Bumps [jinja2](https://github.com/pallets/jinja) from 2.10.1 to 2.11.3.
- [Release notes](https://github.com/pallets/jinja/releases)
- [Changelog](https://github.com/pallets/jinja/blob/master/CHANGES.rst)
- [Commits](pallets/jinja@2.10.1...2.11.3)

Signed-off-by: dependabot[bot] <support@github.com>
allow loading jinja templates from filesystem
sphinx 1.6.6 to 3.5.4
elasticsearch 7.0.0 to >=7.0.0,<8.0.0
…s_jertel_fork

added optional Prometheus metrics endpoint
fix compound query key in metric aggregation
@nsano-rururu
Copy link
Contributor

@3vanlock

Any way you could push this PR to https://github.com/jertel/elastalert ?

@3vanlock
Copy link
Author

Sure, no problem. Looks like it won't automatically merge, I'll get a new PR in to that repo.

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.