All Versions
208
Latest Version
Avg Release Cycle
22 days
Latest Release
-

Changelog History
Page 2

  • v3.0.24 Changes

    🔄 Changed

    • 🚦 964861f7 patch - Bump agent to v-f57e6cb

      • Enable process metrics on Heroku and Dokku
  • v3.0.23 Changes

    🛠 Fixed

    • 🚦 d73905d3 patch - Fix sanitized values wrapped in Arrays. When a value like [{ "foo" => "bar" }] was sanitized it would be stored as { "foo" => "?" }, omitting the parent value's Array square brackets. Now values will appear with the same structure as they were originally sanitized. This only applies to certain integrations like MongoDB, moped and ElasticSearch.
    • 096d3cdf patch - Fix the ActiveJob default_queue_name config option issue being reset to "default". When ActiveJob default_queue_name was set in a Rails initializer it would reset on load to default. Now the default_queue_name can be set in an initializer as well.
  • v3.0.22 Changes

    🔄 Changed

    • 🚦 9762e79d patch - Bump agent to v-bbc830a

      • Support batched statsd messages
      • Set start times for spans with traceparents
      • Check duration in transactions for negative and too high value
  • v3.0.21 Changes

    🔄 Changed

    • 🚦 548dd6f4 patch - Add config override source. Track final decisions made by the Ruby gem in the configuration in the override config source. This will help us track new config options which are being set by their deprecated predecessors in the diagnose report.

    ✂ Removed

    • 🚦 3f503ade patch - Remove internal Appsignal.extensions system. It was unused.
  • v3.0.20 Changes

    ➕ Added

    • 35bd83b8 patch - Add send_session_data option to configure if session data is automatically included transactions. By default this is turned on. It can be disabled by configuring send_session_data to false.

    🗄 Deprecated

    • 35bd83b8 patch - Deprecate skip_session_data option in favor of the newly introduced send_session_data option. If it is configured it will print a warning on AppSignal load, but will also retain its functionality until the config option is fully removed in the next major release.
    • e51a8fb6 patch - Warn about the deprecated working_dir_path option from all config sources. It previously only printed a warning when it was configured in the config/appsignal.yml file, but now also prints the warning if it's set via the Config class initialize options and environment variables. Please use the working_directory_path option instead.

    🛠 Fixed

    • 🚀 c9000eee patch - Fix reported Ruby version in diagnose report. It would report only the first major release of the series, e.g. 2.6.0 for 2.6.1.
  • v3.0.19 Changes

    🔄 Changed

    • 🚦 2587eae3 patch - Store the extension install report as JSON, instead of YAML. Reduces internal complexity.

    🛠 Fixed

    • 🚦 243c1ed4 patch - Improve compatibility with the sequel-rails gem by tracking the performed SQL query in instrumentation events.
  • v3.0.18 Changes

    ➕ Added

    • 🚦 d7bfcdf1 patch - Add Ruby 3.1.0 support. There was an issue with YAML.load arguments when parsing the appsignal.yml config file.
  • v3.0.17 Changes

    🛠 Fixed

    • 🔧 f9d57752 patch - Use the log_level option for the Ruby gem logger. Previously it only configured the extension and agent loggers. Also fixes the debug and transaction_debug_mode option if no log_level is configured by the app.
  • v3.0.16 Changes

    ➕ Added

    • 🚦 fe226e99 patch - Add experimental Span API. This is not loaded by default and we do not recommend using it yet.
    • 🚦 84b1ba18 patch - Add "log_level" config option. This new option allows you to define the kind of messages AppSignal's will log and up. The "debug" option will log all "debug", "info", "warning" and "error" log messages. The default value is: "info"

    The allowed values are:

    • error
    • warning
    • info
    • debug
      • 🚦 6b2ecca2 patch - Clean up index values in error messages from PG index violation errors.

    🔄 Changed

    • 🚦 25bde454 patch - Order the config options alphabetically in diagnose report output.
    • fe226e99 patch - Use the filter_parameters and filter_session_data options to filter out specific parameter keys or session data keys for the experimental Span API. Previously only the (undocumented) filter_data_keys config option was available to filter out all kinds of app data.
    • 🚦 fe226e99 patch - Standardize diagnose validation failure message. Explain the diagnose request failed and why.
    • 🚦 fe226e99 patch - Bump agent to v-5b63505

      • Only filter parameters with the filter_parameters config option.
      • Only filter session data with the filter_session_data config option.
    • 🚦 3ad95ea5 patch - Bump agent to v-0db01c2

      • Add log_level config option in extension.
      • Deprecate debug and transaction_debug_mode option in extension.

    🗄 Deprecated

    • 84b1ba18 patch - Deprecate "debug" and "transaction_debug_mode" config options in favor of the new "log_level" config option.
  • v3.0.15 Changes

    • 🚦 b40b3b4f patch - Print String values in the diagnose report surrounded by quotes. Makes it more clear that it's a String value and not a label we print.
    • 🚦 fd6faf16 patch - Bump agent to 09308fb

      • Update sql_lexer dependency with support for reversed operators in queries.
      • Add debug level logging to custom metrics in transaction_debug_mode.
      • Add hostname config option to standalone agent.