fix: remove invalid label field from non-pipeline component config examples

[mfernest]

Summary

The `label` field is only valid for `inputs`, `outputs`, and `processors`. A bug in the doc-tools generator (docs-extensions-and-macros#176) causes it to be unconditionally added to the example YAML for all component types.

This PR removes the invalid `label: ""` from all affected component type examples:

Type	Files fixed
`metrics`	10 (5 common + 5 advanced)
`caches`	38 (19 common + 19 advanced)
`buffers`	6 (3 common + 3 advanced)
`tracers`	8 (4 common + 4 advanced)
`rate-limits`	4 (2 common + 2 advanced)
`scanners`	16 (8 common + 8 advanced)
Total	76 files

The `metrics` fix was originally reported by a community member via Slack. See DOC-1978.

Also fixes the `prometheus` Common tab example to use `prometheus: {}` (empty map) instead of bare `prometheus:` (empty scalar).

Test plan

• Verify metrics, caches, buffers, tracers, rate-limits, and scanner pages no longer show `label: ""` in their config examples
• Verify the prometheus Common tab shows `prometheus: {}`
• Confirm inputs, outputs, and processors examples still show `label: ""` (valid for those types)

🤖 Generated with Claude Code

Page previews

• prometheus (metrics) — example of a metrics page with label removed
• ttlru (cache) — example of a cache page with label removed

[netlify]

✅ Deploy Preview for redpanda-connect ready!

Name	Link
🔨 Latest commit	73addc1
🔍 Latest deploy log	https://app.netlify.com/projects/redpanda-connect/deploys/69a87d656f2ea9000883be15
😎 Deploy Preview	https://deploy-preview-381--redpanda-connect.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request removes empty label fields from metrics configuration examples across ten YAML files. The affected files span two directories (advanced and common) and cover five metrics types: AWS CloudWatch, InfluxDB, Logger, Prometheus, and StatsD. Additionally, the prometheus.yaml file in the common metrics directory changes the prometheus configuration value from an implicit empty value to an explicit empty object.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately summarizes the main change: removing invalid label fields from non-pipeline component configuration examples.
Description check	✅ Passed	The pull request description clearly explains the purpose: removing invalid label fields from metrics and other component examples due to a doc-tools generator bug.

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

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/doc-1978-metrics-label-field

---

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

[Feediver1]

@mfernest Who is the eng SME for this one? All PRs that add or change technical content require at least one SME approval.

[prakhargarg105]

lgtm

[Feediver1]

lgtm