Added

• Add HTTPoison instrumentation. HTTP requests made with HTTPoison will appear as request.httpoison events on your performance samples' event timeline.

  HTTPoison does not emit telemetry events, so the instrumentation is opt-in. Use Appsignal.HTTPoison in place of HTTPoison when making requests, or replace use HTTPoison.Base with use Appsignal.HTTPoison.Base for custom client modules. Response types (%HTTPoison.Response{}, %HTTPoison.Error{}, etc.) are unchanged.

Changed

• Bundled certificates have been updated.

View the Elixir package v2.17.0 changelog for more information.

Changed

• Disable the error backend by default

  With new ways of instrumenting errors added, the error backend is unneeded in most setups. Disable it by default to make it opt-in.

View the Elixir package v2.16.0 changelog for more information.

Fixed

• Fix issue when running AppSignal for Phoenix in CI. When the CI environment variable was present, AppSignal for Phoenix would break during installation unless a separate environment variable was also present.

View the Elixir for Phoenix package v2.8.1 changelog for more information.

Added

• Report LiveComponent traces and events separately from LiveView traces and events.

  Traces in AppSignal representing updates and event handlers in components will no longer be represented as calls to the view in which the component is mounted, and their events will be part of the live_component group.

  This makes it possible to obtain performance measurements for each component individually, instead of grouped by the view that mounts the component.

• Group samples for calls to handle_event/3 in LiveView and LiveComponent by the event that is being handled.

View the Elixir for Phoenix package v2.8.0 changelog for more information.

Added

• Add support for Oban timeout exceptions

Changed

• Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt or plaintext formats. No further config needed when calling our logger, like so:

  Elixir

  Appsignal.Logger.info("group", "message")

View the Elixir package v2.15.11 changelog for more information.

Fixed

• Fix compatibility with Phoenix 1.8's parameter filtering compiled patterns. This will errors on boot about the AppSignal handlers not attaching.

View the Elixir package v2.15.10 changelog for more information.

Changed

• Allow for more customization of trace namespaces during the trace's lifetime. Previously, it was not possible to customize the namespace of Absinthe traces before the Absinthe instrumentation had run. This is now possible, as the Absinthe instrumentation will only set the namespace if it has not been set already.

View the Elixir package v2.15.9 changelog for more information.

Added

• Add nginx_port configuration option. This configuration option can be used to customize the port on which the AppSignal integration exposes the NGINX metrics server.

View the Elixir package v2.15.8 changelog for more information.

Changed

• Update the result attribute reported for Oban jobs. Instead of it including the job's whole return value, it only contains the Oban job control value: :ok/:error/:discard/:cancel/:snooze. The reason for a discard, cancel, error or snooze result will be stored in the new result_reason attribute. Any :ok result reasons and unexpected result values are ignored. This is to avoid storing sensitive data in the attributes and to make it easier to filter by job control value in the interface.

View the Elixir package v2.15.7 changelog for more information.

Changed

• Log a debug message when the reported error is ignored by the ignore_errors config option.

View the Elixir package v2.15.6 changelog for more information.

Fixed

• Restore normal error reporting behavior by removing the default included Plug.ErrorHandler in the Appsignal.Plug module. It will now longer render a page with HTTP status 500 and the response body "Something went wrong".

View the Elixir for Plug package v2.1.1 changelog for more information.

Added

• Report Oban's configuration prefix value, if present, as a tag in Oban job samples. Thanks to @tfwright for suggesting and implementing this feature.

Changed

• Remove redundant cron check-in pairs. When more than one pair of start and finish cron check-in events is reported for the same identifier in the same period, only one of them will be reported to AppSignal.

View the Elixir package v2.15.5 changelog for more information.

Added

• Allow keyword list configurations

View the Elixir package v2.15.4 changelog for more information.

Changed

• Remove the Hackney dependency. It is no longer used since AppSignal package 2.15.0.

Fixed

• Update appsignal_plug dependency requirement. This fixes an issue with spans being closed double, which led to inaccurate reporting.

View the Elixir for Phoenix package v2.7.0 changelog for more information.

Changed

• Remove Hackney dependency. The integration now uses Finch instead.

Fixed

• Ensure spans in requests with errors aren't double-closed

View the Elixir for Plug package v2.1.0 changelog for more information.

Added

• Add a mix task to check the extension install.

  Run mix appsignal.check_install to see if the NIF and agent were successfully installed. If not, it will return with exit code 1. Use this in your CI or build step to check if AppSignal was installed correctly before deploying or starting your application.

Fixed

• Fix an issue where the check-in scheduler would crash when failing to send a check-in due to a network error.

View the Elixir package v2.15.3 changelog for more information.

Fixed

• Fix an issue where the check-in scheduler crashes upon use.

View the Elixir package v2.15.2 changelog for more information.

Changed

• Switch Hackney to Finch as the bundled HTTP client to operate within the integration

View the Elixir package v2.15.0 changelog for more information.

Changed

• Improve SQL sanitisation for functions and numbered placeholders.

View the Elixir package v2.15.1 changelog for more information.

Changed

• Delay and eventually halt agent reboots by the extension.

  The AppSignal extension is responsible for booting the AppSignal agent. If communication with the agent is lost, the extension is responsible for rebooting it.

  In certain scenarios, such as when several processes with different AppSignal configurations are misconfigured to share the same working directory, the processes' extensions can enter a loop of rebooting and killing each others' agents. These short-lived agents may then attempt to repeatedly send pending payloads to AppSignal in quick succession.

  This change causes the extension to delay each reboot of its agent by one additional second, and to no longer attempt to reboot the agent after the tenth reboot, slowing down and eventually breaking this loop.

View the Elixir package v2.14.1 changelog for more information.