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.
We’ve just released version 1.8 of the AppSignal for Elixir integration, which adds support for more precise values for custom metrics and adds the
working_directory_path option to replace
Custom metrics always supported integers as values for the
count metric. This allowed you to increment the counter with whole numbers, but not fractions. In Elixir package 1.8 you can increment the counter by
0.30, etc. Add that extra bit of precision to your counters!
In this release we’ve reworked the option that configures where the AppSignal working directory is located. (Read about what the working directory is used for in our docs.)
There already was the
working_dir_path option, but it’s behavior wasn’t completely self explanatory. For one, it appended
/appsignal to the path.
1 2 3 4 5
# config/appsignal.exs config :appsignal, :config, working_dir_path: "/tmp/my_app/" # would become working_dir_path: "/tmp/my_app/appsignal"
working_directory_path will not append the path to the user specified path. It will create the specified path if it does not exist yet.
You can switch to the
working_directory_path option without any additional configuration. Do note the
/appsignal sub directory will no longer be created.
In this release we’ve also immediatly deprecated the
working_dir_path option. Please use
It’s also possible configure the
working_directory_path option with an environment variable.
running_in_containerconfig option. No more need to configure this manually for Kubernetes machines 🎉