pt-stalk not honoring all configs listed with --config

[bar down]

Are we sure this pt-stalk --config command actually parses correctly still?

Aside from the above mention of --config= not working, it seems things are still not parsed correctly (or honored) when used without the = sign.

For instance when using multiple configs, it seems that the LAST config is the only one honored:

pt-stalk --config ./deadlocks.conf,./longquery.conf,./highcnx.conf --dest=/var/lib/mysql/pt-stalk --log=/var/log/mysql/pt-stalk/pt-stalk.log --sleep=30 --defaults-file=/etc/percona-toolkit.conf

output:
2016_04_25_15_51_59 Starting /usr/bin/pt-stalk --function=status --variable=Threads_running --threshold=100 --match= --cycles=5 --interval=1 --iterations= --run-time=30 --sleep=30 --dest=/var/lib/mysql/pt-stalk --prefix= --notify-by-email= --log=/var/log/mysql/pt-stalk/pt-stalk.log --pid=/var/run/pt-stalk.pid --plugin=

In this example, my longquery.conf is not triggering, but if I put it as the last argument in the list of configs, it does:
[root@testl1 configs]# pt-stalk --config ./deadlocks.conf,./highcnx.conf,./longquery.conf --dest=/var/lib/mysql/pt-stalk --log=/var/log/mysql/pt-stalk/pt-stalk.log --sleep=30 --defaults-file=/etc/percona-toolkit.conf
2016_04_25_15_52_46 Starting /usr/bin/pt-stalk --function=/usr/local/bin/mysql/pt-stalk/functions/longquery.sh --variable=Long_Query --threshold=0 --match= --cycles=5 --interval=1 --iterations= --run-time=30 --sleep=30 --dest=/var/lib/mysql/pt-stalk --prefix= --notify-by-email= --log=/var/log/mysql/pt-stalk/pt-stalk.log --pid=/var/run/pt-stalk.pid --plugin=
2016_04_25_15_53_52 Check results: /usr/local/bin/mysql/pt-stalk/functions/longquery.sh(Long_Query)=1, matched=yes, cycles_true=1
2016_04_25_15_53_53 Check results: /usr/local/bin/mysql/pt-stalk/functions/longquery.sh(Long_Query)=1, matched=yes, cycles_true=2
2016_04_25_15_53_54 Check results: /usr/local/bin/mysql/pt-stalk/functions/longquery.sh(Long_Query)=1, matched=yes, cycles_true=3
2016_04_25_15_53_55 Check results: /usr/local/bin/mysql/pt-stalk/functions/longquery.sh(Long_Query)=1, matched=yes, cycles_true=4
2016_04_25_15_53_56 Check results: /usr/local/bin/mysql/pt-stalk/functions/longquery.sh(Long_Query)=1, matched=yes, cycles_true=5
2016_04_25_15_53_56 Collect 1 triggered
2016_04_25_15_53_56 Collect 1 PID 50385
2016_04_25_15_53_56 Collect 1 done
2016_04_25_15_53_56 Sleeping 30 seconds after collect
;;

Version:
pt-stalk 3.0.4

[bar down (bardown)]

Same results with version pt-stalk 2.2.17

[Sveta Smirnova (svetasmirnova)]

Thank you for the report.

I cannot repeat this behavior with current version 2.2.19 Please try this version and if bug still exists provide configuration files you use.

[Launchpad Janitor (janitor)]

[Expired for Percona Toolkit because there has been no activity for 60 days.]

[bar down (bardown)]

Sveta, can you paste me the CLI you are using? I'd be more curious to see a working example?

[bar down (bardown)]

I should mention that I've now tested this on the latest version of pt-stalk with the same exact behavior. Version: pt-stalk 3.0.4

No changes in behavior. If anyone uses the --config command correctly or has some way of monitoring multiple triggers at the same time I would love to see an example or sample output!

[bar down (bardown)]

Marking new as I've updated the version to the latest, still without luck.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1342