Repository navigation
pmm-operations: fix upgrade, migration, port and path claims - #27
Merged
EvgeniyPatlan merged 3 commits intoNov 11, 2026
Merged
Conversation
- Watchtower and UI upgrades removed in PMM 3.9.0; upgrade by pulling percona/pmm-server:3 and recreating the container - OVF appliance removed in 3.9.0 - 2->3 is an official data-preserving migration (2.44.1 -> 3.7 -> latest), available until 3.13.0; PMM 2 EOL 2025-10-31 - /srv ownership is 1000:0 - 8443 is the in-container port; host publishes 443 - confirm PMM 3 custom-queries path, add custom-queries/mysql segment for PMM 2 - ARM64 server image since 3.10.0; advisors built in since 3.5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
EvgeniyPatlan
approved these changes
Nov 11, 2026
EvgeniyPatlan
left a comment
Collaborator
There was a problem hiding this comment.
Looks good. Nits:
- The description reads as if 2.44.1 → 3.7 → latest is mandatory. 3.7.0 is only the fallback path.
- Pre-existing: a few places say PMM 2 clients can't work with a PMM 3 server. They do, with limited support (metrics and QAN).
Needs a rebase after #17.
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
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.
Correctness fixes for
pmm-operationsfrom a fact-check against docs.percona.com. Each change was checked against the page cited.Changes
PMM_WATCHTOWER_*sentence, the "Home-dashboard update panel" upgrade, and theDOCKER_API_VERSION+ Watchtower gotcha. UI upgrades were deprecated in 3.8.0 (first announced in 3.7.0) and removed in 3.9.0, together with Watchtower and the Upgrade Now button. Upgrades now go through Docker, Podman or Helm: pullpercona/pmm-server:3and recreate the container. Added a wrong/right row and a gotcha for this./srvownership is uid 1000, gid 0 (chown -R 1000:0), not1000:1000.--publish 443:8443). Fixed the manualdocker run, the "browse to :8443" sentence, thepmm-admin configURL, the firewall row, the ports line and the gotcha./usr/local/percona/pmm/collectors/custom-queries/mysql/{high,medium,low}-resolution/. PMM 2 uses/usr/local/percona/pmm2/collectors/custom-queries/mysql/...; the old text left out thecustom-queries/mysql/segment. Removed the "unconfirmed" note and replaced it with a PMM 3 / PMM 2 path table.pmm2/collectors/custom-queries/postgresqlandtextfile-collectorwith the same layout; the MySQL segment is confirmed by https://github.com/Percona-Lab/pmm-custom-queriessearch_percona_docs(...)snippet are unchanged.Not changed, needs a follow-up
The skill (description, wrong/right table, gotchas) says a PMM 2 client "cannot register" with a PMM 3 server. The migration page says instead that "PMM 3 Server provides limited support for PMM 2 Clients (metrics and Query Analytics only)", and it documents adding a PMM 2 client to a fresh PMM 3 server. This was not one of the listed fixes, so this PR leaves the claim as is.
🤖 Generated with Claude Code