Annaxs opened a new pull request, #1144: URL: https://github.com/apache/pulsar-site/pull/1144
## Motivation There is currently no documentation covering what operators should monitor during and after a Pulsar cluster upgrade. This gap means teams either rely on tribal knowledge or discover issues after they've impacted production traffic. ## Changes Adds a new page `administration-upgrade-observability.md` with: - **Pre-upgrade baseline guidance** — which metrics to record before starting - **Per-component monitoring** — what to watch during ZooKeeper, BookKeeper, broker, and proxy rolling upgrades (GC pause duration, ledger write latency, topic ownership rebalance, bookie disk pressure, client reconnect behaviour) - **Post-upgrade validation checklist** — CLI commands and metric thresholds to confirm cluster health - **Rollback decision criteria** — specific, actionable conditions that should trigger a rollback The page is added to the sidebar under the existing **Administration** section, immediately after the Upgrade Guide. ## Verifying this change The new page renders correctly and links to the existing Upgrade Guide, Monitoring, and Reference Metrics pages. --- Related discussion: [Apache Pulsar Slack – #dev, May 2026](https://apache-pulsar.slack.com) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
