Skip to content

0.47.0

Compare
Choose a tag to compare
@marcotc marcotc released this 29 Mar 23:00
· 7436 commits to master since this release
dfddf9b

Added

Changed

  • BREAKING Separate Resolver configuration and resolution steps (#1319)

    ActiveRecord describes configuration now supports partial matching

    Partial matching of connection fields (adapter, username, host, port, database) is now allowed. Previously, only an exact match of connections fields would be considered matching. This should help greatly simplify database configuration matching, as you will only need to provide enough fields to correctly separate your distinct database connections.

    If you have a c.use active_record, describe: statement in your application that is currently not matching any connections, you might start seeing them match after this release.

    c.use active_record, describe: statements that are currently matching a connection will continue to match that same connection.

    You can refer to the expanded ActiveSupport documentation for details on how to use the new partial matchers and configuration code examples.

    Datadog::Contrib::Configuration::Resolver interface changed

    The interface for Datadog::Contrib::Configuration::Resolver has changed: custom configuration resolvers that inherit from Datadog::Contrib::Configuration::Resolver will need be changed to fulfill the new interface. See code documentation for Datadog::Contrib::Configuration::Resolver for specific API requirements.

  • Remove type check from ThreadLocalContext#local. (#1399) (@orekyuu)

Fixed

  • Support for JRuby 9.2.0.0 (#1409)
  • Failed integration message (#1394) (@e1senh0rn)
  • Addressed "warning: instance variable @components not initialized" (#1419)
  • Close /proc/self/cgroup file after reading (#1414)
  • Improve internal "only once" behavior across the tracer (#1398)
  • Increase thread-safety during tracer initialization (#1418)

Refactored

Read the full changeset and the release milestone.