docs: fix traciing typo in tracing config key

[latent-9]

The top-level tracing configuration key in the config reference is misspelled traciing (double i):

# Optional tracing configuration.  Configures distributed tracing for Alertmanager.
[ traciing: <tracing_config> ]

The actual key is tracing — see config/config.go (TracingConfig ... yaml:"tracing,omitempty"), and the surrounding comment and the <tracing_config> type anchor both use tracing. A config copied from the docs currently fails to load with an unknown-field error. Fixed the key to tracing.

Signed-off-by: latent-9 296084221+latent-9@users.noreply.github.com

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9cf8e391-fa62-475f-9e23-bd8f8f151dca

📥 Commits

Reviewing files that changed from the base of the PR and between 846bdbf and 4428754.

📒 Files selected for processing (1)

• docs/configuration.md

---

📝 Walkthrough

Walkthrough

The documentation corrects the top-level tracing configuration key from traciing to tracing.

Changes

Tracing documentation

Layer / File(s)	Summary
Correct the tracing configuration key docs/configuration.md	The documented key changes from traciing to tracing.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• prometheus/alertmanager#5314: This PR corrects the tracing configuration key documented by that PR.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the typo and its impact, but it omits the required checklist and release-notes section.	Use the repository template, complete all applicable checklist items, and add a release-notes block with NONE or an appropriate bugfix entry.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the documentation area and the specific traciing typo fix.
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.

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