Magicians never share their secrets. But we do. Sign up for our Ruby Magic email series and receive deep insights about garbage collection, memory allocation, concurrency and much more.
We just released AppSignal for Ruby gem version 2.3 which adds support for ActionCable, parameter filtering for background jobs and contains a lot of other improvements.
The AppSignal gem now supports ActionCable, a new feature available in Rails 5.0. Our integration supports error tracking and performance monitoring for actions and subscription events.
When a client connects or disconnects from a ActionCable connection or when an action is performed AppSignal will track these events. All ActionCable metrics will be grouped under the custom “ActionCable” namespace, a feature we introduced in Gem 2.2.
This is a first version of the ActionCable integration and we hope to improve it with your feedback. So please let us know what you’re missing and if something is not working as expected.
We’ve always supported parameter filtering for HTTP requests to avoid sending sensitive data to our servers. This filtering is now also available for background jobs.
Usually arguments to a background job are an identifier for an object in the database that the job will fetch from the database itself. This means no sensitive data would normally be registered.
However, we’ve seen more and more types of data being used for background job arguments that we’ve expanded support for parameter filtering to background jobs as well.
From now on we will automatically apply any filtering to the arguments of background job libraries. See our docs more information about how to use the parameter filtering.
In this release we’ve also fixed some smaller issues:
Appsignal.send_errornow have the same method arguments. PR #317