Note PMM QAN data sources and prepared-statement visibility#357
Merged
patrickbirch merged 1 commit intoJul 8, 2026
Merged
Conversation
Add a note in the PMM section clarifying that QAN reads only a file-based slow query log or Performance Schema, and that server-side prepared statements show placeholders and no EXPLAIN under Performance Schema (upstream MySQL behavior). Signed-off-by: Michael Coburn <michael.coburn@percona.com>
patrickbirch
approved these changes
Jul 8, 2026
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.
What
Adds a short, expectation-setting note so readers recognize why PMM Query Analytics (QAN) may show incomplete data for MySQL prepared-statement workloads.
Why
Server-side prepared statements (used by most application drivers, e.g. JDBC) are exposed by upstream MySQL to Performance Schema with placeholder parameters (
?) rather than literal values. As a result, QAN query examples appear as placeholders and EXPLAIN is unavailable for them. This is upstream MySQL behavior, not a PMM limitation. The note helps users self-diagnose instead of assuming data is missing.Placed in the PMM section of the cluster monitoring page.
Scope
Documentation only — a single admonition in
docs/monitoring.md. Part of a coordinated set of PRs across pmm-doc, psmysql-docs, pxc-docs, k8sps-docs, and k8spxc-docs.DCO: signed off.