Skip to content

Commit

Permalink
Roll up HTTP Clients in datadog tracing (forem#21326)
Browse files Browse the repository at this point in the history
  • Loading branch information
benhalpern authored Oct 14, 2024
1 parent 086a6a2 commit 99d0828
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions config/initializers/datadog.rb
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,13 @@
c.tracing.instrument :active_record, service_name: "#{service_name}-db"
c.tracing.instrument :sidekiq, service_name: "#{service_name}-sidekiq"
c.tracing.instrument :concurrent_ruby
c.tracing.instrument :excon, service_name: "#{service_name}-excon"
c.tracing.instrument :httprb, service_name: "#{service_name}-httprb"
c.tracing.instrument :http, service_name: "#{service_name}-net_http"
c.tracing.instrument :faraday, service_name: "#{service_name}-faraday"

# All HTTP clients roll up to one
unified_service_name = "#{service_name}-http_clients"
c.tracing.instrument :excon, service_name: unified_service_name
c.tracing.instrument :httprb, service_name: unified_service_name
c.tracing.instrument :http, service_name: unified_service_name
c.tracing.instrument :faraday, service_name: unified_service_name

# Multiple Redis integrations to split Redis usage per-instance to
# accommodate having a different Redis instance for each use case.
Expand Down

0 comments on commit 99d0828

Please sign in to comment.