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

Changelog History
Page 1

  • v3.1.4 Changes

    โž• Added

    • ffe49cfe patch - Support temporarily disabling GC profiling without reporting inaccurate gc_time metric durations. The MRI probe's gc_time will not report any value when the GC::Profiler.enabled? returns false.

    ๐Ÿ”„ Changed

    • ๐ŸŽ af7e666c patch - Listen if the Ruby Garbage Collection profiler is enabled and collect how long the GC is running for the Ruby VM magic dashboard. An app will need to call GC::Profiler.enable to enable the GC profiler. Do not enable this in production environments, or at least not for long, because this can negatively impact performance of apps.

    ๐Ÿ›  Fixed

    • ๐Ÿšฆ b3a163be patch - Fix the MRI probe using the Garbage Collection profiler instead of the NilProfiler when garbage collection instrumentation is not enabled for MRI probe. This caused unnecessary overhead.
  • v3.1.3 Changes

    โž• Added

    • ๐Ÿšฆ 811a1082 patch - Add the Transaction.current? helper to determine if any Transaction is currently active or not. AppSignal NilTransactions are not considered active transactions.

    ๐Ÿ”„ Changed

    • dc50d889 patch - Rename the (so far privately reported) gc_total_time metric to gc_time. It no longer reports the total time of Garbage Collection measured, but only the time between two (minutely) measurements.

    ๐Ÿ›  Fixed

    • ๐Ÿšฆ 7cfed987 patch - Fix error on unknown HTTP request method. When a request is made with an unknown request method, triggering and ActionController::UnknownHttpMethod, it will no longer break the AppSignal instrumentation but omit the request method in the sample data.
  • v3.1.2 Changes

    ๐Ÿ”„ Changed

    • ๐Ÿš€ 1b95bb4c patch - Report Garbage Collection total time metric as the delta between measurements. This reports a more user friendly metric that doesn't always goes up until the app restarts or gets a new deploy. This metric is reported 0 by default without GC::Profiler.enable having been called.
    • ๐Ÿšฆ 61a78fb0 patch - Bump agent to 06391fb

      • Accept "warning" value for the log_level config option.
      • Add aarch64 Linux musl build.
      • Improve debug logging from the extension.
      • Fix high CPU issue for appsignal-agent when nothing could be read from the socket.
  • v3.1.1 Changes

    ๐Ÿ”„ Changed

    • ๐Ÿšฆ e225c798 patch - Report all Ruby VM metrics as gauges. We previously reported some metrics as distributions, but all fields for those distributions would report the same values.

    ๐Ÿ›  Fixed

    • ๐Ÿšฆ 31fd19c6 patch - Add hostname tag for Ruby VM metrics. This allows us to graph every host separately and multiple hosts won't overwrite each other metrics.
  • v3.1.0 Changes

    โž• Added

    • ๐Ÿšฆ d10c3f32 minor - Add tracking of thread counts, garbage collection runs, heap slots and other garbage collection stats to the default MRI probe. These metrics will be shown in AppSignal.com in a new Ruby VM Magic Dashboard.

    ๐Ÿ”„ Changed

    • ๐Ÿšฆ 114fe4f9 patch - Bump agent to v-d573c9b

      • Display unsupported OpenTelemetry spans in limited form.
      • Clean up payload storage before sending. Should fix issues with locally queued payloads blocking data from being sent.
      • Add appsignal_create_opentelemetry_span function to create spans for further modification, rather than only import them.
    • ๐Ÿšฆ dd803449 patch - Report gauge delta value for allocated objects. This reports a more user friendly metric we can graph with a more stable continuous value in apps with stable memory allocation.

    • ๐Ÿš€ 547f925e patch - Report gauge delta value for Garbage Collection counts. This reports a more user friendly metric that doesn't always goes up until the app restarts or gets a new deploy.

    ๐Ÿ›  Fixed

    • ๐Ÿ†“ e555a81a patch - Fix FFI function calls missing arguments for appsignal_free_transaction and appsignal_free_data extension functions. This fixes a high CPU issue when these function calls would be retried indefinitely.
  • v3.0.27 Changes

    ๐Ÿ›  Fixed

    • ๐Ÿšฆ 7032dc4b patch - Use Dir.pwd to determine the current directory in the Capistrano 3 integration. It previously relied on ENV["pwd"] which returned nil in some scenarios.
  • v3.0.26 Changes

    โœ‚ Removed

    • ๐Ÿšฆ 56ec42ae patch - Remove Moped support as it is no longer the official Ruby Mongo driver and it's been unmaintained for 7 years.

    ๐Ÿ›  Fixed

    • ๐Ÿšฆ 991ca18d patch - Fix runtime errors on YAML load with older psych versions (< 4) used in combination with newer Ruby version (3.x).
  • v3.0.25 Changes

    โž• Added

    • ๐Ÿšฆ 399cf790 patch - Sanitize ActiveRecord::RecordNotUnique error messages to not include any database values that is not unique in the database. This ensures no personal information is sent to AppSignal through error messages from this error.
  • 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.