[operations] Cross-reference drifted dashboard JSON files in latency runbook

[kubestellar-hive]

What

Adds a cross-reference note to runbooks/api-error-rate-latency.md
pointing out that cluster-objects/dashboard.json and
cluster-objects/dashboard-docs-api.json visualize the same
docs_api_requests_total / docs_api_request_duration_seconds metrics
as cluster-objects/grafana-dashboard.json (already referenced in this
runbook), but with drifted titles, panel layouts, and — for the error
panel — a different definition of "error" (5xx-only vs. 4xx+5xx).

This mirrors the existing cross-reference this same runbook already has
for the three drifted PrometheusRule manifests (see the "Two other
PrometheusRule manifests..." paragraph a few lines above, added for
#6884).

Why

Confirmed finding: see #6891. An on-call engineer who opens whichever
dashboard they have bookmarked during a DocsApiHighRequestLatency or
DocsApiHighErrorRate page gets a different error-rate definition and
aggregation than what the alert evaluated, which is actively misleading
rather than merely redundant. Only grafana-dashboard.json has a
scrape-target-up panel matching DocsApiMetricsTargetDown.

Scope

• Runbook documentation only (runbooks/api-error-rate-latency.md).
• Does not change, delete, or merge any dashboard JSON file.
• Does not change any PrometheusRule alert threshold or
  .github/workflows/* file.
• Does not propose consolidating the dashboards — per operations
  policy, that decision (which dashboard is actually imported into a
  live Grafana instance) is left to a maintainer, tracked in [operations] Three drifted Grafana dashboard JSON files (dashboard.json, dashboard-docs-api.json, grafana-dashboard.json) disagree on error definition and granularity #6891.

Closes/refs: #6891

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

[kubestellar-hive]

Important

Held for human sign-off on the direction, not on the code.

This PR's only tracked rationale is #6891, which the hive filed itself — issue #6891 was filed by kubestellar-hive[bot] and no human has acknowledged it. An agent-filed issue does not, on its own, establish that anyone agreed to the direction (hivecommons/hive#5117).

The change may well be right; nothing here is a review of it. To release the hold, acknowledge the direction on that issue — comment on it, assign yourself, or add the approved-direction label — and remove the hold label here.

[netlify]

✅ Deploy Preview for kubestellar-docs ready!

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

[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 kproche 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

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

[kubestellar-prow]

PR needs rebase.

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.

[kubestellar-hive]

hold released: self-authorization hold disabled by config (#5117)