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.

Sign up for GitHub

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

Jump to bottom

Messages with a timestamp of type String break processing #7364

Closed
mpfz0r opened this issue Feb 4, 2020 · 0 comments · Fixed by #7367
Closed

Messages with a timestamp of type String break processing #7364

mpfz0r opened this issue Feb 4, 2020 · 0 comments · Fixed by #7367
Labels
blocker If not finished by release date, the release will be postponed. bug processing
Milestone
3.2.1

Comments

@mpfz0r
Copy link
Contributor

mpfz0r commented Feb 4, 2020

Recent changes[0] to the ProcessBufferProcessor expect the timestamp field to always
be a DateTime object.

If the timestamp field is set via extractors or pipeline rules that do not explicitly convert
it to DateTime but rather leave it as String, the message processing breaks with:

WARN [ProcessBufferProcessor] Unable to process message <8e417510-46b9-11ea-ab74-005056b2950d>: java.lang.ClassCastException: Cannot cast java.lang.String to org.joda.time.DateTime

[0] Refs #7290

Possible Solution

As a workaround:

  • pipeline rules could be rewritten to use set the timestamp field by either a function that returns DateTime or be converted using the to_date function.
  • Extractors (where applicable) can be configured with a Date Converter

Affected Versions

  • Graylog Version: 3.2
@mpfz0r mpfz0r added processing bug blocker If not finished by release date, the release will be postponed. labels Feb 4, 2020
@mpfz0r mpfz0r added this to the 3.2.1 milestone Feb 4, 2020
@bernd bernd mentioned this issue Feb 4, 2020
Closed
mpfz0r added a commit that referenced this issue Feb 4, 2020
@mpfz0r
Partly revert timestamp based gl2_message_ids (#7290)
bdb4e1b 
Sometimes the message processing doesn't leave us
with a valid DateTime Object at this point.

Fixes #7364
@mpfz0r mpfz0r mentioned this issue Feb 4, 2020
Merged
mpfz0r added a commit that referenced this issue Feb 4, 2020
@mpfz0r
Partly revert timestamp based gl2_message_ids (#7290)
ebe8014 
Sometimes the message processing doesn't leave us
with a valid DateTime Object at this point.

Fixes #7364

(cherry picked from commit bdb4e1b)
@mpfz0r mpfz0r mentioned this issue Feb 4, 2020
Merged
bernd pushed a commit that referenced this issue Feb 4, 2020
@mpfz0r
Partly revert timestamp based gl2_message_ids (#7290) (#7367)
6defaa7 
Sometimes the message processing doesn't leave us
with a valid DateTime Object at this point.

Fixes #7364
@michael-markevich michael-markevich mentioned this issue Feb 6, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocker If not finished by release date, the release will be postponed. bug processing
Projects
None yet
Milestone
3.2.1
Development

Successfully merging a pull request may close this issue.

Partly revert timestamp based gl2_message_ids (#7290) Graylog2/graylog2-server
1 participant
@mpfz0r