So cool that we can use Rust's tracing to get data into AppSignal now.
We were already monitoring it with metrics/logs, but having traces is always a plus.
#opentelemetry #dogfood #appsignal #rust #axum
Changes in the upcoming #Phoenix 1.7 release have led us to rethink how #AppSignal for Phoenix works. AppSignal for Phoenix version 2.2.0 introduces our changes to make upgrading to Phoenix 1.7 easier.
We're trying out a thing at #appsignal :appsignal: : our own Mastodon instance.
We're hoping that people who follow/used to follow us on Twitter and are leaving will follow @appsignal to keep up with the #ruby, #elixir, and #nodejs articles we publish at https://blog.appsignal.com/
So far, I have zero clues whether company accounts work on Mastodon. Trying this on our own instance seemed like the least-spammy method (requires a follow, won't show up on any instance's local timeline). Thoughts?
#appsignal #ruby #elixir #nodejs
We're trying out a thing at #appsignal :appsignal: : our own Mastodon instance.
We're hoping that people who follow/used to follow us on Twitter and are leaving will follow @appsignal to keep up with the #ruby, #elixir, and #nodejs articles we publish at https://blog.appsignal.com/
So far, I have zero clues whether company accounts work on Mastodon. Trying this on our own instance seemed like the least-spammy method (requires a follow, won't show up on any instance's local timeline). Thoughts?
#appsignal #ruby #elixir #nodejs
For those into numbers: #appsignal runs on ~40 dedicated servers and ~10 VPSs for our production env, and another 25 VPSs for staging, spread out across five locations in the Netherlands.
A boring #techstack is a happy techstack.
We run #AppSignal on dedicated servers and use #ansible to manage the infra.
No cloud, no containers, no magic, no noisy neighbours.
Full control (and responsibility!) for everything means when something is up, we fix it ourselves and are not number 20201 in the support queue of $cloud provider.
#techstack #appsignal #ansible