Cherry-pick #13069 to 7.3: [Filebeat] Postgres uses a too permissive multiline pattern #13114
Conversation
This file contains 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
sayden
added
Team:Integrations
jsoriano
approved these changes
Jul 31, 2019
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…issive multiline pattern (elastic#13114)
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.
Cherry-pick of PR #13069 to 7.3 branch. Original message:
See #12078 for more info.
This PR adds the line mentioned in the issue above and one of the solutions.
After some experimenting, I thought it was better to be more explicit about the pattern and to capture next line only if they are dates, which is our only tested and known behavior. We can open this pattern to something more complex, generic once we found more examples.