blob: ddb92c4b3b224a82e5673269a8f02deddb60208b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
SystemTap PMDA
==============
This PMDA uses the SystemTap Linux kernel trace infrastructure to obtain
performance data. Both SystemTap and this PMDA are easily configurable,
allowing arbitrary trace points to be monitored. The PMDA itself is all
Perl code, and thus easily extended to monitor additional types of trace
information from SystemTap.
The file $PCP_PMDAS_DIR/probes.stp contains the SystemTap script which
will be run by the stap(1) command to insert the kernel instrumentation.
It is intended that once suitable instrumentation has been found running
SystemTap interactively, that a modified probes.stp and PMDA would then
be installed to export the interesting data to PCP clients (for logging,
charting, etc).
Metrics
=======
The file ./help contains descriptions for all of the metrics exported
by this PMDA.
Once the PMDA has been installed, the following command will list all
the available metrics and their explanatory "help" text:
$ pminfo -fT systemtap
Installation
============
+ # cd $PCP_PMDAS_DIR/systemtap
+ Check that there is no clash in the Performance Metrics Domain
defined in ./domain.h and the other PMDAs currently in use (see
$PCP_PMCDCONF_PATH). If there is, edit pmdasystemtap.pl to use
a different domain number.
+ Then simply use
# ./Install
and choose both the "collector" and "monitor" installation
configuration options.
De-installation
===============
+ Simply use
# cd $PCP_PMDAS_DIR/systemtap
# ./Remove
Troubleshooting
===============
+ After installing or restarting the agent, the PMCD log file
($PCP_LOG_DIR/pmcd/pmcd.log) and the PMDA log file
($PCP_LOG_DIR/pmcd/systemtap.log) should be checked for any
warnings or errors.
|
