Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-1906

Duplicated parameters shown in `ps aux` command

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Medium
    • Resolution: Reopened
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: PMM Client
    • Labels:

      Description

      Currently, the only way to check for parameters sent to the exporters is by using ps aux | grep

      If we choose to disable collection for default parameters, both the `true` and `false` flags are shown, making it difficult to check which one is used.

      I noticed that the default parameters show only one dash, and custom parameters show two dashes, so it's possible to know which ones are being used, but it's cumbersome and error-prone.

       

      An example follows. I disabled P_S collection on a mysql exporter, and the following is shown

      shell> ps aux | grep exporter | grep 42002 | head -n1
      root 3795 0.0 0.0 115212 1464 ? Ss 09:31 0:00 /bin/sh -c /usr/local/percona/pmm-client/mysqld_exporter -collect.auto_increment.columns=true -collect.binlog_size=true -collect.global_status=true -collect.global_variables=true -collect.info_schema.innodb_metrics=true -collect.info_schema.processlist=true -collect.info_schema.query_response_time=true -collect.info_schema.tables=true -collect.info_schema.tablestats=true -collect.info_schema.userstats=true -collect.perf_schema.eventswaits=true -collect.perf_schema.file_events=true -collect.perf_schema.indexiowaits=true -collect.perf_schema.tableiowaits=true -collect.perf_schema.tablelocks=true -collect.slave_status=true -web.listen-address=192.168.87.3:42002 -web.auth-file=/usr/local/percona/pmm-client/pmm.yml -web.ssl-cert-file=/usr/local/percona/pmm-client/server.crt -web.ssl-key-file=/usr/local/percona/pmm-client/server.key --collect.perf_schema.eventswaits=false --collect.perf_schema.file_events=false --collect.perf_schema.indexiowaits=false --collect.perf_schema.tableiowaits=false --collect.perf_schema.tablelocks=false >> /var/log/pmm-mysql-metrics-42002.log 2>&1
      

      In particular:

      -collect.perf_schema.eventswaits=true

      and

      --collect.perf_schema.eventswaits=false

      The same for all other `collect.perf_schema` flags.

       

      It would be nice if this wasn't the case, so we can use a command such as the following, to check for flags used (since we currently don't have another way of doing it):

      shell> ps aux | grep exporter | grep 42002 | head -n1 | tr '-' '\n' | grep collect | sort
      collect.auto_increment.columns=true 
      collect.binlog_size=true 
      collect.global_status=true 
      collect.global_variables=true 
      collect.info_schema.innodb_metrics=true 
      collect.info_schema.processlist=true 
      collect.info_schema.query_response_time=true 
      collect.info_schema.tablestats=true 
      collect.info_schema.tables=true 
      collect.info_schema.userstats=true 
      collect.perf_schema.eventswaits=false 
      collect.perf_schema.eventswaits=true 
      collect.perf_schema.file_events=false 
      collect.perf_schema.file_events=true 
      collect.perf_schema.indexiowaits=false 
      collect.perf_schema.indexiowaits=true 
      collect.perf_schema.tableiowaits=false 
      collect.perf_schema.tableiowaits=true 
      collect.perf_schema.tablelocks=false >> /var/log/pmm
      collect.perf_schema.tablelocks=true 
      collect.slave_status=true

       

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  agustin.gallego Agustín Gallego
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: