sysdig安装和使用介绍

Posted 2020-10-10 新美好时代

安装步骤
1)安装资源库
rpm --import https://s3.amazonaws.com/download.draios.com/DRAIOS-GPG-KEY.public
curl -s -o /etc/yum.repos.d/draios.repo http://download.draios.com/stable/rpm/draios.repo

2)安装epel包
rpm -ivh epel-release-6-8.noarch.rpm

3)安装内核包及dkms包
yum -y install kernel-devel-$(uname -r)
yum -y install kernel-devel-3.10.0-327.el7.x86_64.rpm
yum -y install dkms-2.2.0.3-31.1.noarch.rpm

4)安装sysdig包
yum -y install sysdig

#openssl安装包地址
https://www.openssl.org/source/

#sysdig安装包地址
https://www.sysdig.org/install/

#rpm安装包地址
https://centos.pkgs.org/
http://rpm.pbone.net/

#查看最耗时的文件
sudo sysdig-probe-loader
sudo sysdig -c topfiles_time

#安装
https://www.sysdig.org/install/

使用列子
https://github.com/draios/sysdig/wiki/sysdig-examples

 

 sysdig类型

----------------------
Field Class: fd

fd.num the unique number identifying the file descriptor.
fd.type type of FD. Can be ‘file‘, ‘directory‘, ‘ipv4‘, ‘ipv6‘, ‘unix‘,
‘pipe‘, ‘event‘, ‘signalfd‘, ‘eventpoll‘, ‘inotify‘ or ‘signal
fd‘.
fd.typechar type of FD as a single character. Can be ‘f‘ for file, 4 for IP
v4 socket, 6 for IPv6 socket, ‘u‘ for unix socket, p for pipe,
‘e‘ for eventfd, ‘s‘ for signalfd, ‘l‘ for eventpoll, ‘i‘ for i
notify, ‘o‘ for unknown.
fd.name FD full name. If the fd is a file, this field contains the full
path. If the FD is a socket, this field contain the connection
tuple.
fd.directory If the fd is a file, the directory that contains it.
fd.filename If the fd is a file, the filename without the path.
fd.ip matches the ip address (client or server) of the fd.
fd.cip client IP address.
fd.sip server IP address.
fd.lip local IP address.
fd.rip remote IP address.
fd.port (FILTER ONLY) matches the port (either client or server) of the
fd.
fd.cport for TCP/UDP FDs, the client port.
fd.sport for TCP/UDP FDs, server port.
fd.lport for TCP/UDP FDs, the local port.
fd.rport for TCP/UDP FDs, the remote port.
fd.l4proto the IP protocol of a socket. Can be ‘tcp‘, ‘udp‘, ‘icmp‘ or ‘ra
w‘.
fd.sockfamily the socket family for socket events. Can be ‘ip‘ or ‘unix‘.
fd.is_server ‘true‘ if the process owning this FD is the server endpoint in
the connection.
fd.uid a unique identifier for the FD, created by chaining the FD numb
er and the thread ID.
fd.containername
chaining of the container ID and the FD name. Useful when tryin
g to identify which container an FD belongs to.
fd.containerdirectory
chaining of the container ID and the directory name. Useful whe
n trying to identify which container a directory belongs to.
fd.proto (FILTER ONLY) matches the protocol (either client or server) of
the fd.
fd.cproto for TCP/UDP FDs, the client protocol.
fd.sproto for TCP/UDP FDs, server protocol.
fd.lproto for TCP/UDP FDs, the local protocol.
fd.rproto for TCP/UDP FDs, the remote protocol.
fd.net matches the IP network (client or server) of the fd.
fd.cnet client IP network.
fd.snet server IP network.
fd.lnet local IP network.
fd.rnet remote IP network.

----------------------
Field Class: process

proc.pid the id of the process generating the event.
proc.exe the first command line argument (usually the executable name or
a custom one).
proc.name the name (excluding the path) of the executable generating the
event.
proc.args the arguments passed on the command line when starting the proc
ess generating the event.
proc.env the environment variables of the process generating the event.
proc.cmdline full process command line, i.e. proc.name + proc.args.
proc.exeline full process command line, with exe as first argument, i.e. pro
c.exe + proc.args.
proc.cwd the current working directory of the event.
proc.nthreads the number of threads that the process generating the event cur
rently has, including the main process thread.
proc.nchilds the number of child threads that the process generating the eve
nt currently has. This excludes the main process thread.
proc.ppid the pid of the parent of the process generating the event.
proc.pname the name (excluding the path) of the parent of the process gene
rating the event.
proc.pcmdline the full command line (proc.name + proc.args) of the parent of
the process generating the event.
proc.apid the pid of one of the process ancestors. E.g. proc.apid[1] retu
rns the parent pid, proc.apid[2] returns the grandparent pid, a
nd so on. proc.apid[0] is the pid of the current process. proc.
apid without arguments can be used in filters only and matches
any of the process ancestors, e.g. proc.apid=1234.
proc.aname the name (excluding the path) of one of the process ancestors.
E.g. proc.aname[1] returns the parent name, proc.aname[2] retur
ns the grandparent name, and so on. proc.aname[0] is the name o
f the current process. proc.aname without arguments can be used
in filters only and matches any of the process ancestors, e.g.
proc.aname=bash.
proc.loginshellid
the pid of the oldest shell among the ancestors of the current
process, if there is one. This field can be used to separate di
fferent user sessions, and is useful in conjunction with chisel
s like spy_user.
proc.duration number of nanoseconds since the process started.
proc.fdopencount
number of open FDs for the process
proc.fdlimit maximum number of FDs the process can open.
proc.fdusage the ratio between open FDs and maximum available FDs for the pr
ocess.
proc.vmsize total virtual memory for the process (as kb).
proc.vmrss resident non-swapped memory for the process (as kb).
proc.vmswap swapped memory for the process (as kb).
thread.pfmajor number of major page faults since thread start.
thread.pfminor number of minor page faults since thread start.
thread.tid the id of the thread generating the event.
thread.ismain ‘true‘ if the thread generating the event is the main one in th
e process.
thread.exectime CPU time spent by the last scheduled thread, in nanoseconds. Ex
ported by switch events only.
thread.totexectime
Total CPU time, in nanoseconds since the beginning of the captu
re, for the current thread. Exported by switch events only.
thread.cgroups all the cgroups the thread belongs to, aggregated into a single
string.
thread.cgroup the cgroup the thread belongs to, for a specific subsystem. E.g
. thread.cgroup.cpuacct.
thread.vtid the id of the thread generating the event as seen from its curr
ent PID namespace.
proc.vpid the id of the process generating the event as seen from its cur
rent PID namespace.
thread.cpu the CPU consumed by the thread in the last second.
thread.cpu.user the user CPU consumed by the thread in the last second.
thread.cpu.system
the system CPU consumed by the thread in the last second.
thread.vmsize For the process main thread, this is the total virtual memory f
or the process (as kb). For the other threads, this field is ze
ro.
thread.vmrss For the process main thread, this is the resident non-swapped m
emory for the process (as kb). For the other threads, this fiel
d is zero.
proc.sid the session id of the process generating the event.
proc.sname the name of the current process‘s session leader. This is eithe
r the process with pid=proc.sid or the eldest ancestor that has
the same sid as the current process.
proc.tty The controlling terminal of the process. 0 for processes withou
t a terminal.

----------------------
Field Class: evt

evt.num event number.
evt.time event timestamp as a time string that includes the nanosecond p
art.
evt.time.s event timestamp as a time string with no nanoseconds.
evt.datetime event timestamp as a time string that includes the date.
evt.rawtime absolute event timestamp, i.e. nanoseconds from epoch.
evt.rawtime.s integer part of the event timestamp (e.g. seconds since epoch).
evt.rawtime.ns fractional part of the absolute event timestamp.
evt.reltime number of nanoseconds from the beginning of the capture.
evt.reltime.s number of seconds from the beginning of the capture.
evt.reltime.ns fractional part (in ns) of the time from the beginning of the c
apture.
evt.latency delta between an exit event and the correspondent enter event,
in nanoseconds.
evt.latency.s integer part of the event latency delta.
evt.latency.ns fractional part of the event latency delta.
evt.latency.human
delta between an exit event and the correspondent enter event,
as a human readable string (e.g. 10.3ms).
evt.deltatime delta between this event and the previous event, in nanoseconds
.
evt.deltatime.s integer part of the delta between this event and the previous e
vent.
evt.deltatime.ns
fractional part of the delta between this event and the previou
s event.
evt.outputtime this depends on -t param, default is %evt.time (‘h‘).
evt.dir event direction can be either ‘>‘ for enter events or ‘<‘ for e
xit events.
evt.type The name of the event (e.g. ‘open‘).
evt.type.is allows one to specify an event type, and returns 1 for events t
hat are of that type. For example, evt.type.is.open returns 1 f
or open events, 0 for any other event.
syscall.type For system call events, the name of the system call (e.g. ‘open
‘). Unset for other events (e.g. switch or sysdig internal even
ts). Use this field instead of evt.type if you need to make sur
e that the filtered/printed value is actually a system call.
evt.category The event category. Example values are ‘file‘ (for file operati
ons like open and close), ‘net‘ (for network operations like so
cket and bind), memory (for things like brk or mmap), and so on
.
evt.cpu number of the CPU where this event happened.
evt.args all the event arguments, aggregated into a single string.
evt.arg one of the event arguments specified by name or by number. Some
events (e.g. return codes or FDs) will be converted into a tex
t representation when possible. E.g. ‘evt.arg.fd‘ or ‘evt.arg[0
]‘.
evt.rawarg one of the event arguments specified by name. E.g. ‘evt.rawarg.
fd‘.
evt.info for most events, this field returns the same value as evt.args.
However, for some events (like writes to /dev/log) it provides
higher level information coming from decoding the arguments.
evt.buffer the binary data buffer for events that have one, like read(), r
ecvfrom(), etc. Use this field in filters with ‘contains‘ to se
arch into I/O data buffers.
evt.buflen the length of the binary data buffer for events that have one,
like read(), recvfrom(), etc.
evt.res event return value, as a string. If the event failed, the resul
t is an error code string (e.g. ‘ENOENT‘), otherwise the result
is the string ‘SUCCESS‘.
evt.rawres event return value, as a number (e.g. -2). Useful for range com
parisons.
evt.failed ‘true‘ for events that returned an error status.
evt.is_io ‘true‘ for events that read or write to FDs, like read(), send,
recvfrom(), etc.
evt.is_io_read ‘true‘ for events that read from FDs, like read(), recv(), recv
from(), etc.
evt.is_io_write ‘true‘ for events that write to FDs, like write(), send(), etc.
evt.io_dir ‘r‘ for events that read from FDs, like read(); ‘w‘ for events
that write to FDs, like write().
evt.is_wait ‘true‘ for events that make the thread wait, e.g. sleep(), sele
ct(), poll().
evt.wait_latency
for events that make the thread wait (e.g. sleep(), select(), p
oll()), this is the time spent waiting for the event to return,
in nanoseconds.
evt.is_syslog ‘true‘ for events that are writes to /dev/log.
evt.count This filter field always returns 1 and can be used to count eve
nts from inside chisels.
evt.count.error This filter field returns 1 for events that returned with an er
ror, and can be used to count event failures from inside chisel
s.
evt.count.error.file
This filter field returns 1 for events that returned with an er
ror and are related to file I/O, and can be used to count event
failures from inside chisels.
evt.count.error.net
This filter field returns 1 for events that returned with an er
ror and are related to network I/O, and can be used to count ev
ent failures from inside chisels.
evt.count.error.memory
This filter field returns 1 for events that returned with an er
ror and are related to memory allocation, and can be used to co
unt event failures from inside chisels.
evt.count.error.other
This filter field returns 1 for events that returned with an er
ror and are related to none of the previous categories, and can
be used to count event failures from inside chisels.
evt.count.exit This filter field returns 1 for exit events, and can be used to
count single events from inside chisels.
evt.around (FILTER ONLY) Accepts the event if it‘s around the specified ti
me interval. The syntax is evt.around[T]=D, where T is the valu
e returned by %evt.rawtime for the event and D is a delta in mi
lliseconds. For example, evt.around[1404996934793590564]=1000 w
ill return the events with timestamp with one second before the
timestamp and one second after it, for a total of two seconds
of capture.
evt.abspath Absolute path calculated from dirfd and name during syscalls li
ke renameat and symlinkat. Use ‘evt.abspath.src‘ or ‘evt.abspat
h.dst‘ for syscalls that support multiple paths.
evt.is_open_read
‘true‘ for open/openat events where the path was opened for rea
ding
evt.is_open_write
‘true‘ for open/openat events where the path was opened for wri
ting

----------------------
Field Class: user

user.uid user ID.
user.name user name.
user.homedir home directory of the user.
user.shell user‘s shell.

----------------------
Field Class: group

group.gid group ID.
group.name group name.

----------------------
Field Class: syslog

syslog.facility.str
facility as a string.
syslog.facility facility as a number (0-23).
syslog.severity.str
severity as a string. Can have one of these values: emerg, aler
t, crit, err, warn, notice, info, debug
syslog.severity severity as a number (0-7).
syslog.message message sent to syslog.

----------------------
Field Class: container

container.id the container id.
container.name the container name.
container.image the container image name (e.g. sysdig/sysdig:latest for docker,
).
container.image.id
the container image id (e.g. 6f7e2741b66b).
container.type the container type, eg: docker or rkt
container.privileged
true for containers running as privileged, false otherwise
container.mounts
A space-separated list of mount information. Each item in the l
ist has the format <source>:<dest>:<mode>:<rdrw>:<propagation>
container.mount Information about a single mount, specified by number (e.g. con
tainer.mount[0]) or mount source (container.mount[/usr/local]).
The pathname can be a glob (container.mount[/usr/local/*]), in
which case the first matching mount will be returned. The info
rmation has the format <source>:<dest>:<mode>:<rdrw>:<propagati
on>. If there is no mount with the specified index or matching
the provided source, returns the string "none" instead of a NUL
L value.
container.mount.source
the mount source, specified by number (e.g. container.mount.des
t[0]) or mount destination (container.mount.source[/usr/local])
. The pathname can be a glob.
container.mount.dest
the mount destination, specified by number (e.g. container.moun
t.dest[0]) or mount source (container.mount.dest[/usr/local]).
The pathname can be a glob.
container.mount.mode
the mount mode, specified by number (e.g. container.mount.mode[
0]) or mount source (container.mount.mode[/usr/local]). The pat
hname can be a glob.
container.mount.rdwr
the mount rdwr value, specified by number (e.g. container.mount
.rdwr[0]) or mount source (container.mount.rdwr[/usr/local]). T
he pathname can be a glob.
container.mount.propagation
the mount propagation value, specified by number (e.g. containe
r.mount.propagation[0]) or mount source (container.mount.propag
ation[/usr/local]). The pathname can be a glob.

----------------------
Field Class: fdlist

fdlist.nums for poll events, this is a comma-separated list of the FD numbe
rs in the ‘fds‘ argument, returned as a string.
fdlist.names for poll events, this is a comma-separated list of the FD names
in the ‘fds‘ argument, returned as a string.
fdlist.cips for poll events, this is a comma-separated list of the client I
P addresses in the ‘fds‘ argument, returned as a string.
fdlist.sips for poll events, this is a comma-separated list of the server I
P addresses in the ‘fds‘ argument, returned as a string.
fdlist.cports for TCP/UDP FDs, for poll events, this is a comma-separated lis
t of the client TCP/UDP ports in the ‘fds‘ argument, returned a
s a string.
fdlist.sports for poll events, this is a comma-separated list of the server T
CP/UDP ports in the ‘fds‘ argument, returned as a string.

----------------------
Field Class: k8s

k8s.pod.name Kubernetes pod name.
k8s.pod.id Kubernetes pod id.
k8s.pod.label Kubernetes pod label. E.g. ‘k8s.pod.label.foo‘.
k8s.pod.labels Kubernetes pod comma-separated key/value labels. E.g. ‘foo1:bar
1,foo2:bar2‘.
k8s.rc.name Kubernetes replication controller name.
k8s.rc.id Kubernetes replication controller id.
k8s.rc.label Kubernetes replication controller label. E.g. ‘k8s.rc.label.foo
‘.
k8s.rc.labels Kubernetes replication controller comma-separated key/value lab
els. E.g. ‘foo1:bar1,foo2:bar2‘.
k8s.svc.name Kubernetes service name (can return more than one value, concat
enated).
k8s.svc.id Kubernetes service id (can return more than one value, concaten
ated).
k8s.svc.label Kubernetes service label. E.g. ‘k8s.svc.label.foo‘ (can return
more than one value, concatenated).
k8s.svc.labels Kubernetes service comma-separated key/value labels. E.g. ‘foo1
:bar1,foo2:bar2‘.
k8s.ns.name Kubernetes namespace name.
k8s.ns.id Kubernetes namespace id.
k8s.ns.label Kubernetes namespace label. E.g. ‘k8s.ns.label.foo‘.
k8s.ns.labels Kubernetes namespace comma-separated key/value labels. E.g. ‘fo
o1:bar1,foo2:bar2‘.
k8s.rs.name Kubernetes replica set name.
k8s.rs.id Kubernetes replica set id.
k8s.rs.label Kubernetes replica set label. E.g. ‘k8s.rs.label.foo‘.
k8s.rs.labels Kubernetes replica set comma-separated key/value labels. E.g. ‘
foo1:bar1,foo2:bar2‘.
k8s.deployment.name
Kubernetes deployment name.
k8s.deployment.id
Kubernetes deployment id.
k8s.deployment.label
Kubernetes deployment label. E.g. ‘k8s.rs.label.foo‘.
k8s.deployment.labels
Kubernetes deployment comma-separated key/value labels. E.g. ‘f
oo1:bar1,foo2:bar2‘.

----------------------
Field Class: mesos

mesos.task.name Mesos task name.
mesos.task.id Mesos task id.
mesos.task.label
Mesos task label. E.g. ‘mesos.task.label.foo‘.
mesos.task.labels
Mesos task comma-separated key/value labels. E.g. ‘foo1:bar1,fo
o2:bar2‘.
mesos.framework.name
Mesos framework name.
mesos.framework.id
Mesos framework id.
marathon.app.name
Marathon app name.
marathon.app.id Marathon app id.
marathon.app.label
Marathon app label. E.g. ‘marathon.app.label.foo‘.
marathon.app.labels
Marathon app comma-separated key/value labels. E.g. ‘foo1:bar1,
foo2:bar2‘.
marathon.group.name
Marathon group name.
marathon.group.id
Marathon group id.

----------------------
Field Class: span

span.id ID of the span. This is a unique identifier that is used to mat
ch the enter and exit tracer events for this span. It can also
be used to match different spans belonging to a trace.
span.time time of the span‘s enter tracer as a human readable string that
includes the nanosecond part.
span.ntags number of tags that this span has.
span.nargs number of arguments that this span has.
span.tags dot-separated list of all of the span‘s tags.
span.tag one of the span‘s tags, specified by 0-based offset, e.g. ‘span
.tag[1]‘. You can use a negative offset to pick elements from t
he end of the tag list. For example, ‘span.tag[-1]‘ returns the
last tag.
span.args comma-separated list of the span‘s arguments.
span.arg one of the span arguments, specified by name or by 0-based offs
et. E.g. ‘span.arg.xxx‘ or ‘span.arg[1]‘. You can use a negativ
e offset to pick elements from the end of the tag list. For exa
mple, ‘span.arg[-1]‘ returns the last argument.
span.enterargs comma-separated list of the span‘s enter tracer event arguments
. For enter tracers, this is the same as evt.args. For exit tra
cers, this is the evt.args of the corresponding enter tracer.
span.enterarg one of the span‘s enter arguments, specified by name or by 0-ba
sed offset. For enter tracer events, this is the same as evt.ar
g. For exit tracer events, this is the evt.arg of the correspon
ding enter event.
span.duration delta between this span‘s exit tracer event and the enter trace
r event.
span.duration.human
delta between this span‘s exit tracer event and the enter event
, as a human readable string (e.g. 10.3ms).

----------------------
Field Class: evtin

evtin.span.id accepts all the events that are between the enter and exit trac
ers of the spans with the given ID and are generated by the sam
e thread that generated the tracers.
evtin.span.ntags
accepts all the events that are between the enter and exit trac
ers of the spans with the given number of tags and are generate
d by the same thread that generated the tracers.
evtin.span.nargs
accepts all the events that are between the enter and exit trac
ers of the spans with the given number of arguments and are gen
erated by the same thread that generated the tracers.
evtin.span.tags accepts all the events that are between the enter and exit trac
ers of the spans with the given tags and are generated by the s
ame thread that generated the tracers.
evtin.span.tag accepts all the events that are between the enter and exit trac
ers of the spans with the given tag and are generated by the sa
me thread that generated the tracers. See the description of sp
an.tag for information about the syntax accepted by this field.
evtin.span.args accepts all the events that are between the enter and exit trac
ers of the spans with the given arguments and are generated by
the same thread that generated the tracers.
evtin.span.arg accepts all the events that are between the enter and exit trac
ers of the spans with the given argument and are generated by t
he same thread that generated the tracers. See the description
of span.arg for information about the syntax accepted by this f
ield.
evtin.span.p.id same as evtin.span.id, but also accepts events generated by oth
er threads in the same process that produced the span.
evtin.span.p.ntags
same as evtin.span.ntags, but also accepts events generated by
other threads in the same process that produced the span.
evtin.span.p.nargs
same as evtin.span.nargs, but also accepts events generated by
other threads in the same process that produced the span.
evtin.span.p.tags
same as evtin.span.tags, but also accepts events generated by o
ther threads in the same process that produced the span.
evtin.span.p.tag
same as evtin.span.tag, but also accepts events generated by ot
her threads in the same process that produced the span.
evtin.span.p.args
same as evtin.span.args, but also accepts events generated by o
ther threads in the same process that produced the span.
evtin.span.p.arg
same as evtin.span.arg, but also accepts events generated by ot
her threads in the same process that produced the span.
evtin.span.s.id same as evtin.span.id, but also accepts events generated by the
script that produced the span, i.e. by the processes whose par
ent PID is the same as the one of the process generating the sp
an.
evtin.span.s.ntags
same as evtin.span.id, but also accepts events generated by the
script that produced the span, i.e. by the processes whose par
ent PID is the same as the one of the process generating the sp
an.
evtin.span.s.nargs
same as evtin.span.id, but also accepts events generated by the
script that produced the span, i.e. by the processes whose par
ent PID is the same as the one of the process generating the sp
an.
evtin.span.s.tags
same as evtin.span.id, but also accepts events generated by the
script that produced the span, i.e. by the processes whose par
ent PID is the same as the one of the process generating the sp
an.
evtin.span.s.tag
same as evtin.span.id, but also accepts events generated by the
script that produced the span, i.e. by the processes whose par
ent PID is the same as the one of the process generating the sp
an.
evtin.span.s.args
same as evtin.span.id, but also accepts events generated by the
script that produced the span, i.e. by the processes whose par
ent PID is the same as the one of the process generating the sp
an.
evtin.span.s.arg
same as evtin.span.id, but also accepts events generated by the
script that produced the span, i.e. by the processes whose par
ent PID is the same as the one of the process generating the sp
an.
evtin.span.m.id same as evtin.span.id, but accepts all the events generated on
the machine during the span, including other threads and other
processes.
evtin.span.m.ntags
same as evtin.span.id, but accepts all the events generated on
the machine during the span, including other threads and other
processes.
evtin.span.m.nargs
same as evtin.span.id, but accepts all the events generated on
the machine during the span, including other threads and other
processes.
evtin.span.m.tags
same as evtin.span.id, but accepts all the events generated on
the machine during the span, including other threads and other
processes.
evtin.span.m.tag
same as evtin.span.id, but accepts all the events generated on
the machine during the span, including other threads and other
processes.
evtin.span.m.args
same as evtin.span.id, but accepts all the events generated on
the machine during the span, including other threads and other
processes.
evtin.span.m.arg
same as evtin.span.id, but accepts all the events generated on
the machine during the span, including other threads and other
processes.

 

sysdig命令

Category: Application
---------------------
httplog HTTP requests log
httptop Top HTTP requests
memcachelog memcached requests log

Category: CPU Usage
-------------------
spectrogram Visualize OS latency in real time.
subsecoffset Visualize subsecond offset execution time.
topcontainers_cpu
Top containers by CPU usage
topprocs_cpu Top processes by CPU usage

Category: Errors
----------------
topcontainers_error
Top containers by number of errors
topfiles_errors Top files by number of errors
topprocs_errors top processes by number of errors

Category: I/O
-------------
echo_fds Print the data read and written by processes.
fdbytes_by I/O bytes, aggregated by an arbitrary filter field
fdcount_by FD count, aggregated by an arbitrary filter field
fdtime_by FD time group by
iobytes Sum of I/O bytes on any type of FD
iobytes_file Sum of file I/O bytes
spy_file Echo any read/write made by any process to all files. Optionall
y, you can provide the name of one file to only intercept reads
/writes to that file.
stderr Print stderr of processes
stdin Print stdin of processes
stdout Print stdout of processes
topcontainers_file
Top containers by R+W disk bytes
topfiles_bytes Top files by R+W bytes
topfiles_time Top files by time
topprocs_file Top processes by R+W disk bytes

Category: Logs
--------------
spy_logs Echo any write made by any process to a log file. Optionally, e
xport the events around each log message to file.
spy_syslog Print every message written to syslog. Optionally, export the e
vents around each syslog message to file.

Category: Misc
--------------
around Export to file the events around the time range where the given
filter matches.

Category: Net
-------------
iobytes_net Show total network I/O bytes
spy_ip Show the data exchanged with the given IP address
spy_port Show the data exchanged using the given IP port number
topconns Top network connections by total bytes
topcontainers_net
Top containers by network I/O
topports_server Top TCP/UDP server ports by R+W bytes
topprocs_net Top processes by network I/O

Category: Performance
---------------------
bottlenecks Slowest system calls
fileslower Trace slow file I/O
netlower Trace slow network I/0
proc_exec_time Show process execution time
scallslower Trace slow syscalls
topscalls Top system calls by number of calls
topscalls_time Top system calls by time

Category: Security
------------------
list_login_shells
List the login shell IDs
shellshock_detect
print shellshock attacks
spy_users Display interactive user activity

Category: System State
----------------------
lscontainers List the running containers
lsof List (and optionally filter) the open file descriptors.
netstat List (and optionally filter) network connections.
ps List (and optionally filter) the machine processes.

Category: Tracers
-----------------
tracers_2_statsd
Export spans duration as statds metrics.

Use the -i flag to get detailed information about a specific chisel