AppSignal now offers Apollo Gateway support, giving you span-level gateway performance insights to enhance Apollo Gateway performance in your Node.js applications. In this blog post, we'll give you a whistle-stop tour of how to instrument and monitor Apollo Gateway requests in your Node.js application.

In the first part of this series, we toured performance APIs in Node.js. We discussed the capabilities of APIs and how they can diagnose slowdowns or network issues in your Node application. Now, in this concluding segment, we will embark on a practical journey, applying these performance hooks in a real-world scenario. You will understand how to effectively use these tools to monitor and enhance your application's performance. Let's dive in and see these concepts in action!

We have improved our custom metrics offering with two recent Python releases. In release 1.1.1 of our Python package, we added the add_distribution_value helper, and in version 1.2.0, we added support for minutely probes, so you can measure the distribution of key data points in your Python application. In this blog post, we'll show you how to set up custom metrics in your Python application to gain valuable insights without sifting through logs or querying databases.

When you first try a new library or framework, you are excited about it. However, as soon as you run something on production, things are less than ideal — an error here, an exception there - bugs everywhere! You start reading your logs, but you often lack context, like how often an error happens, in what line, etc. Fortunately, tools such as AppSignal can help. AppSignal helps you track your errors and gives you a lot of valuable insights.

We recently announced AppSignal Business Add-Ons, our alternative to pricy enterprise plans. The add-ons offered HIPAA BAA, Long-Term Log Storage, and Two-Factor Authentication Enforcement for an additional fee. However, after listening to feedback from our customers, we decided that Two-Factor Authentication Enforcement is a core feature that should be available to all organizations on all plans for free.

Introducing the alternative to expensive all-encompassing Enterprise Plans: AppSignal Business Add-ons. With our Business Add-Ons, you only need to pay for the features that matter to you, giving you the additional features your organization needs with the same freedom and flexibility all AppSignal customers enjoy. We currently have two Business Add-Ons on offer: In this blog post, we'll give you a whistle-stop tour of our new Business Add-Ons and explain how to add them to your organization's plan.

We're excited to announce AppSignal support for Vector logs and metrics! AppSignal's Vector support allows you to expand your monitoring horizons beyond our standard language integrations, making it possible to leverage AppSignal to both monitor the performance and manage the logs of components of your stack that fall outside a standard application. With Vector, you can use AppSignal to monitor how your databases and Kubernetes clusters perform and metrics from many other sources.

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.