We just released AppSignal for Ruby gem version 2.7.0 which allows for longer tag values to be sent, supports more precise values for custom metrics and adds the
working_directory_path option to replace
Previously the tag limit was set to 100 characters. This proved too short for some cases. Values were dropped if they had a length longer than 100 characters to keep samples from becoming too large.
Now, tags for AppSignal transactions (web requests, background jobs, etc.) have a new 256 maximum value limit. Tags aren't dropped if they exceed the value limit, but they're truncated to 265 characters if needed.
Appsignal.tag_request(:tag => "value") Appsignal.tag_job(:tag => "value")
Doubles for custom metrics
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 Ruby gem 2.7 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.
# config/appsignal.yml production: 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.
- Detect Kubernetes machines as containers for
running_in_containerconfig option. No more need to configure this manually for Kubernetes machines 🎉