0.7.2

Bugfixes

• [tracer] ensuring submitted spans belong to the same trace, this fixes a possible data loss with message dropping trace reason: trace id mismatch when using threads (#133)
• [doc] added missing comma for Rack example, thanks @elyara for fixing this (#130)

Read the full changeset

0.7.1

New features

• it's now possible to configure Sidekiq service on a worker level, contributed by @krasnoukhov (#124, #125)

Minor changes

• a header X-Datadog-Trace-Count is now sent when posting payloads to agent, it contains the number of traces in the payload (#123)

Read the full changeset

0.7.0

New features

• add a Rack middleware that can be used with any web framework compliant with the Rack interface (#111, #116 - docs)
• add Grape auto instrumentation to trace all endpoints execution and before-after filters (#117 - docs)
• Rails integration can activate the Grape instrumentation using the auto_instrument_grape flag in the Rails initializer file (docs)

Major changes

• Rails uses out of the box the Rack middleware so that the full request processing is traced. Before, only the Rails controller was instrumented, making difficult to see anything that happens outside of the Rails framework. While this changes how some traces are displayed, it doesn't introduce any breaking change with previous versions (#112, #118, thanks @Ferdy89 for the contribution!). However, you can expect changes around the displayed names/URLs.

Bugfixes

• in some cases, Rails app would drop spans because they would have no service and not be properly instrumented. This, causing wrong stats and partial traces. It's now fixed with the new rack support (see above, #112)
• Span instances can be finished only once (#109)
• stacktraces are constructed with proper newline characters (#108 and #115, contributed by @Ferdy89 )
• ddtrace logs are easier to isolate from your apps log (#107)

Read the full changeset

0.6.2

New features

• Active Record support for Sinatra apps, many thanks to @cabello for this contribution (#88)
• When no service is given for the root span, a default one is picked up,
  to avoid dropping traces in the agent (#105)

Bugfixes

• Rails env is not used as a default env any more (#106)

Breaking changes

• If you use Rails and rely on the new env feature introduced by #92 in https://github.com/DataDog/dd-trace-rb/releases/v0.6.1 then you now need to explicitly set the value.

A typical Rails configuration would be:

    Rails.configuration.datadog_trace = {
      auto_instrument: true,
      auto_instrument_redis: true,
      env: Rails.env,
    }

Read the full changeset

0.6.1

New features

• Support for global tags, contributed by Robert Coker (#92)
• Logger enhancements, it's now overridable and log messages are by default marked as coming from ddtrace (#99)

Bugfixes

• [redis] fixed the type of the Redis service, now reports as a database (#97)

Read the full changeset

0.6.0

New features

• Support for Ruby 1.9 (#83)

Bugfixes

• [sidekiq] correctly handling wrappers such as Active Job and reporting the right resource #90 (reported & fixed by @tpendragon)
• [sidekiq] fixed initialize issue #91 (reported & fixed by @tpendragon)
• [active_record] reporting :cached key when available (fixes 0 msec span issue #57)
• [rails] reporting controller exceptions as errors in stats (#95)

Breaking changes

• [net/http] using METHOD and not URL as a resource. This temporarily break stats as the request GET /index now reports as GET instead of /index (#98)

Read the full changeset

0.5.0

New features

• Added Sidekiq integration (#79, #87, docs)
• Added client sampling to the Tracer (#74, #81, docs)

Bugfixes

• [rails] Redis instrumentation honors Rails settings; now it's not automatically activated and it works well with external processes like Sidekiq (#86)

Breaking changes

• Default port 7777 has been replaced with the new 8126 (available from Datadog Agent 5.11.0 and above) (#82)

Migrate from 0.4.x to 0.5.0

• Datadog Agent 5.11.0 or above is required.

Read the full changeset

0.4.3

Bugfixes

• [rails] discard all parameters from the cache_store configuration to exclude the connection address (#77)
• [elasticsearch] safe-guard when the body is already encoded by a third party library; this ensures that ElasticSearch query is properly executed even if there are tracing errors (#78)

Read the full changeset

0.4.2

Documentation

• Moving our documentation to http://www.rubydoc.info/gems/ddtrace/

Read the full changeset

0.4.1

Documentation

• Improved client documentation (#76)

Bugfixes

• Removed duplicated data in Redis integration (#69)
• Default log level is set to WARNING so the tracer doesn't spam application logs (#73)

Read the full changeset