PMM 3.6 Remote MySQL service on Windows connects successfully but remains Down (mysql_up = 0

Percona Monitoring and Management (PMM) PMM 3.x
1

Environment

  • PMM Server 3.6
  • Oracle Linux 8
  • Podman
  • MySQL 5.7.13 Enterprise on Windows Server

Problem

I am adding a Windows-hosted MySQL instance using:

Inventory → Add Service → MySQL (Remote)

The service is created successfully.

Observations

  • PMM can connect successfully.
  • ServiceInfo returns MySQL version 5.7.13.
  • performance_schema = ON.
  • Network connectivity is confirmed.
  • MySQL user authenticates successfully.
  • mysql_up remains 0.
  • Service Status remains Down.
  • Built-in dashboards show No Data.

Relevant PMM log

CheckConnection response
ServiceInfo response: version:“5.7.13-enterprise-commercial-advanced-log”

Later I see:

Agent with ID not found.

Question

Is this a known limitation or bug with PMM 3.6 remote monitoring of Windows-hosted MySQL, or is there an additional configuration step required after the service is created?

2

Hi @smitha,
There should not be any issues monitoring remote MySQL, even on Windows. You’ll need to investigate the PMM logs which are inside the docker container in /srv/logs to find out what’s going on.

3

Thank you very much Matt, for pointing that out. I reviewed the pmm-managed logs and noticed ‘remote error: tls: handshake failure’. It appears I had incorrected added the remote host with the option 'Skip TLS certificate and hostname validation’ with the assumption it would simply skip tls validation. I unchecked that and readded it and the service status came up and it is able to query the dashboard as expected.