[AGNTLOG-229 Multiline features FAQ #29931
Open
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
DDuongNguyen
changed the title
📝 Documentation Team Review RequiredThis pull request requires approval from the @DataDog/documentation team before it can be merged. Please ensure your changes follow our documentation guidelines and wait for a team member to review and approve your changes. |
Preview links (active after the
|
DDuongNguyen
changed the title
urseberry
reviewed
Jun 16, 2025
Comment on lines
+636
to
+637
| If you know the format of your logs, you should use manual multi-line rules for more precise control. | ||
| If you are sending lots of multi-line logs and you are unsure of their format or don't have the means to configure all sources individually, you should use automatic multi-line detection. |
There was a problem hiding this comment.
Suggested change
| If you know the format of your logs, you should use manual multi-line rules for more precise control. | |
| If you are sending lots of multi-line logs and you are unsure of their format or don't have the means to configure all sources individually, you should use automatic multi-line detection. | |
| If you know the format of your logs, you should use manual multi-line rules for precise control. | |
| If you are sending lots of multi-line logs, and you are unsure of their format or don't have the means to configure all sources individually, you should use automatic multi-line detection. |
Comment on lines
+641
to
+642
| All non-JSON log lines will be processed individually as separate log entries. | ||
| All JSON-formatted log lines will be treated as a single line of logs, and only the first valid JSON format will enter the intake; the rest will be dropped. |
There was a problem hiding this comment.
Suggested change
| All non-JSON log lines will be processed individually as separate log entries. | |
| All JSON-formatted log lines will be treated as a single line of logs, and only the first valid JSON format will enter the intake; the rest will be dropped. | |
| All non-JSON log lines are processed individually as separate log entries. | |
| All JSON-formatted log lines are treated as a single line of logs, and only the first valid JSON format enters the intake; the rest are dropped. |
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? What is the motivation?
This PR adds a user-friendly FAQ section to the multi-line log aggregation documentation to help users better understand when and how to use different multi-line aggregation approaches.
The motivation is to reduce confusion and help users choose the right multi-line aggregation approach for their specific needs.
Merge instructions
Merge readiness:
Additional notes
This is a documentation-only change that improves clarity without modifying any functionality.