A true alchemist is never done exploring. And neither are we. Sign up for our Elixir Alchemy email series and receive deep insights about Elixir, Phoenix and other developments.
After releasing version 1.0 of our Elixir Integration last month, we’re excited to announce version 1.1, which was released today.
We’ve always had full stack traces for all of our errors so you can easily find bugs in your code, but we’re now linking error samples that happened in Phoenix controllers to their actions in AppSignal.
From now on, you can see which errors occured and what the error rate is per controller action in the controllers tab. Also, we’re now creating performance samples for actions, even when they’ve triggered an error.
In previous versions, we had a issue with updating the configuration, which caused problems with hot reloading apps. The AppSignal package writes its configuration to the system environment so our agent can configure itself using the same config. The system environment values are leading, however, and this created a problem when loading in an updated configuration. The new AppSignal config was always ignored.
To fix this, we now keep two copies of the configuration; one is owned by the agent, and the other is owned by the integration. Because the integration configuration is always leading, we’re now properly reloading the configuration after reloading the integration.
We’ve updated the installer to properly work with Elixir projects that don’t have environment-based configuration files, so you can now use the installer for plain Elixir projects without Phoenix.
The (optional) dependency on Phoenix has been loosened to
=> 1.2.0, so we’ll
immediately support 1.3.0 when it comes out. In the meantime, we’ve set up a
branch that depends on
~> 1.3.0-rc.0 and is based on master, so
you can try AppSignal if you’re running any of the Phoenix release candidates.