You will want to use the "-o" option on the "dfm perf data retrieve" command to specify a specific object whose counters you wish to query.
C:\>dfm perf data retrieve help
NAME
retrieve -- This command allows you to extract the counter data
with supported statistical calculations on them.
SYNOPSIS
dfm perf data retrieve { [ -o object-name-or-id ... ] [ -C perf-counter ... ]
[ -V view-name ] }
[ -d duration ] [ -b start-time ] [ -e end-time ]
[ -M month ... ] [ -D weekday ... ] [ -T time-range ... ]
[ -m statistical-method [ -P percentile-value ]
[ -S data-advance-method ] ]
[ -s sample-rate ] [ -x output-format ] [ -R ]
Description of options:
-o Object instance for which data is to be retrieved. Multiple object
instances can be specified. Specifying a parent will retrieve data
for all its children.
-C A counter of the form object-name:counter-name (ex. system:cpu_busy).
Multiple counters can be specified.
So in your case, the CLI would be something like "dfm perf data retrieve -o yourvolumename -C volume:cifs_read_latency". Note that you don't put the volume name in the counter parameter. You can put multiple "-C" parameters on a single command line if you need multiple counters for the same object, for instance:
dfm perf data retrieve -o yourvolumename -C volume:cifs_read_latency -C volume:cifs_write_latency -C volume:cifs_other_latency
If you use multiple counters within a single retrieve another option to consider is "-x TimeIndexed" which organizes the output in a tabular format by sample time. If you specify counters that are updated on un-correlated schedules or if you specify multiple objects that might have uncorrelated collection schedules you may run into some odd results on a TimeIndex report, since DFM tries to make sense of all the data in a single aggregation.
Hope this helps you.
Bob Greenwlad
Lead Storage Engineer, Huron Legal
Huron Consulting Group
NCDA | NCIE-SAN Clustered Data OnTap
