[ENGSUP-1947] Upgrade elastalert #3
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Use the alert_subject, and its associated args if present
Custom PagerDuty alert titles
Without this, the ES version lookup prevents the polling on the ElasticSearch status (ES must become responsive before we ask it for its version).
This will help users distinguish between two conditions: 1. ElasticSearch is not reachable; 2. ElasticSearch is reachable but the writeback index does not exist. Hopefully, this should help users take appropriate action (especially in case
Wait for provisioning
…mp_after_inactivity of inactivity
…vity Add jira_bump_after_inactivity field
…_alerter Feature/advanced post alerter
Improvements to post alerter
This commit adds support for a TLS certificate file and TLS key file, to be used for authenticating with the SMTP server.
Added a documentation clarification for import
Timestamp bug fix
Configurable subfield for string multi-fields
Support TLS cert and key in email alert
Prevent enhancements running again over retried failed alerts
Currently, Kibana can only query alerts by their creation time, not the time of the event. The event time is stored in the match_body, however that is not indexed. This change adds the match_time field to an alert, and adds it as indexed field to the ElasticSearch index. In order to make use of the indexin feature, you will have to reindex.
Add match_time to alert
Lowered the default bump_after_inactivity settings to 0 days
adds eval function to jira alerter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Upgrade to latest from upstream.