After update from 1.7.0 to 1.8.0 some db instances couldn’t sent data to qan.
:~# pmm-admin list
pmm-admin 1.8.0
PMM Server | pmm.qa.com
Client Name | master.db.com
Client Address | 172.*.*.*
Service Manager | linux-systemd
-------------- ------------------------------------ ----------- -------- ------------------------------------------ ------------------------------------------
SERVICE TYPE NAME LOCAL PORT RUNNING DATA SOURCE OPTIONS
-------------- ------------------------------------ ----------- -------- ------------------------------------------ ------------------------------------------
mysql:queries master.db.com - YES pmm:***@unix(/var/run/mysqld/mysqld.sock) query_source=slowlog, query_examples=true
linux:metrics master.db.com 42000 YES -
mysql:metrics master.db.com 42002 YES pmm:***@unix(/var/run/mysqld/mysqld.sock)
~# pmm-admin check-network
PMM Network Status
Server Address | pmm.qa.com
Client Address | 172.*.*.*
* System Time
NTP Server (0.pool.ntp.org) | 2018-03-03 13:58:34 +0000 UTC
PMM Server | 2018-03-03 13:58:34 +0000 GMT
PMM Client | 2018-03-03 13:58:34 +0000 UTC
PMM Server Time Drift | OK
PMM Client Time Drift | OK
PMM Client to PMM Server Time Drift | OK
* Connection: Client --> Server
-------------------- -------
SERVER SERVICE STATUS
-------------------- -------
Consul API OK
Prometheus API OK
Query Analytics API OK
Connection duration | 800.78µs
Request duration | 1.69178ms
Full round trip | 2.49256ms
* Connection: Client <-- Server
-------------- ------------------------------------ --------------------- ------- ---------- ---------
SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD
-------------- ------------------------------------ --------------------- ------- ---------- ---------
linux:metrics master.db.com 172.*.*.*:42000 OK YES -
mysql:metrics master.db.com 172.*.*.*:42002 OK YES -
But in grafana I see
Also when I try to remove mysql:queries for add it again I got error:
~# pmm-admin rm mysql:queries
Error removing MySQL queries master.db.com: timeout 10s waiting on agent to connect to API.
[HR][/HR]
Second issue doesn’t connected with 1.8.0.
In fingerprint of query I see wrong schema detection. For example:
db_server 1: has user schema with order table.
db_server 2: has message schema with table mail
in QAN I am checking user server. In fingerprint I see
select from message.order ...
but there are no schema message on user server.
Everything else works ok, Explain, table structure all looks correct.
Hi Stateros , were you able to determine why some hosts stopped sending metrics after upgrade to 1.8.0?
Can you please share the contents from /var/log/pmm-mysql-metrics* for an affected host so we can see why it is failing?
Hi Stateros , sorry for not being clear - the files in /var/log/pmm-* will exist on any node that has pmm-client package installed and if it is running exporters.
I suspect your issue is different than what Stateros is experiencing, and I suggest you open a separate thread for your request.
Can you share in that new thread the actual error message you are receiving? Thanks!
[/QUOTE]
thx 4 ur support， I hv solved my issue，
while i change the template from sqlite3 to mysql，i must add a new datasource named api-qan(mysql) which used to stored the template,i did not do this step before
but i hv met another issue ,i will open a separate thread to discuss it
