diff options
| author | Andrew Newdigate <andrew@gitlab.com> | 2019-08-23 13:11:19 +0300 |
|---|---|---|
| committer | Nick Thomas <nick@gitlab.com> | 2019-08-23 13:11:19 +0300 |
| commit | 3956e7bb8695ebea0038d529162127fd514ea8f1 (patch) | |
| tree | 5e4777e71d95a093776b6af0363e011406703a6b /config/initializers/tracing.rb | |
| parent | f7f3b3c3efd58f31ed422808722b0c81a0bf1064 (diff) | |
Add cache tracing and Redis tracing
This change adds Distributed Tracing support for two new types of events
1. Redis Calls
1. ActiveSupport (Rails) Caching Operations
The intention is to help application developers and infrastructure
SREs to understand the pressure that caching operations can have on
the application when running at scale.
The Redis and Caching spans can be viewed in the Jaeger UI by clicking
the "Trace" link in the performance bar when running on GDK.
Diffstat (limited to 'config/initializers/tracing.rb')
| -rw-r--r-- | config/initializers/tracing.rb | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/config/initializers/tracing.rb b/config/initializers/tracing.rb index 3c8779f238f..5b55a06692e 100644 --- a/config/initializers/tracing.rb +++ b/config/initializers/tracing.rb @@ -21,9 +21,13 @@ if Labkit::Tracing.enabled? end end + # Instrument Redis + Labkit::Tracing::Redis.instrument + # Instrument Rails Labkit::Tracing::Rails::ActiveRecordSubscriber.instrument Labkit::Tracing::Rails::ActionViewSubscriber.instrument + Labkit::Tracing::Rails::ActiveSupportSubscriber.instrument # In multi-processed clustered architectures (puma, unicorn) don't # start tracing until the worker processes are spawned. This works |