- 1 Systemtap Static Probes
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 How To Test
- 1.8 User Experience
- 1.9 Dependencies
- 1.10 Contingency Plan
- 1.11 Documentation
- 1.12 Release Notes
- 1.13 Comments and Discussion
Systemtap Static Probes
WORK IN PROGRESS: Currently a copy of Features/SystemtapStaticProbes, will turn into a new feature page for f14. SHOULD BE SPLIT INTO SEPARATE FEATURES: Make them individually for interested/participating packages
Systemtap allows event tracing of programs when they have static probes inserted. This allows for tracing specifics of an application on a higher level that is meaningful to the application user so they don't have to know the exact source code details for tracing what is happening.
- Name: Mark Wielaard
- email: email@example.com
- Targeted release: Fedora 14
- Last updated: 22 Feb 2009
- Percentage of completion: 10%, work based on F13 feature.
- See under scope for individual package status.
- Some experiments showed some greater than expected impact on performance in the dormant case. So for each package identified we need to do some benchmarking to make sure there is zero overhead in to normal case. (Add any relevants benchmarks to the scopes section under the relevant package please).
By packaging a new version of systemtap, that enables programs that already have static dtrace probe markers in their sources and by making those packages build depend on the new systemtap-sdt-devel package and recompiling them with probe points enabled, users of those packages will be able to trace any high level events that these packages provide.
Benefit to Fedora
It will be easier for developers and users to observe what is really happening on their system on a higher (application) level.
- Work with upstream to identify any issues with the new capabilities while we activate probes in packages.
- Identify packages that already include static user probes (see below)
- Work with package maintainer to enable them in the Fedora build spec file.
- Add documentation on enabled probes and how to use them with a systemtap tapset.
Currently identified packages:
See also the F13 feature for java, python. tcl and postgresql work that could be expanded.
- Need tweaks to systemtap to gen proper header from .d file (should be fixed with systemtap 1.1 package).
- Add patch from upstream docs
Tracking bug: https://bugzilla.redhat.com/show_bug.cgi?id=496113
- firefox-3.1-0.6 (upstream docs) - rajan
- Profile Firefox using SystemTap on DTrace probes: ProfilingFirefox
- mysql 6.0.8: really new alpha version from mysql.com has probes. However, the version in fedora 5.0.67 doesn't. A backport would be required. Won't be in next fedora
- apachetop-0.12.6 (newer httpd have patches directly  - note needs some build tweaking)
- php-5.2.8: implemented as an add-on module (shared library listed in /etc/php.ini) that intercepts internal php interpreter function pointers and wraps those calls with markers
- ruby-1.8.6-p287: similar to php, but richer & far more complicated
- ghc very recently got some static probe support see http://hackage.haskell.org/trac/ghc/wiki/DTrace (not tried to build yet).
- darcs patch
It seems as if several of the above were dtrace-instrumented in code that was never merged into the upstream versions of the package, but instead represented as run-time add-ons or private patches for Solaris distributions. Disappointing, but perhaps we can do better and engage the respective upstream teams. This will of course take time and panache.
At least the patches tend to be very small so we have some freedom to choose between approaches (adding STAP_PROBE/whatever hooks directly to the core upstream code; or fedora local patches; or add-on shared libraries like for php/httpd).
Another approach worth considering is adding tapsets that map process.mark() events to process.function/statement() to approximate the dtrace out-of-tree patches.
How To Test
Whether systemtap and static markers are working in general can be tested by installing systemtap, kernel-debuginfo and the systemtap-testsuite. Running sudo make installcheck in /usr/share/systemtap/testsuite
When applications get static markers enabled we should add them to a testing page listing:
- Package install instructions.
- Setup and sample run of the application
- A reference to the probe names.
- And an simple example stap invocation listing markers that can be enabled.
Question: Is there a convention/template for adding such test pages for test days?
For packages that have static probes enabled users will be able to trace high-level events, like for example database transactions, through stap.
- Might need some coordination with gcc (for debug info output) and elfutils (for grokking the debuginfo output). But this is mostly done upstream already.
- Any package wishing to expose existing probes in its (upstream) sources depending on systemtap-sdt-devel and adding an --enable-dtrace or equivalent to its spec file.
- Not required for this feature, but since systemtap uses debuginfo, this feature is enhanced by the Debug Info Revamp Feature.
Even if all the tracing will not work, packages that are converted to provide static probes will not be impacted since the probe points have (near) zero overhead, so in the worse case some packages were recompiled to enable the feature, but users will still not be able to use it.
The upstream wiki is the best description for now http://sourceware.org/systemtap/wiki/UsingStaticUserMarkers the systemtap list has an example on converting a package http://sourceware.org/ml/systemtap/2009-q1/msg00140.html
While working on this feature this section will be expanded to list packages that have probe points enabled and pointers to (upstream) package documentation on the probe names and semantics like for postgresql http://www.postgresql.org/docs/8.2/static/dynamic-trace.html
Systemtap has been extended to support user space tracing, and in particular to support static (dtrace compatible) markers enabled in various programs in Fedora 12. This enables users, developers and administrators a high level overview of what is going on with their system or deep down in a specific program or subsystem.
Systemtap comes with a tutorial, a language reference manual, a tapsets reference and an examples directory under /usr/share/doc/systemtap-?.?/
- TODO: Should have a list of which packages were enabled with markers when finished.
Comments and Discussion