VictorOps: Set state_message and entity_display_name from rule #2212
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
|
Can someone have a look at it? |
|
@ChristophShyper |
|
Hi @nsano-rururu. Sorry for noticing your message so late, I've created a new PR with the same changes jertel/elastalert2#329 |
|
For anybody interested - since this project has been abandoned - it has been been fixed in https://github.com/jertel/elastalert2 |
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.
This change adds all data gathered from ElasticSearch to VictorOps's payload, which then can be used easily with transmogrifier (line 1578).
If
victorops_entity_display_nameis not set thenentity_display_nameis taking value ofalert_subject. Or randomized by VictorOps.