Add PMM HA Cluster messaging for GA launch (#197)#229
Draft
brianamarie wants to merge 2 commits into
Draft
Conversation
Draft positioning for PMM platform high availability ahead of GA, including product claims, reliability-pillar propagation, and ExpertOps operational scope. Supports the messaging lane for #197; merge with the HA GA release once product confirms scope and factual claims. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
New File Governance CheckNo added markdown files detected. Doc Coverage CheckNo new markdown docs detected. Manual waiver commands (maintainers)
Waiver JSON is stored in a hidden PR comment ( Triggered by |
Contributor
|
{ |
Contributor
Messaging Smart Suggestions
Only auto-apply suggestions at high confidence with reviewer approval. Triggered by |
brianamarie
commented
Jul 7, 2026
| - Percona Advisors and reliability: Beyond metrics and QAN, advisor checks flag misconfigurations, degradation, and query-level problems like data loss and corruption early. Runs use configurable intervals or manual execution for engines in inventory, adding rules-based review alongside dashboards and analytics. | ||
| - Engine-native replication metrics: PMM leverages each engine's native capabilities for replication monitoring. For PostgreSQL, PMM reads `pg_stat_wal_receiver` data via custom queries in `postgres_exporter` (namespace: `pg_custom_stat_wal_receiver`, columns include `lag_bytes`), providing accurate replication lag measurement without requiring external heartbeat tools. This is a concrete advantage for MySQL-to-PostgreSQL migration stories: PostgreSQL's built-in replication instrumentation replaces the need for tools like pt-heartbeat. *(Source: `postgres_exporter/queries-hr.yml#L32`; validated Feb 2026.)* | ||
| - HA visibility for incident response: PMM surfaces replication and node health signals that help teams validate high availability behavior and shorten failover diagnosis, especially where incidents involve multi-team handoffs between application, platform, and database owners. | ||
| - High availability for the PMM platform: PMM keeps dashboards, alerts, Query Analytics, and advisors reachable through PMM Server failures and maintenance windows. PMM HA Cluster runs three PMM Server replicas with automated leader election and load-balanced failover routing. Teams monitoring production MySQL, PostgreSQL, MongoDB, Valkey, and Redis estates keep observability when the monitoring layer itself fails, not only when a database node fails. Installation is Helm-based on Kubernetes, with operator-managed storage for metrics, query analytics, and Grafana metadata. |
Collaborator
Author
There was a problem hiding this comment.
@theTibi Please focus your review on this file, specifically these two PMM HA bullets on 21-22, and the the questions added in 48-51. Thank you!
Collaborator
Author
|
/impact-ok all |
Contributor
|
🤖 Recorded |
Contributor
Messaging Impact Check
licensing-or-open-source-claims (WARN)License and open source positioning changes are cross-cutting. Required review files:
Suggested additional scan:
offering-name-or-tier-change (WARN)Offering naming updates should stay aligned across offering pages. Required review files:
Suggested additional scan:
product-messaging-module-touch (WARN)Product messaging modules often need checks against company framing and shared pillars or offerings. Required review files:
Suggested additional scan:
Manual waiver commands (maintainers):
Waiver state is stored in Triggered by |
brianamarie
added
Content & messaging
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Warning
DO NOT MERGE UNTIL PMM 3.10 IS RELEASED
This messaging describes PMM HA Cluster as a shipped, generally available capability. It must not merge to
mainuntil PMM 3.10 is released, which is when HA becomes available. Merging earlier would put GA claims onmainbefore the feature ships.Summary
Draft canonical messaging for PMM HA Cluster GA (#197).
products/pmm/messaging.md— source of truth: PMM platform HA bullets, deployment-option contrast (Docker HA / Kubernetes single-instance / HA Cluster), sales enablement, and a rename of the existing database-HA bullet so platform HA and database HA are not conflated.use-cases-value-pillars/performance-reliability.md— reliability-pillar propagation: problem, solution, and business-continuity use case.offerings/expertops/messaging.md— ExpertOps operational angle: problems, partnership scope, and a common scenario.Review ask for @theTibi
Please focus your review on
products/pmm/messaging.md, specifically the two PMM HA bullets under Performance and Reliability at Scale and the HA lines in Sales enablement.The other two files (
performance-reliability.md,expertops/messaging.md) are propagation: they mirror the product-file story in cross-portfolio and offering language. You can skip them unless something looks wrong. If the product claims change, I will update the propogated claims.