Capture LoggingEvent original timestamp + document Event Schema #15
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
| Was just about to create something similar to this. Pipeline timestamp drift on log4j events is a problem we're facing at the moment, and this solves it quite nicely. |
Member
| LGTM |
| Merged sucessfully into master! |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
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.
Collect the original timestamp without altering its format (milliseconds in a long), leaving the @timestamp setting/formatting to the date filter. This could cover the use case described in elastic/logstash#995
Also I tried to describe in simple asciidoc the event schema that is produced by this input.
It would be great if you could provide a more advanced template on how to document "structured-inputs".