Operations | Monitoring | ITSM | DevOps | Cloud

Imagine stepping into the role of a DevOps engineer at an online learning company that utilizes Open edX as its core Learning Management System (LMS). As the platform scales to accommodate more learners, a myriad of challenges begin to surface: These are just the tip of the iceberg. It's pivotal that you provide timely reports on site performance and error tracking in real time, and fix any issues before they affect a significant user base.

We're excited to introduce Check-ins, our no-fuss solution to monitoring your scheduled jobs and continuous processes. AppSignal Check-ins allow you to seamlessly monitor the scheduling, run times, and health of your scheduled jobs and processes, with a simple setup using helpers or API endpoints. In this post, we'll introduce you to the new Check-ins feature and show you how to start monitoring your app's background processes with AppSignal.

For Phoenix developers, maintaining the health of your applications is critical. AppSignal offers a powerful solution to gain deep insights into your application's performance and stability. In this introductory guide, we'll walk through the process of setting up AppSignal in your Phoenix app, instrumenting your code for detailed monitoring, handling errors effectively, and utilizing AppSignal's features to maintain and improve your application's performance.

We've released version 4.0 of the AppSignal gem, which offers significant changes and improvements to our Ruby integration. In this blog post, we'll cover the core updates and explain the steps you need to take before you upgrade.

In the first part of this series, we saw that even if you just use AppSignal’s default application monitoring, you can get a lot of information about how your Phoenix application is running. Even so, there are many ways in which a Phoenix application may exhibit performance issues, such as slow database queries, poorly engineered LiveView components, views that are too heavy, or non-optimized assets.

When we observe a slow system, our first instinct might be to label it as failing. This presumption is widespread and highlights a fundamental truth: performance is synonymous with an application's maturity and readiness for production. In web applications, where milliseconds can determine the success or failure of a user interaction, the stakes are incredibly high. Performance is not just a technical benchmark, but a cornerstone of user satisfaction and operational efficiency.

Most of the time, the default application monitoring metrics, graphs, and visualizations provided by AppSignal will do for your Ruby app. However, you might be the kind of user who likes a bit of control over what is measured, how it’s displayed, and how critical information about your app should be relayed. AppSignal allows you to customize app metrics and dashboards as you wish. In this guide, we’ll learn all about AppSignal's custom metrics, including: And more!

AppSignal's Node.js package now supports monitoring BullMQ jobs. In this article, we'll demonstrate how easy it is to start monitoring BullMQ performance and what insights you can expect to see for your BullMQ jobs in AppSignal.

While building an app with FastAPI can be reasonably straightforward, deploying and operating it might be more challenging. The whole user experience can be ruined by unexpected errors, slow responses, or even worse — downtime. AppSignal is a great tool of choice for efficiently tracking your FastAPI app's performance. It allows you to easily monitor average/95th percentile/90th percentile response times, error rates, throughput, and much more. Useful charts are available out of the box.

AppSignal is a powerful error tracking and performance monitoring tool that can help you maintain reliability and speed in your Elixir applications. In this tutorial, the first of a two-part series, you'll learn how to integrate AppSignal into your Elixir application, configure it for error tracking, interpret error reports, and leverage AppSignal's features to debug and resolve issues.