Skip to content
Ruby static tracing report
Shell Makefile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs
examples
img
scripts Disable gitignore in ci Jul 24, 2019
src Improve docs for alternative tracing tools Aug 17, 2019
templates
.gitignore
.gitmodules
.nojekyll
.rubocop.yml
.ruby-version
.spelling_ignore
.travis.yml
Makefile
README.md
TODO.md
bibliography.yaml
ieee-with-url.csl

README.md

Build Status

Docker Repository on Quay

USDT Report

This is the backend page for https://blog.srvthe.net/usdt-report-doc/, a report I have prepared of my exploration into USDT tracing in production.

I believe that this is relatively new territory, as up until now existing tracing in ruby has been limited to an "all or nothing" sort of approach, of attaching to every function in ruby, causing a guaranteed overhead to the application.

This debugging tax may be a reasonable compromise in development environments, but why should it need to be so in production?

USDT tracing offers a means of only analyzing code that needs to be analyzed, which reduce the overhead of collecting metrics.

You can’t perform that action at this time.