Update postgresql.yaml to reduce number of Grok Parser Samples #21970
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
Removing a log sample from the first Grok Parser of the Postgresql Integration Pipeline. Grok Parsers allow a maximum of 5 log samples but this Grok Parser currently contains 6 samples. If a user clones this pipeline and edits any processor within it, they will be unable to save changes to the pipeline. The sample that is removed was listed as the second sample but falls under the same rule as the first sample (default_format)
wilskong
changed the title
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
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.
What does this PR do?
PR removes a log sample from the first Grok Parser of the Postgresql Integration Pipeline.
Grok Parsers allow a maximum of 5 log samples but this Grok Parser currently contains 6 samples. If a user clones this pipeline and edits any processor within it, they will be unable to save changes to the pipeline.
The sample that is removed was listed as the second sample but falls under the same rule as the first sample (default_format)
Motivation
A customer cloned the Postgresql Integration Pipeline recently and was unable to save changes to their clone. The error that was returned read "Creation of processor could not be completed successfully" without additional context.
see https://datadoghq.atlassian.net/browse/LOGSS-9623 for more details.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged