Go to main content

Using Oracle® Solaris 11.4 StatsStore and System Web Interface

Exit Print View

Updated: February 2019
 
 

Displaying Resource and Statistic Slices

Wildcards and slice notation enable you to specify multiple resources or statistics in one SSID.

Displaying Multiple Resources Using Wildcards and Slice Notation

To specify multiple resources with one SSID, use the * wildcard or the s (slice) keyword. Both of the following commands show the same result:

$ sstore list //:class.cpu//:res.id/*
$ sstore list //:class.cpu//:res.id//:s.[*]
IDENTIFIER
//:class.cpu//:res.id/0
//:class.cpu//:res.id/1
//:class.cpu//:res.id/2
//:class.cpu//:res.id/3

The following command selects a subset of resources:

$ sstore list //:class.cpu//:res.id///:s.[1,3]
IDENTIFIER
//:class.cpu//:res.id/1
//:class.cpu//:res.id/3

The slice notation is particularly helpful if the resource namespace is numeric and sequential. The following command selects a range of resources:

$ sstore list //:class.cpu//:res.id///:s.[1:3]
IDENTIFIER
//:class.cpu//:res.id/1
//:class.cpu//:res.id/2
//:class.cpu//:res.id/3

The following commands show resources with non-numeric names. Both of the following commands show the same result:

$ sstore list //:class.io//:res.name/*
$ sstore list //:class.io//:res.name//:s.[*]
IDENTIFIER
//:class.io//:res.name/nfs1
//:class.io//:res.name/nfs2
//:class.io//:res.name/sd0
//:class.io//:res.name/sd2
//:class.io//:res.name/sd3
//:class.io//:res.name/sd4
//:class.io//:res.name/sd5

The following command selects a subset of resources with non-numeric names:

$ sstore list //:class.io//:res.name///:s.[nfs2,sd5]
IDENTIFIER
//:class.io//:res.name/nfs2
//:class.io//:res.name/sd5

A range cannot specify non-numeric resource names:

$ sstore list //:class.io//:res.name///:s.[sd2:sd5]
Warning (//:class.io//:res.name/sd2:sd5) - lookup error: no matches found

Displaying Multiple Statistics Using Wildcards and Slice Notation

Similar to resources, you can specify multiple statistics with one SSID by using the * wildcard or the s (slice) keyword. Statistic slice notation is useful for specifying the arguments for an operation as shown in Performing Operations on Statistic Values.

$ sstore list //:class.io//:res.name/sd0//:stat.*
IDENTIFIER
//:class.io//:res.name/sd0//:stat.nread
//:class.io//:res.name/sd0//:stat.nwritten
//:class.io//:res.name/sd0//:stat.reads
//:class.io//:res.name/sd0//:stat.writes

The following examples specify both resource and statistic slices. All of the following examples show the same result:

$ sstore list //:class.io//:res.name///:s.[sd0,sd3]//:stat.//:s.[nread,reads]
$ sstore list //:class.io//:res.name///:s.[sd0,sd3]//:stat.//:s.[*read*]
$ sstore list //:class.io//:res.name///:s.[sd0,sd3]//:stat.*read*
IDENTIFIER
//:class.io//:res.name/sd0//:stat.nread
//:class.io//:res.name/sd0//:stat.reads
//:class.io//:res.name/sd3//:stat.nread
//:class.io//:res.name/sd3//:stat.reads

Displaying Values of Statistic Slices

The following sstore capture command shows the current value of the nwritten and writes statistics for the sd0 and sd3 resources:

$ sstore capture //:class.io//:res.name///:s.[sd0,sd3]//:stat.*writ* 1 1
TIME                VALUE IDENTIFIER
2016-03-14T15:55:00 22455019008 //:class.io//:res.name/sd0//:stat.nwritten
2016-03-14T15:55:00 7922750 //:class.io//:res.name/sd0//:stat.writes
2016-03-14T15:55:00 0 //:class.io//:res.name/sd3//:stat.nwritten
2016-03-14T15:55:00 12 //:class.io//:res.name/sd3//:stat.writes

After data recording starts (for example, with sstore capture), recording continues for several minutes. Even though the previous capture command only requested one data point, additional values are recorded.

The following sstore export command requests data values at 90-second intervals over a three-minute period, specifying the time output from the previous capture command as the start time for the period:

$ sstore export -t 2016-03-14T15:55:00 -e 2016-03-14T15:58:00 -i 90 \
> //:class.io//:res.name/sd0//:stat.*writ*
TIME                VALUE IDENTIFIER
2016-03-14T15:55:00 22455019008.0 //:class.io//:res.name/sd0//:stat.nwritten
2016-03-14T15:56:30 22579517952.0 //:class.io//:res.name/sd0//:stat.nwritten
2016-03-14T15:58:00 22699119616.0 //:class.io//:res.name/sd0//:stat.nwritten
2016-03-14T15:55:00 7922750.0 //:class.io//:res.name/sd0//:stat.writes
2016-03-14T15:56:30 7965336.0 //:class.io//:res.name/sd0//:stat.writes
2016-03-14T15:58:00 8008724.0 //:class.io//:res.name/sd0//:stat.writes

If you use the -p option to specify a number of data points, you get the specified number of consecutive data points that were recorded, even if you specified and interval (-i) or an end time (-e). For example, if you added -p 2 to the previous command, you would get values at 15:55:00 and 15:55:01.

If you use the -p option with a negative argument, you get the specified number of consecutive data points that were recorded prior to.

For data of type counter (the most common type), if values are recorded for several minutes, then recording is stopped, and then recording is started again, sstore export shows interpolated values for the period when no data was recorded.