We're launching our new Getting Started page. This feature helps first-time users to set up their monitoring with AppSignal, as soon as they've signed up. Before we dive in, we'd love to share our beliefs about onboarding. All developers share these same “first-time” moments: Many of our customers start monitoring their applications for the first time with AppSignal, or experience new types of issues when scaling an application.

We've simultaneously launched 4 new integrations for Node.js: Redis, ioredis, MySQL, and MySQL2. This means that you can now see all the details of a query in the Event Timeline and Slow Query screens in AppSignal. Because we are a small and bootstrapped team, we've chosen to embrace OpenTelemetry as a means of expanding AppSignal's offering in the Node.js ecosystem.

We've launched a feature that will help you fix errors and performance issues as a team! 🎉 With Logbook you get the full incident history. Read and leave team comments, see which notifications were sent at what time, and see team activity for changes in incident states. It's now easier than ever to see what the current state of an incident is.

Before today, we would send an email for every Performance or Exception incident if a notification rule was triggered. This meant that if you deployed a new version of your app and your incident notification settings were set to "first in deploy", you'd get two emails if two errors occurred.

Process management refers to various activities around the creation, termination, and monitoring of processes. A process manager is a program that ensures that your applications always stay online after being launched. Process managers can prevent downtime in production by automatically restarting your application after a crash or even after the host machine reboots. They are also useful in development: they auto-restart an app once its source files or dependencies are updated.

We're happy to announce that we've added a feature that will enable you to create folders for your custom metric dashboards.

During the last few months, we've been working hard on improving our Node.js integration. We've released loads of quality fixes and improvements to our diagnose command, configuration, and general package structure. Today, we'd like to highlight some of the enhancements and fixes that we've recently released.

In the first of this two-part series, we covered how to set up AppSignal in a Ruby on Rails application for many great insights out of the box. AppSignal can automatically track errors, monitor performance, and report metrics about some dependencies. But, in many cases, each of our applications behaves in different ways, so we'll want more than just generic monitoring. In this post, we will run through adding custom instrumentation and monitoring to a Ruby on Rails application.

You can now share any graph from AppSignal with your team, company, and the world. Click the export icon in the graph header to create a hosted image that you can link, embed, or download for further annotation. Developers often share performance screenshots with each other. Some screenshots end up on Twitter where developers explain how they improved their application’s performance with AppSignal. We regularly take screenshots of our graphs as well.

When it comes to monitoring your Elixir application, it's challenging to make sense of the many metrics and statistics that you can read from the internals of the Erlang virtual machine. In this post, we'll be looking at the scheduler utilization metric in order to understand what it is, why we should monitor it, and how to monitor it.