| COLLECTL(1) | Collectl | COLLECTL(1) |
NAME¶
collectl - Collects data that describes the current system status.SYNOPSIS¶
Record Mode - read data from live system and write to file or display on terminalOPTIONS¶
Record ModeIf the HiRes modules is present,
collectl sample monitoring will be aligned such that a sample will
always be taken at the top of a minute (this does NOT mean the first sample
will occur then) so that all instances of collectl running on any systems
which have their clocks synchronized will all take samples at the same time.
Furthermore, if one is doing process monitoring, those samples will also be
taken at the top of the minute and so can delay the start of sampling up to 2
full process monitoring intervals.
Collect summary data for ALL subsystems except
slabs, since slab monitoring requires a different monitoring interval. This
also means you won't get any detail data which also includes processes and
environmementals. You can use this switch anywhere -s can be used but not both
together. If the system supports lustre and/or interconnect monitoring those
statistics will be provided but the warnings produced when they are not
available you try to select them with -s will not be displayed.
In the first form, one specifies an address,
optional port and timeout (the first colon is required to specify timeout for
default port). All data is then written to that socket prefaced with the
current host name at the named address and port until the socket is closed, at
which time collectl will exit.
In the second form one enters the text "server" and optional port. In
this form, collectl runs as a server, waiting for a connection and once
established writes data on that socket. The key difference here is if the
client exists collectl keeps running and will again look for a new connection,
allowing it to survive client restarts or crashes.
The default port is set at 2655 but can be changed - see collectl.conf.
In both forms, one can additionally request local data logging by specifying a
combination of -P and -f. See man collectl-logging for more
details.
Add the specified string to the end of the
headers in the data files. If any embedded spaces be sure to quote it. This
can be very useful when doing characterizations or benchmarking and you're
frequently changing system/application parameters and restarting collectl
between tests.
Name/location of the collectl configuration
file. If not specified, collectl searches for collectl.conf
first in /etc (the default), then in the same directory the collectl
executable is in, and finally the current working directory.
The number of samples to record. This is one
way of 3 ways of describing how long collectl should run (see -r and
-R ). Note that these 3 switches are mutually exclusive.
Run collectl as a daemon, primarily
used when starting as a service. One caveat about this mode is you can only
run one copy.
This requests that collectl does not print
anything on the terminal (or send it to a socket) using the standard
brief/verbose/plot formats. Instead it executes a perl "require" on
the named file, using an extension of ph if not specified. It first looks in
the current directory and if not there the directory the executable is in. It
then calls the function "file"Init(options) towards the beginning of
collectl and again as simply "file"(@options) to generate the
exported formatted output. See the document sections on Exporting Custom
Output and Logging for more details.
This is the name of a file to write the output
to. See the description of File Naming for further
details.
Flush output buffers after this number of
seconds. This is equivalent to issuing kill -s USR1 at the same
frequency (but a lot easier!). If 0, a flush will occur every data collection
interval.
The main purpose of this switch is for those
users who have discovered there is some data in the raw files that never
appears in any display and have taken to displaying it themselves with grep.
Unfortunately this method does not include timestamps and so makes it
difficult to interpret the results. Even if you include the timestamp from the
file it is in UTC and so needs to be translated to be of any real value. This
switch does just that and then some.
Specifically, it allows you to playback a file and instead of processing it
normally it simply searches for any entries that match the perl pattern and
reports those lines prefaced with time stamps. You can optionally change the
time format with the usual -o options and can even select the timeframe with
--from and --thru.
Always start the display for the current
interval at the top of the screen also known as the home position (non-plot
format only). This generates a real-time, continously refreshing display when
the data fits on a single screen.
This loads the named files and executes
callbacks to them, which is the API mechanism for importing additional metrics
into collectl. See the webpage on the API for further detail.
Since these files also include instructions for how to report the output in all
the various forms, you will also need to include --import during playback.
Finally, since the default is to seamlessly include imported data with
everything else collectl reports, if you ONLY want to display imported data
you much explicitly deselect all other subsystems either by including -s-
(note the trailing minus sign) followed by all the subsystems were recorded OR
simply say -s-all.
This is the sampling interval in seconds. The
default is 10 seconds when run as a daemon and 1 second otherwise. The process
subsystem and slabs (-sY and -sZ) are sampled at the lower rate of
interval2. Environmentals (-sE), which only apply to a subset of
hardware, are sampled at interval3. Both interval2 and
interval3, if specified, must be an even multiple of interval1.
The daemon default is -i10:60:300 and all other modes are -i1:60:300. To
sample only processes once every 10 seconds use -i:10.
Whenever collectl finishes a data collection
interval, it checks to see if the starting parent has exited. This is to
prevent the case in which someone might start a copy of collectl and then the
process dies and collectl keeps running. If that is the behavior someone
actually intends, they should start collectl with --nohup.
NOTE - when running as a daemon, --nohup is implied.
Whenever collectl wants to tell the user
something, it assigns a category to it such as Informational, Warning, Error
or Fatal. When run with -m, all messages are displayed for the user and if
logging data to a file with -f, these messages are also sent to a log file
which is in the data collection directory and has an extenion of
"log". However, if -m is not specified Informational messages (such
as collectl starting or stopping) are not reported on the terminal but the
other 3 are. Sometimes the warnings can be annoying and one can suppress these
with --quiet though they will still be written to the message log in -f. You
cannot suppress Error or Fatal errors.
When selected, collectl runs
indefinately (or at least until the system reboots). The maximum number of raw
and/or plot files that will be retained (older ones are automatically deleted)
is controlled by the days field, the default is 7 days. The
increment field which is also optional (but is position dependent)
specifies the duration of an individual collection file in minutes the default
of which is 1440 or 1 day.
This switch overrides the DiskFilter setting
in collectl.conf and explicitly defines a perl regx expression against which
records from /prod/diskstats are selected for processing. When there are a lot
of disks to process, this can be a handy way to reduce the amount of data
collected and actually improve performance since there are less patterns to
match each input record against. Just remember that unlike --dskfilt which
only filters during display, records filtered with this switch are never even
recorded and so lost forever.
As a side benefit of this switch, if you really want to look at partition level
stats you can do so by leaving off the trailing space in the default pattern.
One must be also be careful in selecting the correct pattern since it's easy to
get it wrong and you may end up collecting the WRONG data! To verify you are
collecting what you think you are, make a test run using -d4 to see the raw
data being recorded in real-time.
This works just like --rawdskfilt except it
applies to networks. Unlike disk filtering which has an explicit default
pattern, the default for network filtering is to simply record all network
data from /proc/net/dev.
The -d4 switch also works here, as well as everywhere, to see the raw data as it
is being collected.
Only available in conjunction with -P, this
switch causes the creation/logging of raw data in addition to plottable data.
While this may seem excessive, keep in mind that unlike plottable data, raw
data can be played back with different switches potentially providing more
details. The overhead to write out this additional data is minimal, the only
real cost being that of extra disk space.
This switch only works when running in daemon
mode and so must be specified in the DaemonCommands line. Its presence will
cause collectl to write the collectl.pid file into the same directory as its
other output files as specified by -f, since /var/run does not normally grant
non-privileged users write access. Furthermore, the ownership of that
directory must match the specified ownership since collectl needs to write ALL
it's files to that directory and can no longer assume global permissions when
run as root.
This WILL also require manually modifying /etc/init.d/collectl to change the
PIDFILE variable to point to the same directory which the -f switch in the
DaemonCommands line of collectl.conf points to.
As a final note of caution, since this mechanism changes where collectl
reads/writes its pid file, once you start using --runas, all calls to run
collectl as a daemon must use it or it may be confused and exhibit
unpredictable behavior.
Specify the duration of data collection where
the duration is a number followed by one of wdhms, indicating how many
weeks, days, hours, minutes or seconds the collection is to be taken
for.
Specify the plot format separator - default is
a space. If this is a numeric field it is interpretted as the decimal value of
the associated ASCII character code. Otherwise it is interpretted as the
character itself. In other words, "--sep :" sets the separator
character to a colon and "--sep 9" sets it to a horizontal tab.
"--sep 58" would also set it to a colon.
The switches -G and --group have been replaced
by --rawtoo, which is more rescriptive of its function. When specified, it
tells collectl to treat process and slab data as an entirely separate group of
raw files, named with the extention "rawp". These separate files can
be played back and processed just like any other collectl raw files and in
fact one can even play back both at the same time if that is what is desired.
The only real purpose of this switch is that on some systems with many
processes, it is possible to generate huge raw files (some have been observerd
to be >250MB!) and while collectl will happily play back/process these
files it can take a long time. By using the --tworaw switch one still gets a
huge rawp file, but the normal raw file is a much more manageable size and as
a result will faster to process then when all data is combined into the same
file.
When playing back a file, use this switch to
create an identical raw file differing only in the timeframe being convered,
so naturally one must also include --from, --thru or both. Further, since the
resultant file will contain the exact same raw data you cannot select a subset
using -s. This switch is actually intended for a support function for
situations where somone is having problems playing back a file and a subset of
the original raw file that covers the problem time has been requested,
hopefully allowing a significantly file to be posted or emailed.
If specified, rather than actually play back
the file specified with -p, ALL raw data between the date ranges is selected
and a subset of that raw file created. The rules for how to interpret the
filename are the same as used for -f.
If specified, this is the name of a file or
directory to write the output to (rather than the terminal). See the
description for details on the format of this field. This requires the -P flag
as well.
Play back data starting with this time, which
may optionally include the ending time as well, which is of the format of
[date:]time[-[date:]time]. The leading 0 of the hour is optional and if the
seconds field is not specified is assumed to be 0. If no dates specified the
time(s) apply to each file specified by -P. Otherwise the time(s) only apply
to the first/last dates and any files between those dates will have all their
data reported.
When reporting usernames associated with a
UID, use this file for the mapping. This is particularly important on systems
running NIS where this are no user names in /etc/passwd.
By default, collectl uses the file
/var/run/collectl.pid to indicate the pid of the running instance of collectl
and prevent multiple copies from being run. If you DO want to run a second
copy, this switch will cause collectl to change its process name to
collectl-name and use that name as the associated pid file as well.
This field originally was used before collectl
reported the timezone in the file headers and allowed one to compensate. Since
then it is rarely needed except in two possible cases, one in which data on
two systems is to be compared and they weren't synchonized with ntp. This
allows all the times to be reported as shifted by some number of seconds. The
other case (and this is very rare) is when a clock had changed in the middle
of a sample and will not be converted correctly. When this happens one may
have to play back the samples in pieces and manually set the time
offset.
Read data from the specified playback
file(s), noting that one can use wildcards in the filename if quoted (if
playing back multiple files to the terminal you probably want to include -m to
see the filenames as they are processed). The filename must either end in
raw or raw.gz. As an added feature, since people sometimes
automate the running of this option and don't want to hard code a date, you
can specify the string YESTERDAY or TODAY and they will be replaced in the
filename string by the appropriate date.
When specified and there is process data in
the raw file, a summary file will be generated with one entry unique process
containing such things as the total cpu consumed for both user and system,
min/max utilization of various memory types, total page faults and several
others.
When specified and there is slab data in the
raw file, a summary file will be generated with one entry unique slab
containing data on physical memory usage by that slab.
Time thru which to play back a raw file. See
--from for more
Control the level of debugging information,
not typically used. For details see the source code.
Display standard, extended help message (which
doesn't include the optional displays such as --showoptions, --showsubsys,
--showsubopts, --showtopopts) or everything.
Sets the number of intervals to display data
for before repeating the header. A value -1 will prevent any headers from
being displayed and a value of 0 will cause only a single header to be
displayed and never repeated.
In brief mode, include iosize with disk,
infiniband and network data.
Override one or more default exception limits.
If more than one limit they must be separated by hyphens. Current values are:
SVC:value
IOS:value
LusKBS:value
LusReints:value
AND
OR
-L, --lustsvcs [c|m|o][:seconds]
-m, --messages
Report partition activity with Service times
>= 30 msec
Report device activity with 10 or more reads
or writes per second
Report client or OSS activity greater than
limit. Only applies to Client Summary or OSS Detail reporting.
[default=100000]
Report MDS activity with Reint greater than
limit. Only applies to MDS Summary reporting. [default=1000]
Both the IOS and SCV limits must be reached
before a device is reported. This is the default value and is only included
for completeness.
Report device activity if either IOS or SVC
thresholds are reached.
This switch limits which servics lustre checks
for and the frequency of those checks. For more information see the man page
collectl-lustre.
Write status to a monthly log file in the same
directory as the output file (requires -f to be specified as well). The name
of the file will be collectl-yyyymm.log and will track various messages
that may get generated during every run of collectl.
Set priority to a nicer one of 10.
-o, --options Options
These apply to the way output is displayed OR
written to a plot file. They do not effect the way data is selected for
recording. Most of these switches work in both record as well as playback
mode. If you're not sure, just try it.
1
2
a
c
d
D
g
G
m
n
T
u
-U or --utc
x
X
z
Data in plotting format should use 1 decimal
point of precision as appropriate.
Data in plotting format should use 2 decimal
points of precision as appropriate.
Always append data to an existing plot file.
By default if a plot file exists, the playback file will be skipped as a way
of assuring it is associated with a single recorded file. This switch
overrides that mechanism allowing muliple recorded files to be processed and
written to a single plot file.
Always open newly named plot fies in
create mode, overwriting any old ones that may already exists. If one
processes multiple files for the same day in append mode multiple
times, the same data will be appended to the same file mulitple times. This
assures a new file is created at the start of the processing.
For use with terminal output and brief mode.
Preceed each line with a date/time stamp, the date being in mm/dd format. This
option can also be applied to plot formatit which will cause the date portion
to also be displayed in this format as opposed to D format.
For use with terminal output and brief mode.
Preceed each line with a date/time stamp, the date being in yyyymmdd
format.
For use with terminal output and brief mode.
When displaying values of 1G or greater there is limited precision for 1 digit
values. This options provides a way to display additional digits for more
granularity by substituting a "g" for the decimal point rather than
the trailing "G".
For use with terminal output and brief mode.
This is similar to "g" but preserves the trailing "G" by
sacrificing a digit of granularity.
Whenever times are reported in plot format, in
the normal terminal reporting format at the bginning of each interval or when
when one of the time reporting options (d, D, T or U is selected), append the
milliseconds to the time.
Where appropriate, data such as disk KBs or
transfers are normalized to units per second by taking the change in a counter
and dividing by the number of seconds in that interval. In the case of CPUs,
utilization (calculated in jiffies) is normalized as a percentage of the
interval.
Normalization can be disabled via this option, the result being the reported
values are not divided by the duration of the interval. This can be
particulary useful for reporting values that are < 1/2 the sampling, which
will be rounded to 0.
For use with terminal output and brief mode,
preceeds each line with a time stamp.
Create plot files with unique names by include
the starting time of a colletion in the name. This forces multiple collections
taken the same day to be written to multiple files.
In plot format only, report timestamps in
Coordinated Universal time which is more commonly know as UTC.
Report only exception records for selected
subsystems. Exception reporting also requires --verbose. Currently this only
applies to disk detail and Lustre server information so one must select at
least -s D, l or L for this to apply. If writing to a detail file, this data
will go into a separate file with the extension X appended to the
regular detail file name.
Report both exceptions as well as all details
for selected subsystems, for -s D, l or L only.
If the compression library has been installed,
all output files will be compressed by default. This switch tells collectl not
to compress any plottable files. If collectl tries to compress but cannot
because the library hasn't been installed, it will generate a warning which
can be suppressed with this switch.
Generate output in plot format. This format is
space separated data which consists of a header (prefaced with a # for easy
identification by an analysis program as well as identifying it as a comment
for programs, such as gnuplot, which honor that convention). When written to
disk, which is the typical way this option is used, summary data
elements are written to the tab file and the detail elements
written to one or more files, one per detail subsystem. If -f is not
specified, all output is sent to the terminal. Output is always one line per
sampling interval.
This switch will cause brief data to be
reported as both totals and averages after processing one or more files for
the same day or in playback mode.
This switch controls the way brief stats are
reported, the default is to report the totals once, at the end of a day's
worth of raw files, if more than one.
a - include averages along with totals
i - include the interval data itself, which is the equivalent of -oA
s - print summary stats at the end of each file processed even if more than one
per day
This field controls which subsystem data is to
be collected or played back for. The rules for displaying results vary
depending on the type of data to be displayed. If you write data for CPUs and
DISKs to a raw file and play it back with -sc, you will only see CPU data. If
you play it back with -scm you will still only see CPU data since memory data
was not collected. However, when used with -P, collectl will always honor the
subsystems specified with this switch so in the previous example you will see
CPU data plus memory data of all 0s. To see the current set of default
subsystems, which are a subset of this full list, use -h.
You can also use + or - to add or subtract subsystems to/from the default
values. For example, "-s-cdn+N"< will remove cpu, disk and
network monitoring from the defaults while adding network detail.
The default is "cdn", which stands for CPU, Disk and Network summary
data.
Refer to data definitions on the sourceforge website OR in
/usr/share/collectl/doc/collectl-xxx to see complete descriptions of the data
returned.
SUMMARY SUBSYSTEMS
b - buddy info (memory fragmentation)
c - CPU
d - Disk
f - NFS V3 Data
i - Inode and File System
j - Interrupts
l - Lustre
m - Memory
n - Networks
s - Sockets
t - TCP
x - Interconnect
y - Slabs (system object caches)
DETAIL SUBSYSTEMS
This is the set of detail data from which in most cases the corresponding
summary data is derived. There are currently 2 types that do not have
corresponding summary data and those are "Environmental" and
"Process". So, if one has 3 disks and chooses -sd, one will
only see a single total taken across all 3 disks. If one chooses -sD,
individual disk totals will be reported but no totals. Choosing -sdD
will get you both.
C - CPU
D - Disk
E - Environmental data (fan, power, temp), via ipmitool
F - NFS Data
J - Interrupts
L - Lustre OST detail OR client Filesystem detail
M - Memory node data, which is also known as numa data
N - Networks
T - 65 TCP counters only available in plot format
X - Interconnect
Y - Slabs (system object caches)
Z - Processes
In collectl mode this command will cause the
header that is normally written to a data file to be displayed on the terminal
and collectl then exists. This can be a handy way to get a brief overview of
the system configuration.
This command shows only the portion of the
help text that desribes the -o and --options switches to save the time of
wading through the entire help screen.
This command shows the first set of headers
that will be printed by collectl and exits. Doesn't really make sense for
multi-section output like several sets of verbose or detail data. Also note
that since it requires one monitoring interval to build up some headers which
may be dynamic, it also forces the interval to 0.
List all the subsystem specifice options
Show all the different values for the --top
type field, which specify the field(s) by to sort the data
This command only works on systems using the
new slab allocator and will list the root name (these are those entries in
/sys/slab which are not soft links) along with all its alias names. If a name
doesn't have an alias, it will not appear in this report.
This command only works on systems using the
new slab allocator. Like --showrootslabs, it will name a slab and all its
aliases but rather than show the root slab name it will show one of the
aliases to provide a more meaningful name. If there are any slabs that only
have a single (or no) alias they will not be included in this report.
Similar to --showoptions, this command
summaries just the paramaters associated with -O and --subopts.
Yet another way to summare a portion of the
help text, this command only shows valid subsystems.
Include the top "num" consumers by
resource for this interval. The default number is the height of the window if
it can be determined otherwise 24, and the default resource is the total cpu
time which is taken as the sum of SysT and UsrT. See --showtopopts for a list
of other types of data you can sort on.
This switch can also be used with -s in which case a portion of the window is
reserved at the top to fill in the subsystem data, which is currently in
verbose mode though a brief format is contemplated for some time in the
future.
In interactive mode and if not specified, the process monitoring interval will
be set to that for other subsystems. The screen will be cleared for each
interval resulting in a display similar to the "top" utility. In
playback more the screen will NOT be cleared. You cannot use this switch in
"record" mode.
Sets collectl's umask to control output file
permissions. Only root can set the umask. See "man umask" for
details.
Write periodic micro-timestamps into raw file
at different points in time for fine grained measurements of operation times.
1 - write timestamps when entering major sections
2 - write timestamps for all /proc accesses except for process data
4 - write timestamps for /proc data for all processes including threads
Show version and whether or not Compression
and/or HiResTime modules have been installed and exit.
Show default parmeter and control settings,
all of which can be changed in /etc/collectl.conf
Display output in verbose mode. This often
displays more data than in the default mode. When displaying detail data,
verbose mode is forced. Furthermore, if summary data for a single subsystem is
to be displayed in verbose mode, the headers are only repeated occasionally
whereas if multiple subsystems are involved each needs their own header.
Disply data in wide mode. When
displaying data on the terminal, some data is formatted followed by a K, M or
G as appropriate. Selecting this switch will cause the full field to be
displayed. Note that there is no attempt to align data with the column
headings in this mode.
SUBSYSTEM OPTIONS¶
The following options are subsystem specific and typically filter data for collection and/or display as well as affect the output format:NOTE - this does NOT effect data collection,
ALL disk data will always be collected. However, only data for disk names that
match the pattern(s) will be included in the summary totals and displayed
displayed when details are requested. Alternaltively, if you preface the first
expression with a caret, all names that match that string will be excluded
from the summary totals and detail displays rather then included. If you don't
know perl, a partial string will usually work too.
The default is to display ALL data but the
following will cause a subset to be displayed
f - display fan data
p - display current (power) data
t - display temperature data
C - convert temperature to Celcius if in Farenheit
F - convert temperature to Farenheit if in Celcius
M - display each type of data on separate line
T - display data truncated to whole integers (some implemenations displayed them
with fractional components)
9 - any number, will tell ipmitool to read on this device number
If specified as a comma separated list of perl
regular substitution expressions without the =~s portion, each expression is
applied to each environmental field name, thereby allowing one to rename the
column headers. This can be most useful when running on heterogeneuos systems
and you want consistent column names.
R - show memory values (including swap space)
as rates of change as opposed to absolute values. One can also show absolute
changes between intervals by including -on.
NOTE - this does NOT effect data collection,
ALL network data will always be collected. However, only data for network
names that match the pattern(s) will be included in the summary totals and
displayed displayed when details are requested. Alternaltively, if you preface
the first expression with a caret, all names that match that string will be
excluded from the summary totals and detail displays rather then included. If
you don't know perl, a partial string will usually work too.
e - include network error counts in brief and
explicit error types elsewhere
E - only include lines with network errors in them
i - include i/o sizes in brief mode
w - set width of network device name
Specify one or more comma separated filters as
a C/S followed by an nfs version number and only those will have data reported
on. For example, C2 says to report data on V2 Clients. As a data collection
performance optimization, if one or more client filters are specified, data
will actually be collected for all clients as is also done for servers.
These filters restrict which processes are
selected for collection/display. Using this filter will significanly reduce
the load on process data collection since collectl creates a blacklist of
those existing processes that do not pass the filter and so are permanently
excluded from any future processing.
The format of a filter is a one charter type followed by a match string.
Multiple filters may be specified if separated by commas.
c - substring of the command being executed as explicitly read from
/proc/pid/stat. Note that this can actually be a perl expression, so if you
want a command that ends in a particular string all you need to is append a \$
to the end of the string. Otherwise it would match any commands containing
that string.
C - any command that starts with the specified string
f - full path of the command, including arguments, as read from
/proc/pid/cmdline. Like the c modifier this too can be a perl expression.
p - pid
P - parent pid
u - any process ownerd by this user's UID or in the range specifide by uxxx-yyy
U - any process owned by this username
caution: the process names collectl tries to match with c and C is the
second field in /proc/pid/stat which may not necessarily be what you think! eg
the name for X emacs is actually emacs-x
These options control the way data is
displayed and can also improve data collection performance
c - include CPU time of children who have exited (same as ps -S)
f - use cumulative totals for page faults in process data instead of rates
i - show process I/O counters in display instead of default format
I - disable collection of I/O counters, see note below
m - show breakdown of memory utilization instead of default format
p - never look for new pids or threads during data collection
r - show root command name only (no directory) for narrower display
R - show ALL process priorities ('RT' currently displayed if realtime)
t - include ALL process threads (increases collection overhead)
w - widen display by including whole argument string, with optional max width
x - include extended process attributes (currently only for context switches)
z - exclude any processes with 0 in sort field (in --top mode)
Process data is the most expensive type of data collected, costing as much as 3
times the CPU load as all other types of data combined. Collecting thread data
makes this even more expensive. One can significantly reduce this load by over
25 percent by disabling the collection of I/O stats. However, keep in mind
that even if you don't try to optimize process data collection, the overall
system load by collectl can still be on the order of about 0.2% when running
as a daemon with default collection rates. See the online documentation on
measuring performance for more information.
A security hole was identified that allowed non-priviledged users to read
/proc/pid/io and guess password lengths and noe many distros retrict access to
the owner or root. As a result, non-priviledged users will see all 0 I/O
counts for processes that are not theirs when specifying --procopt i.
One can specify a list of slab names separated
by commas and only those slabs whose names start with those strings will be
listed or summaried.
s - exclude any slabs with an allocation of
0
S - only show those slabs whose allocations
changed since last display
i - include i/o sizes in brief mode
DESCRIPTION¶
The collectl utility is a system monitoring tool that records or displays specific operating system data for one or more sets of subsystems. Any set of the subsystems, such as CPU, Disks, Memory or Sockets can be included in or excluded from data collection. Data can either be displayed back to the terminal, or stored in either a compressed or uncompressed data file. The data files themselves can either be in raw format (essentially a direct copy from the associated /proc structures) or in a space separated plottable format such that it can be easily plotted using tools such as gnuplot or excel. Data files can be read and manipulated from the command line, or through use of command scripts.RESTRICTIONS/PROBLEMS¶
Thread reporting currently only works with 2.6 kernels.FILES, EXAMPLES AND MORE INFORMATION¶
http://collectl.sourceforge.net OR /opt/hp/collectl/docsACKNOWLEDGEMENTS¶
I would like to thank Rob Urban for his creation of the Tru64 Unix collect tool, which collectl is based on.AUTHOR¶
This program was written by Mark Seger (mjseger@gmail.com).| APRIL 2003 | LOCAL |