0.4.0

Improvements

• The gem is available in the rubygems.org repository
• Extended support to Ruby 2.4.0
• Extended support to Passenger 5.0+
• Sinatra web application library is supported; requests and templates
  rendering are instrumented. See Sinatra documentation for more details.
• Ruby net/http module is instrumented so that HTTP calls are traced when
  the built-in module is used. See HTTP documentation for more details.

Bugfixes

• Use alias_method in Redis instrumentation to prevent recursion when
  other libraries are patching the same class (#56)
• Prevent conditional requires when ActiveRecord is not used (#62)
• Adding Passenger support for the underlying cache system. Now traces are
  properly generated when Rails.cache is used (#64)
• Reducing logs verbosity (#65) when Rails is auto instrumented

Breaking changes

• Rails auto-instrumentation is disabled by default. You have to manually
  activate the Rails instrumentation in your initializer. See Rails documentation
  for more details (#55)

Read the full changeset

Migrate from 0.3.1 to 0.4.0

• The official rubygems.org repository should be used and new versions will not be available in the previous repository. To receive new updates, change your Gemfile as follows:

source 'https://rubygems.org'

# tracing gem
gem 'ddtrace', '0.4.0'

# ...other gems...

• If you're using the Rails integration, update your config/initializers/datadog-tracer.rb so that the
  auto_instrument and auto_instrument_redis are both enabled (or
  disabled according to your choice). You can find an example in the following
  code:

# config/initializers/datadog-tracer.rb

# this condition activates or deactivates the Rails auto instrumentation
# according to your environment; change it so that it reflects your
# application requirements
tracer_status = Rails.env.staging? || Rails.env.production?

Rails.configuration.datadog_trace = {
  auto_instrument: tracer_status,
  auto_instrument_redis: tracer_status,
  default_service: 'my-rails-app',
  # ...other configurations...
}

0.3.1

Bugfixes

• ActiveSupport integration fixes
• Fixed span ordering problems, which could lead to inconsistent data (includes #48)

For more info, check our updated docs: http://gems.datadoghq.com/trace/docs/

See the full changeset

0.3.0

Major changes

• Redis support
• Elastic Search support
• Use only one thread, instead of two, to send data to the trace agent
• Rails users who want to send their traces to some other host than localhost should now use trace_agent_hostname in tracer configuration
• Bug fixes, including #42

For more info, check our updated docs: http://gems.datadoghq.com/trace/docs/

See the full changeset

0.2.0

Major changes

• added msgpack gem as a dependency
• using Trace Agent API v0.3 that supports both JSON and Msgpack formats
• provided JSONEncoder and MsgpackEncoder that are switched at runtime the API v0.3 is not reachable (404)
• MsgpackEncoder is the current default encoder

Read the full changeset

0.1.5

Release improvements

• [rails] the sql.query meta is sent only once in the ActiveSupport instrumentation
• [rails] the sql.query meta is properly obfuscated. This process takes place in the trace-agent so that our APM backend will receive the SQL query without parameters
• add experimental support for JRuby 9k. Actually we're still targeting the compatibility mode >=2.1.0
• [rails] cache activity is monitored under the rails-cache service (it's a default name). This means that you can monitor cache interactions even outside a user request. The service name can be changed using the default_cache_service setting.

For more info, check our updated docs: http://gems.datadoghq.com/trace/docs/

See the full changelog

0.1.4

Improvements

• the library uses the new trace agent API (v0.2). This improves performances on the communication side

Bugfixes

• ActiveRecord sets the SQL query as a resource name, so that you can search traces for each given query (query values are removed from the stored data)
• The database service now is recognized as a "Database service"
• Rails users can change the database service name updating the default_database_service in the Rails.configuration.datadog_trace. If the value is not set, it defaults to the adapter_name

Other

• the library is shipped with the BSD-3-Clauses license

Read the full changeset

0.1.3

Bugfixes

• fixed wrong rescue in the HTTPTransport#send. Errors related to the sending thread are reported as expected.

Read the full changeset

0.1.2

Integrations

• added support for Unicorn (4.8+ and 5.1+) and Puma (2.16+ and 3+)
• added experimental support for Passenger 5.0

Changes

• the span.set_tag enforces the string representation for the given value so if an array is given, it will be serialized as a string

Read the full changeset

0.1.1

Integrations

• [rails] using connection_config instead of the connection object
• [rails] instrumentation is set up using the config.after_initialize hook

Core

• add the Datadog::Tracer.debug_logging accessor to enable / disable the tracer debug mode

Read the full changeset

0.1.0

Core components

• Client implementation to trace Ruby code
• Supporting Ruby 2.3, 2.2, 2.1

Integrations

• add support for Ruby on Rails 3.2, 4.2, 5.0