[hivecommons-hive]

Summary

cluster-objects/prometheusrule.yaml (added in #6746) defines two
alerts — DocsApiHighErrorRate and DocsApiHighRequestLatency — over
the docs site's instrumented search/docs-image API routes, but
neither had a runbook_url annotation or a dedicated diagnosis doc.
Every other alerting mechanism in this repo (generate-leaderboard.yml,
generate-acmm-history.yml, and the scorecard/stale-workflow monitoring
runbooks) links a runbook — these two alerts were the outlier.

• Adds runbooks/api-error-rate-latency.md: detection/diagnosis steps
  specific to the two instrumented routes (what a 500 vs. elevated
  latency means for search vs. docs-image, and when to instead
  follow runbooks/deploy-rollback.md for a shared root cause), plus
  recovery guidance.
• Adds a runbook_url annotation to both alerts pointing at the new doc.
• Indexes the new runbook from the README's Operational Readiness section.

Why this is operations scope

This is documentation and an alert annotation only — no alert threshold,
condition, or severity is changed or weakened, and no exporter/external
data flow is added. Matches the allowed "user-impact alert rules with
runbook links" and "runbooks/*.md" scope.

Validation

• python3 -c "import yaml; yaml.safe_load(open('cluster-objects/prometheusrule.yaml'))" passes.
• Manually reviewed src/app/api/search/route.ts and
  src/app/api/docs-image/[...path]/route.ts to confirm the
  documented 500-status causes match the actual catch handling in
  each route.

I will not merge this PR myself.

— hive: agent=operations backend=copilot model=claude-sonnet-4-6

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubestellar-docs ready!

Name	Link
🔨 Latest commit	25e143d
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6a9d1536a256f200089bd0a4
😎 Deploy Preview	https://deploy-preview-6753--kubestellar-docs.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.

[kubestellar-prow]

Hi @kubestellar-hive[bot]. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

Thank you for your contribution! Your PR has been merged.

Check out what's new:

• KubeStellar Console — Live multi-cluster dashboard
• Marketplace — Community extensions
• Knowledge Base — Troubleshooting and how-tos

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey