in_systemd: review processing updates to config parameter table.

[eschabell]

Fixed a few descriptions in the config parameters table as requested in reviews.

Fixes #2214.

Summary by CodeRabbit

• Documentation
  • Improved systemd input plugin documentation with clarified explanations for database synchronization configuration options and tag behavior with wildcards.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Documentation update to the systemd input plugin, clarifying the db.sync enumeration phrasing and restating tag behavior with wildcard patterns without altering functionality.

Changes

Cohort / File(s)	Summary
Systemd input plugin documentation pipeline/inputs/systemd.md	Updated db.sync description from "Values" to "Possible values" for clarity; reworded tag description to explicitly state Fluent Bit's use of tags and clarify wildcard behavior

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Updating general layout and case for config options in systemd input plugin docs. Fixes #2214. #2228: Parallel modifications to systemd input plugin documentation covering db.sync configuration and tag behavior clarifications.

Suggested reviewers

• alexakreizinger
• cosmo0920

Poem

📚✨ A rabbit hops through docs so clear,
Where "Possible values" bring cheer!
Tags and wildcards, now understood,
The systemd path reads twice as good! 🐰

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR description states it fixes issue #2214 about Systemd input plugin, but the actual changes are documentation clarifications to config parameters, which diverges from the stated objective about journal cursor handling.	Clarify the connection between the config parameter documentation updates and the journal cursor objective from issue #2214, or verify this PR addresses the correct linked issue.
Out of Scope Changes check	❓ Inconclusive	Documentation updates to systemd.md config parameter descriptions are in scope for fixing issue #2214 per PR description, though the connection between parameter clarifications and journal cursor functionality is unclear.	Verify whether documentation-only changes to config parameters are the intended scope for resolving the journal cursor objective mentioned in issue #2214.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: documentation review updates to the in_systemd config parameter table.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1cfd26c and 833a3d7.

📒 Files selected for processing (1)

• pipeline/inputs/systemd.md (2 hunks)

🔇 Additional comments (2)

pipeline/inputs/systemd.md (2)

12-12: Improved clarity on db.sync parameter values.

The change from "Values" to "Possible values" better communicates that the listed items (extra, full, normal, off) are enumerated options. The enumeration remains consistent and complete.

---

21-21: Excellent clarification of tag wildcard behavior.

The expanded description now explicitly explains the Systemd-specific capability: wildcard expansion with _SYSTEMD_UNIT values. The concrete example (host.* => host.UNIT_NAME) and the fallback behavior (host.unknown) are clear and actionable.

The description aligns well with the documented examples below (lines 35 and 57), which both use tag: host.* with _SYSTEMD_UNIT=docker.service, demonstrating the wildcard expansion in practice.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}