Fix a bug in splitting line on S3 file with DD_MULTILINE_LOG_REGEX_PATTERN #811
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?
Fix a parsing issue for a S3 file with
DD_MULTILINE_LOG_REGEX_PATTERN
environment variable, which is introduced by the refactoring at 196c633Motivation
My log files in S3 bucket was parsed wrongly and ingested to Datadog Log when I upgraded the version from 3.108.0 to 3.116.0. Strictly speaking, the issue was introduced from 3.113.0 [diff].
Testing Guidelines
Since this is a very small change, I didn't wrote any test code. Instead, I paste the sample code here for easier understanding
Additional Notes
This problem happens only when
DD_MULTILINE_LOG_REGEX_PATTERN
is given but the content of file doesn't match it.Types of changes
Check all that apply