Updating IRIS Alerter to use ElastAlert Alerter defaults #1532
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently the IRIS alert uses rule supplied values for the description and simply uses the rule title for the alert title. This significantly reduces the ability to dynamically create/repurpose alerts as the rule creator must tailor each individual alert with a custom description. Additionally this description field as it stands does not resolve any variable or template fields resulting in a static description for all alerts.
This PR aims to resolve this by using the built in create_alert_body() and create_title() functions within the Alerter class.
As this is possibly a breaking change I'm opening this PR as a draft for discussion.
Checklist
make test-docker
with my changes.Questions or Comments
Do not merge this PR until discussed! :)I think this should be complete now. The defaults should be close enough to the current functionality and is more in line with expectations with the ElastAlert ecosystem.