AppSignal now supports Solid Cache, giving you the same deep cache performance insights you'd get from other Rails cache stores. In this blog post, we'll give you a quick tour of Solid Cache, and how you can benefit from monitoring your app's cache with AppSignal.

CPU-bound tasks can grind your Node.js applications to a standstill, frustrating users and driving them away. You must master the art of profiling your application to pinpoint bottlenecks, and implement effective strategies to resolve any issues. In this guide, we'll explore various techniques to help you identify and fix the root causes of your Node.js performance issues. Let's get started!

At AppSignal, our pricing revolves around the number of requests we process for a customer and the number of buckets of logging data we store. After their free trial, customers are offered the most fitting plan for them based on their usage in the previous 30 days. About nine years ago, we noticed that many customers were slowly growing their number of requests, but we kept charging them for the plan they started on.

We've improved our core features to help you debug issues more efficiently and effectively. This article will walk you through the changes we've made to our Error Tracking, Performance Monitoring, Anomaly Detection, and Log Incidents features that enable you to gain the insights you need to dive deep into issues quicker than ever before.

In late 2012, we were getting somewhere with this unnamed side project that was supposed to replace our overpriced New Relic subscription. If we wanted to tell the world about it, it needed a name. This is a brief history of how we came up with the name, and how we landed appsignal.com. Besides being co-founder, I was also "the name guy” at 80beans, the consultancy where AppSignal was born; you know, the person that comes up with fun names and finds out the.com has been squatted.