Support adding custom headers #57
Closed
Conversation
This file contains hidden or 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
|
Hello @ptv999duke Do you have an example of for what this could be used for? |
|
Our use case is that we need to attach unique ids to all the internal emails we send via logstash, for tracking/filing purposes. However, we've gotten requests that the unique id not be in a naturally visible location for the email. The best location we found was adding custom headers to the email. |
kingjan1999
added a commit
to kingjan1999/logstash-output-email
that referenced
this pull request
Oct 7, 2021
|
Any chance this can be merged in? |
|
@logstashmachine bump minor |
aramperes
reviewed
Jul 5, 2022
|
moved the change to #63 so it can be rebased against main. |
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.
Adds the ability to specify custom email headers based on available fields of the event.