Should the documentation be different, or version 2 has completely different commands set?
I am running latest pmm Agent on Centos and Ubuntu servers. On both, output for pmm-admin check-network
and pmm-admin
is the same:
[root@server-3 centos]# pmm-admin check-network
pmm-admin: error: expected command but got "check-network", try --help
[root@server-3 centos]# pmm-admin
usage: pmm-admin [] [ ...]
Version 2.4.0
Flags:
-h, --help Show context-sensitive help (also try --help-long and --help-man)
--version Show application version
--server-url=SERVER-URL PMM Server URL in `https://username:password@pmm-server-host/` format
--server-insecure-tls Skip PMM Server TLS certificate validation
--debug Enable debug logging
--trace Enable trace logging (implies debug)
--json Enable JSON output
Commands:
help [...]
Show help
config [] [] [] []
Configure local pmm-agent
list []
Show Services and Agents running on this Node
status
Show information about local pmm-agent
summary []
Fetch system data for diagnostics
add mongodb [] [] []
Add MongoDB to monitoring
add mysql [] [] []
Add MySQL to monitoring
add postgresql [] [] []
Add PostgreSQL to monitoring
add proxysql [] [] []
Add ProxySQL to monitoring
register [] [] [] []
Register current Node at PMM Server
remove [] []
Remove Service from monitoring
Am I doing something worng?
pmm-admin check-network is documented in Documentation for 2.4 Section 3.4
To make sure that the new server is available run the pmm-admin check-network command from the computer
where PMM Client is installed. Run this command as root or by using the sudo command
Hi @“Arnis Juraga”,
pmm-admin check-network
is not a valid v2 command. Can you send the link to the documentation you mention?
The official one! Open documentation, search for “check-network”. You will find. To be honest, I tried pmm2.4 and had multiple problems, starting from installation documentation issues.
Anyway - the problem for me was, that machine was registering successfully on my DOCKER installation, clients registered visible in Dashboard, but later not receiving any data. So I followed debugging (troubleshooting) and that documentation is very outdated then for 2.4…
All are official links:
https://www.percona.com/doc/percona-monitoring-and-management/index.html
Select “PMM 2” on the left side dropdown.
https://learn.percona.com/hubfs/Manuals/Percona_Monitoring_And_Management_PMM/PMM-2.1/PerconaMonitoringAndManagement%202.4.0.pdf
pmm-admin status
pmm-admin list
do similar things. but, yeah, i miss the nice colored output of check-network
@“Arnis Juraga”,
Thanks for the details, I’ll check the link you sent with the team, and create a new bug report for it, if needed.
For any other incorrect (or incomplete) documentation sections, feel free to open a documentation bug in https://jira.percona.com/projects/PMM/issues.
Regarding the lack of metrics, did you also check the client-side logs?
journalctl -u pmm-admin
The official one! Open documentation, search for “check-network”. You will find. To be honest, I tried pmm2.4 and had multiple problems, starting from installation documentation issues.
Anyway - the problem for me was, that machine was registering successfully on my DOCKER installation, clients registered visible in Dashboard, but later not receiving any data, nor Linux nor MySQL. So I followed debugging (troubleshooting) and that documentation is very outdated then for 2.4…
All are official links:
https://www.percona.com/doc/percona-monitoring-and-management/index.html
Select “PMM 2” on the left side dropdown.
https://learn.percona.com/hubfs/Manuals/Percona_Monitoring_And_Management_PMM/PMM-2.1/PerconaMonitoringAndManagement%202.4.0.pdf