Operations | Monitoring | ITSM | DevOps | Cloud

These days, using a tool such as Cursor, GitHub Copilot, Zed, or Claude makes it easier than ever to develop and deploy applications. You express your requirements, receive the completed project back as output, and there you have it! You now have an application that is in production and functioning. However, the surprise comes after the app has been deployed. When your app breaks or behaves abnormally, it may not be immediately obvious what is wrong or how to fix it.

Prometheus and Grafana are the default monitoring recommendations across DevOps blogs, Reddit, and Hacker News, and for good reason. Prometheus is open-source and backed by the CNCF, but it’s not actually a complete monitoring system. It’s more of a metric collection engine.

Your AI coding assistant already knows your codebase. Now it can know your production environment too. AppSignal's MCP server gives AI agents and AI code editors direct access to your monitoring data — errors, performance metrics, and more — so they can help you debug, investigate and resolve issues without switching context. And with our new public endpoint, getting started is simpler than ever.

The Node.js service has just been containerized and deployed with a single fly deploy command across continents. Everything seems to be alright, but then a week later, a user messages you saying the app is slow. You run the fly logs command and scroll through some logs, and find nothing out of the ordinary. The Fly.io dashboard says the app is running and healthy, but something behind the scenes is slowing down the app, and you have no idea what. You don’t even know where to start.

Angular's Signal-based reactivity model represents one of the biggest paradigm shifts the framework has seen since Ivy. By replacing the asynchronous push-pull model of RxJS with synchronous, localized updates, Signals make state management both simpler and faster. But this new simplicity hides a subtle danger: when something breaks inside your reactive graph, it often does so silently. A computed value might stop updating. An effect might fire indefinitely.

With all the discussion in the dev community lately about changes made at Heroku, we wanted to use this moment to talk about PaaS (Platform as a Service) providers and how AppSignal can be a vital tool to ensure you're using your app's hosts for everything from optimal performance to lower usage bills.

Want your log queries to be more precise? Is your vibe code flooding you with logs and need a helping hand to make sense of it all? Good news! We've upgraded our log query language to be more powerful, flexible, and intuitive, letting you focus on finding answers fast rather than endlessly scrolling through your logs. And that's not all: We've revamped our logging interface, making it easier than ever to manage logs, customize views, and leverage log attributes.

As your application scales to serve hundreds, thousands, or even millions of users, understanding its performance becomes essential. Performance monitoring helps you make informed decisions based on data instead of guesswork or user complaints. Imagine users reporting that your app feels"slow". Without proper instrumentation and monitoring, you're left troubleshooting blindly.

Over the last couple of years, we've witnessed a remarkable shift in the JavaScript ecosystem, as many popular developer tools have been rewritten in systems programming languages like Rust, Go, and Zig. This transition has delivered dramatic performance improvements and other innovations that are reshaping how developers build JavaScript-backed applications.

Erlang's Observer is often discussed in passing and regarded as a curiosity during Elixir courses. However, Observer provides many powerful tools for monitoring and debugging your application, both in development and production. Together, we will learn how to access the Observer GUI and debug a project that leaks memory, both locally and through a remote node. We will set up process tracing and track garbage collections to find the offending code in our sample project. Let's get started!