After updating the Server and Client to 1.0.7 I tried to use the QAN. This doesn’t work before, but I hadn’t the time to get a deeper look whats going wrong.
linux:metrics and mysql:metrics works, check-network shows OK for every Server Service especially for the Query Analytics API. I renamed the client from ‘dblegacy-prod-slave’ to ‘db-legacy-slave’. Now I tried to add mysql:queries with
and in pmm-mysql-queries-0.log it shows:
2016/12/13 15:08:24.397517 main.go:165: Starting agent…
2016/12/13 15:08:24.398197 main.go:346: Agent is ready
2016/12/13 15:08:24.468939 main.go:207: API is ready
2016/12/13 15:08:25.411188 WARNING agent-ws bad status
2016/12/13 15:08:25.411933 WARNING log-ws bad status
2016/12/13 15:08:25.505428 WARNING instance-manager Cannot update mysql dblegacy-prod-slave (65100efb47bd4a0f5451d27eea62a76c): PUT https://pmm..com/qan-api/instances/65100efb47bd4a0f5451d27eea62a76c failed: code 409:
Therefore I rename the client back to “dblegacy-prod-slave” and got:
Error adding MySQL queries: PUT https://pmm..com/qan-api/instances/65100efb47bd4a0f5451d27eea62a76c: API returned HTTP status code 409, expected 204
No Logfile written.
Can I somehow wipe all QAN Data and Nodes on the Server side? I deregister the Node/Services with Consul.