pipeline: podman metrics: document exclude_name_regex option

[stondo]

Summary

Documents the new exclude_name_regex configuration option for the
in_podman_metrics (Podman metrics) input plugin.

Companion to the code change in fluent/fluent-bit#11970.

The option skips containers whose name matches a user-supplied regular
expression before their metrics are collected, for example
exclude_name_regex '-(infra|service)$' to skip Podman pod infrastructure
(pause / catatonit) containers. It defaults to unset, so existing behaviour
(collect every container) is unchanged.

Change

Adds an exclude_name_regex row to the Configuration parameters table in
pipeline/inputs/podman-metrics.md.

---

Signed-off-by: Stefano Tondo stondo@gmail.com

Summary by CodeRabbit

• New Features

  • Added configuration parameter to exclude containers by name using regular expression patterns before metrics collection. When unset, all containers are included.

• Documentation

  • Updated Podman metrics input documentation with new container exclusion option details.

[coderabbitai]

Warning

Review limit reached

@eschabell, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 48 minutes and 23 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fea456ba-a307-4d15-a242-fb445aad639d

📥 Commits

Reviewing files that changed from the base of the PR and between 424425a and 89a346b.

📒 Files selected for processing (1)

• pipeline/inputs/podman-metrics.md

📝 Walkthrough

Walkthrough

A single row is added to the configuration parameters table in pipeline/inputs/podman-metrics.md, documenting the exclude_name_regex option that filters containers by name via regex before metrics collection, with a default of _none_.

Changes

Podman Metrics Input Documentation

Layer / File(s)	Summary
Document exclude_name_regex config parameter pipeline/inputs/podman-metrics.md	Adds a table row for exclude_name_regex, describing its regex-based pre-collection container name exclusion and its default value of _none_.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 A regex row, so small and neat,
Tucked into the table, tidy and fleet.
Exclude by name before you collect,
With _none_ as default — perfect, correct!
The docs hop forward, one line at a time~ 🌿

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding documentation for the exclude_name_regex option to the Podman metrics input configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[eschabell]

@stondo fixed a lint issue, but now ready to go, thanks for the doc PR! Waiting only on code PR merging.