LP #1190636: pt-stalk have the possibility to define data collection interval

Description

**Reported in Launchpad by Kenny Gryp last update 20-06-2013 17:18:17

Looking at the code:

if [ "$CMD_VMSTAT" ]; then
$CMD_VMSTAT 1 $OPT_RUN_TIME >> "$d/$p-vmstat" &
$CMD_VMSTAT $OPT_RUN_TIME 2 >> "$d/$p-vmstat-overall" &
fi
if [ "$CMD_IOSTAT" ]; then
$CMD_IOSTAT -dx 1 $OPT_RUN_TIME >> "$d/$p-iostat" &
$CMD_IOSTAT -dx $OPT_RUN_TIME 2 >> "$d/$p-iostat-overall" &
fi
if [ "$CMD_MPSTAT" ]; then
$CMD_MPSTAT -P ALL 1 $OPT_RUN_TIME >> "$d/$p-mpstat" &
$CMD_MPSTAT -P ALL $OPT_RUN_TIME 1 >> "$d/$p-mpstat-overall" &
fi

You can see that all commands have an interval time of 1 second.
When collecting data for a longer period of time (like for example 1 hour or 1 day), it would be good to be able to define that.

Environment

None

Smart Checklist

Activity

Show:

lpjirasync January 24, 2018 at 7:35 PM

**Comment from Launchpad by: Daniel Nichter on: 20-06-2013 17:18:07

Created https://blueprints.launchpad.net/percona-toolkit/+spec/pt-stalk-ext-cmd-interval since this is not a bug.

Not a Bug

Details

Assignee

Reporter

Priority

Smart Checklist

Created January 24, 2018 at 7:35 PM
Updated February 3, 2018 at 11:52 PM
Resolved January 24, 2018 at 7:35 PM