Cherry-pick #23334 to 7.x: [Filebeat] Add postgresql csv fileset #24088
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 #23334 to 7.x branch. Original message:
As a configuration option, create another pipeline inside the module to
parse CSV log files.
Although it's necessary to configure the database to emit such logs,
there is some advantages: configured properly, some events like
statement timeout
andlock timeout
will display the query in thesame event, opposed to multiple lines, one with the error message and
other with statement.
What does this PR do?
This PR creates a new fileset/pipeline inside PostgreSQL module. This new fileset parses and create events based on CSV log files from postgresql.
Why is it important?
PostgreSQL logs weren't designed to be parsed, so, without very complicated logic, it's not possible to encapsulate all information in just one event. One example of that is
statement timeout
:Using the CSV log, those 2 lines become 1:
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist