For the record, the tool is supposed to ignore --sleep and --interval because --no-stalk means "collect once and exit". The bug was, as Baron pointed out, that --interval was being used instead of --run-time. So the collection sub-process was running for --run-time, but vmstat, iostate, and mpstat were not.
For the record, the tool is supposed to ignore --sleep and --interval because --no-stalk means "collect once and exit". The bug was, as Baron pointed out, that --interval was being used instead of --run-time. So the collection sub-process was running for --run-time, but vmstat, iostate, and mpstat were not.