[hivecommons-hive]

What changed

Three separate PrometheusRule manifests in cluster-objects/ (alerts.yaml, prometheusrule.yaml, prometheusrule-docs-api.yaml) alerted on the same docs_api_requests_total/docs_api_request_duration_seconds metrics with drifted alert names and thresholds — including an exact alert: name collision (DocsApiHighErrorRate defined twice, with different semantics, in two different PrometheusRule objects). This drift was already confirmed in #6884, but that issue was closed with only runbook_url cross-links added (#6885, #6936) — the actual duplication was never fixed and is still present on main today.

• cluster-objects/alerts.yaml is now the single canonical PrometheusRule for all docs_api_*/docs_i18n_* app-metric alerts. Every distinct alert from the other two files was merged in, renamed only where needed to avoid a name collision. No threshold was loosened — the one alert dropped (DocsApiHighLatencyP95, p95>2s aggregate) was strictly subsumed by the merged-in 1s aggregate alert, which always fires at least as early.
• cluster-objects/prometheusrule-docs-api.yaml is removed entirely (fully folded into alerts.yaml).
• cluster-objects/prometheusrule.yaml now holds only the infra/platform alerts (DocsApiMetricsTargetDown, the two rollout-checker CronJob alerts) that reference metrics outside src/lib/metrics.ts (up{} / kube_cronjob_status_last_successful_time) — scripts/lint-dashboard.mjs's known-metric check only validates alerts.yaml against that file's declared docs_* metrics, so these can't be validated if moved there.
• Updated runbooks/api-error-rate-latency.md, runbooks/README.md, README.md, and cluster-objects/grafana-dashboard.json's panel titles/description to match the new canonical file and alert names.

Why

On-call visibility, not a cosmetic cleanup: if more than one of these manifests is ever applied to the same cluster, a single underlying condition fires under two or three different alert names at two or three different thresholds, with no single source of truth for "is the docs API actually degraded." The exact DocsApiHighErrorRate name collision between alerts.yaml (per-route) and prometheusrule.yaml (aggregate) was the sharpest version of this.

Verification

• npm run lint:dashboard passes (validates cluster-objects/alerts.yaml against src/lib/metrics.ts's declared metrics).
• npx vitest run scripts/lint-dashboard-helpers.test.mjs — 26/26 passed.
• Both remaining PrometheusRule YAML files parse and list the expected, non-colliding alert names (verified with python3 -c "import yaml; ...").
• npx markdownlint-cli2 on the changed runbook/README files — 0 issues.

Known limitation / follow-up

The dashboard-JSON side of the same drift class (#6891, #6928) is a separate, still partly-open gap: #6928's uid collision was fixed in #6967, but #6891's panel/aggregation drift across dashboard.json/dashboard-docs-api.json/grafana-dashboard.json was not, and editing those dashboards is outside this PR's scope (grafana-dashboard.json's panel titles/description were updated only because this PR's alert renames made them stale). Filing a separate issue for that.

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

[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	e001588
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6ac750a2634a800008018a62
😎 Deploy Preview	https://deploy-preview-7317--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 @hivecommons-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