docs: Add raw_message_key examples and update UDP/TCP output plugin docs#2613
Conversation
Signed-off-by: Tristan Phipson <tristanphipson@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughDocumentation updates add TCP/TLS getting started and raw message examples, and revise UDP raw_message_key wording and examples to use ChangesOutput documentation updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…usage example - Also fixed few linting issues. Signed-off-by: Tristan Phipson <tristanphipson@gmail.com> Signed-off-by: Eric D. Schabell <eric@schabell.org>
68f41af to
c27ee02
Compare
eschabell
left a comment
There was a problem hiding this comment.
@tristanphipson added small lifting fixes, but thanks for the doc PR, merging!
Changes
This PR updates and enhances the UDP and TCP output plugin documentation:
UDP Output Plugin:
$sign is required before the key nameraw_message_keytakes precedence over theformatpropertyTCP Output Plugin:
raw_message_keywith the TCP output pluginWhy
Users frequently need to send raw message payloads (e.g., syslog lines) instead of JSON-formatted output. The existing documentation lacked the
$syntax requirement, concrete examples for both UDP and TCP, and configuration file samples showing how to reference fields at different nesting levels, leading to configuration confusion and incorrect usage.Related
Related to general UDP and TCP output plugin documentation clarity and accuracy.
Summary by CodeRabbit
raw_message_key, including end-to-end YAML/CONF guidance and record accessor usage for top-level and nested fields.raw_message_keybehavior (raw payload sent;formatignored) and aligned examples with$record accessor syntax.