1. 24 Jan, 2019 1 commit
  2. 22 Jan, 2019 1 commit
    • Andrew Newdigate's avatar
      Adds inter-service OpenTracing propagation · ca464b60
      Andrew Newdigate authored
      This change allows the GitLab rails and sidekiq components to receive
      tracing spans from upstream services such as Workhorse and pass these
      spans on to downstream services including Gitaly and Sidekiq.
      This change will also emit traces for incoming and outgoing requests
      using the propagated trace information. This will allow operators and
      engineers to view traces across the Workhorse, GitLab Rails, Sidekiq and
      Gitaly components.
      Additional intra-service instrumentation will be added in future
  3. 17 Jan, 2019 1 commit
    • Andrew Newdigate's avatar
      Conditionally initialize the global opentracing tracer · 57a8859a
      Andrew Newdigate authored
      This change will instantiate an OpenTracing tracer and configure it
      as the global tracer when the GITLAB_TRACING environment variable is
      configured. GITLAB_TRACING takes a "connection string"-like value,
      encapsulating the driver (eg jaeger, etc) and options for the driver.
      Since each service, whether it's written in Ruby or Golang, uses the
      same connection-string, it should be very easy to configure all
      services in a cluster, or even a single development machine to be
      setup to use tracing.
      Note that this change does not include instrumentation or propagation
      changes as this is a way of breaking a previous larger change into
      components. The instrumentation and propagation changes will follow
      in separate changes.