Percona PMM inventory points to two access layers
Percona Monitoring and Management combines dashboards, metric storage, query analytics, inventory, and agent management in one server. A public login page is therefore not the only security question. The PMM access model has browser users and service accounts, and each path reaches different controls.
A count-only ZoomEye run on 2026-11-21 measured app="Percona Monitoring and Management" at 1,411 index matches. The exact title query returned 1,412. A shorter app="PMM" query returned five, while title="Percona PMM" returned zero. All queries used sub_type=all, page 1, and page size 1. The longer product name is the useful inventory lead here. The short abbreviation is ambiguous and does not replace the product-level query. The counts are index matches, not confirmed exposed or vulnerable servers.
PMM documentation describes two access-control dimensions. Standard roles inherited from Grafana provide feature-level permissions: Viewer, Editor, and Admin. Label-based access control can restrict metrics and Query Analytics data by labels such as environment or service name. If an administrator has not configured a custom default role, the documentation says a first-time user receives Viewer and full access to all metrics. That default deserves review when teams expect new users to see only their own environment.
API access is a separate path. PMM 3 uses service accounts and service tokens instead of the older API-key model. The documentation says API access requires authentication with service-account tokens and that service accounts can have granular permissions and multiple tokens. A PMM agent registration token may therefore carry inventory or registration authority that should not be given to a generic dashboard user.
A review should inventory three things together: the human role, the label selector, and the service-account scope. Test a Viewer who should see only production or test metrics. Test an agent token that should register one class of service and should not modify arbitrary inventory. Confirm that a token cannot act as a dashboard administrator.
The security page adds two deployment checks. PMM ships with a self-signed certificate for initial encrypted connectivity, but the documentation says that is not a properly secured connection. Replace it with a trusted certificate and secure cookies. Also review the initial admin account. The login documentation lists a default admin password and a first-login prompt that can be skipped. A production server should not keep that credential or skip the change.
The external count can help an owner find candidate PMM servers. Reconcile it with DNS, certificates, and monitoring inventory. Do not attempt to log in, enumerate inventory, or register an agent. For an owned host, verify the certificate, default account state, access-control setting, label roles, service accounts, and repository boundaries.
PMM gives a team a useful view of database health. The security review has to cover who sees the telemetry and which automation can change the monitored inventory.
Exact query: app="Percona Monitoring and Management"
Open the normalized ZoomEye search
Top comments (0)