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

override timestamp to now for bad timestamp values #2065

Merged
merged 1 commit into from Apr 12, 2016

Conversation

Projects
None yet
2 participants
@kroepke
Member

kroepke commented Apr 12, 2016

If the timestamp field of a message is incompatible to the ES format we are using, or an unknown data type (non Date, DateTime or String), force the timestamp to be "now".

This prevents bad extractors or inputs from causing these malformed messages to be discarded.

fix #2064

@kroepke kroepke added this to the 2.0.0 milestone Apr 12, 2016

override timestamp to now for bad timestamp values
If the timestamp field of a message is incompatible to the ES format we are using, or an unknown data type (non Date, DateTime or String), force the timestamp to be "now".

This prevents bad extractors or inputs from causing these malformed messages to be discarded.

fix #2064

@bernd bernd self-assigned this Apr 12, 2016

@bernd

This comment has been minimized.

Member

bernd commented Apr 12, 2016

LGTM 👍

@bernd bernd merged commit fc94e57 into master Apr 12, 2016

4 checks passed

ci-server-integration Jenkins build graylog2-server-integration-pr 816 has succeeded
Details
ci-web-linter Jenkins build graylog-pr-linter-check 305 has succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@bernd bernd deleted the issue-2064 branch Apr 12, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment