appsignal-elixir changelog

Changelog History

Page 1

• v2.2.13 Changes

  🛠 Fixed

  • 🚦 26be6e58 patch - Fix session data by reverting the sample data key change

• v2.2.12 Changes

  ➕ Added

  • 65c5d716 patch - Don't set session data when the send_session_data configuration is set to false

• v2.2.11 Changes

  ➕ Added

  • 🚦 e287e58c patch - Allow ignoring specific pids through Tracer.ignore/1
  • 🚦 c325114a patch - Log messages are now sent through a centralised logger, defaulting to logging to the /tmp/appsignal.log file. To log to standard output instead, set the log config property to "stdout".
  • 🚦 96c60363 patch - Don't set parameters when the send_params configuration is set to false

  🔄 Changed

  • bb6c7a65 patch - Add the config "override" source to better communicate and help debug when certain config options are set. This is used by the diagnose report. The override source is used to set the new config option value when a config option has been renamed, like send_session_data.
  • 🚦 003a2edd patch - The extension installation will no longer fail when the CA certificate file is not accessible.

  • 🚦 db97b2f6 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 values

  • 🚦 709224ad patch - Bump agent to v-f57e6cb

    • Enable process metrics on Heroku and Dokku

• v2.2.10 Changes

  ➕ Added

  • 0469f4b2 patch - Add send_session_data option to configure if session data is automatically included in spans. By default this is turned on. It can be disabled by configuring send_session_data to false.

  🔄 Changed

  • 🚦 ffe65216 patch - Remove Ruby exclusive headers from request_headers defaults.
  • 🚦 c0a98928 patch - Bump AppSignal agent version to 15ee07b. Add internal tracking of transmission duration.
  • 🚦 8c14f827 patch - The diagnose library report now reports the agent version from the committed agent file, rather than the downloaded version, which is reported in the installation report.

  🗄 Deprecated

  • 0469f4b2 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.

  🛠 Fixed

  • 🗄 e4ec8e68 patch - Prefer the value of the log_level config option, instead of the deprecated debug config option, when deciding whether to log a debug message. If log_level does not have a value, or its value is invalid, the values of the deprecated debug and transaction_debug_mode config options are taken into account.

• v2.2.9 Changes

  🛠 Fixed

  • 2b78e1e2 patch - Fix debug and transaction_debug_mode log options. If set, previously the log_level would remain "info", since version 2.2.8.

• v2.2.8 Changes

  ➕ Added

  • 🚦 4a9bcca3 patch - Add "log_level" config option. This new option allows you to select the type of messages AppSignal's logger 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
    • 10078177 patch - Add send_environment_metadata config option to configure the environment metadata collection. For more information, see our environment metadata docs.
    • ⏱ 10078177 patch - Add the Erlang scheduler utilization to the metrics reported by the minutely probes. The metric is reported as a percentage value with the name erlang_scheduler_utilization, with the tag type set to "normal" and the tag id set to the ID of the scheduler in the Erlang VM.

  🔄 Changed

  • 🚦 10078177 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.

  • 🚦 10078177 patch - Remove the valid key from the diagnose output. It's not a configuration option that can be configured, but an internal state check if the configuration was considered valid.

  • 🚦 10078177 patch - Print the extension installation dependencies and flags in the diagnose report output.

  • 🚦 10078177 patch - Standardize diagnose validation failure message. Explain the diagnose request failed and why.

  • 🚦 f3bb8546 patch - Bump agent to v-0db01c2

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

  🗄 Deprecated

  • 4a9bcca3 patch - Deprecate "debug" and "transaction_debug_mode" config options in favor of the new "log_level" config option.

  ✂ Removed

  • 🚦 f40ead99 patch - Remove the unused allocation tracking config option.

  🛠 Fixed

  • 🚦 10078177 patch - Fix a bug where setting the :phoenix, :filter_parameters configuration key to an allow-list of the form {:keep, [keys]} would apply this filtering to all sample data maps. The filtering is now only applied to the params sample data map.
  • 🚦 10078177 patch - Fix the Push API key validator request query params encoding.
  • 🚦 10078177 patch - When the Push API key config option value is an empty string, or a string with only whitespace characters, it is not considered valid anymore.
  • 🚦 10078177 patch - Transmit the path file modes in the diagnose report as an octal number. Previously it send values like 33188 and now it transmits 100644, which is a bit more human readable.
  • 10078177 patch - Improve parameter and session data filtering options. Previously all filtering was done with one combined denylist of parameters and session data. Now filter_parameters only applies to parameters, and filter_session_data only applies to session data.
  • 🚦 10078177 patch - Fix the download of the agent during installation when Erlang is using an OpenSSL version that does not support TLS 1.3, such as versions below OpenSSL 1.1.1.
  • 🐎 ad0b00f1 patch - Suppress a warning emitted by Telemetry 1.0.0, regarding the performance penalty of using local functions as event handlers, by specifying the module of the captured function.

• v2.2.7 Changes

  • 🚦 f07f9cf9 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.

• v2.2.6 Changes

  • 🚦 acb7295 patch - Print String values in the diagnose report surrounded by quotes, and booleans as "true" and "false", rather than "yes" and "no". Makes it more clear that it's a value and not a label we print.
  • 🚦 e71792f patch - Fix diagnose output rendering an additional empty line for the appsignal.log file. It appeared that only 9 lines were printed instead of the 10 expected lines.
  • 🚦 422cbd1 patch - Render the install report errors in the diagnose CLI output fewer times. A missing download and/or install report could sometimes be displayed up to two times, in total four errors.
  • 🚀 f7c0b1e patch - Support mix task diagnose arguments. When an app is released with mix release CLI arguments cannot normally be passed to the diagnose task. Use the eval command pass along the CLI arguments as function arguments.

    mix format
    # Without arguments
    bin/your_app eval ':appsignal_tasks.diagnose()'
    # With arguments
    bin/your_app eval ':appsignal_tasks.diagnose(["--send-report"])'
  

  • ⚡️ c51c065 patch - Update diagnose output labels to be similar to our other language integrations.
  • 🚦 9d3e253 patch - Add new config option to enable/disable StatsD server in the AppSignal agent. This new config option is called enable_statsd and is set to false by default. If set to true, the AppSignal agent will start a StatsD server on port 8125 on the host.

• v2.2.5 Changes

  • ⚡️ e7d676a9 patch - Update SSL configuration for OTP 23 and newer to fix the Cloudfront mirror download during installation.
  • 🚦 7ccf75ce patch - Fix install result message to no longer show a success message when an installation failure occurred.

• v2.2.4 Changes

  • 🚦 787684bf patch - Installation report improved for download errors. Download errors are more descriptive in the installation result of the diagnose report.

• 1
• 2
• 3
• 4
• 5
• Next ›
• Last »