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

Do not remap empty messages #18

Closed
wants to merge 1 commit into from

Conversation

@ggtools
Copy link
Contributor

commented Sep 15, 2015

When en event includes a short_message and an empty full_message (like go-gelf when writing a single line message), remap sets message to an empty string while keeping short_message. This commits ensure that in this case message will be filled with short_message rather than an empty string.

Do not remap empty messages
When en event includes a `short_message` and an empty `full_message` (like [go-gelf](https://github.com/Graylog2/go-gelf) when writing a single line message), remap sets `message` to an empty string while keeping `short_message`. This commits ensure that in this case `message` will be filled with `short_message` rather than an empty string.
@ggtools

This comment has been minimized.

Copy link
Contributor Author

commented Sep 22, 2015

CLA signed

@elasticsearch-release

This comment has been minimized.

Copy link

commented Nov 2, 2015

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then say 'jenkins, test it'.

@xaka

This comment has been minimized.

Copy link

commented Dec 25, 2015

I've just encountered the same issue. It would be nice to get this one merged and released. Please 🍻.

@xkrt

This comment has been minimized.

Copy link

commented Jan 12, 2016

+1 please merge

@vervas

This comment has been minimized.

Copy link
Contributor

commented Feb 3, 2016

+1 same here

@elasticsearch-bot

This comment has been minimized.

Copy link

commented Feb 11, 2016

Jordan Sissel merged this into the following branches!

Branch Commits
master 03794c8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.