Amsterdam, Netherlands
2013
  |  By Dejan Lukić
There’s no scenario in which you should be required to run six monitoring tools at once. OK, I may have been a bit dramatic there, you might actually be at a scale where you need it. But for the rest of us, it’s certainly overkill. Using UptimeRobot for, “Is the site up?”, Papertrail for logs, PagerDuty so someone actually gets notified… Tons of logins, tons of invoices, tons of separate configs, and the worst thing is, they are all unaware of each other.
  |  By Dejan Lukić
MCP is generating a lot of hype nowadays (but then again, almost anything that emerges in AI seems to attract hype). The anticipation around it is similar to the level of excitement that would break out if Apple were to finally introduce USB-C to iPhones. To be fair, though, some of that hype is warranted, considering the fact that MCP provides a standardized approach to connecting agents with third-party tools, which significantly simplifies this type of integration (hence the USB-C analogy).
  |  By Dejan Lukić
Vibe coding made building software feel almost too accessible. You describe what you want, an AI assistant scaffolds it, and a few hours later, something is running. So, it was only a matter of time before developers started asking the obvious question: why should I pay for a monitoring tool when I can just build my own? In all fairness, the DIY instinct is a healthy one. But monitoring is one of the last corners you’d want to cut.
  |  By Dejan Lukić
An incident has hit your product. I've been there: you're context-switching between hosting, CI/CD, codebase, AppSignal for monitoring, and whatever else your product depends on to minimize downtime and potential losses. You're trying to piece everything together, but it takes a lot of time, and that's something you don't have. AI agents connected to your tooling and your monitoring data via MCP free up that time for you.
  |  By Tarun Singh
Migrating your app to a new service can be scary. Render makes the deployment side easy, but a green deploy doesn’t mean everything is working. Silent failures are often the most dangerous kind. They go unnoticed until a customer calls to report a broken webhook or you realize the queue depth has been climbing since the cutover and nobody has caught it yet. The migrations that explode on deploy are not the ones you should fear. It’s those that look fine for three days.
  |  By Dejan Lukić
Python is the native language of AI-assisted development. Models are really good at writing it, and a lot of people are now shipping it without ever having written much Python themselves. The whole thing is really simple. You prompt an app, Claude Code or Cursor produces a working Flask or FastAPI backend, and you’re live in a few hours. However, there’s still a big difference between “it works on my machine” and “it works in production”.
  |  By Karen Patteri de Souza
At AppSignal, we love talking to our customers to learn how they're using the product. Recently, one of them showed us something worth sharing: with a single chat prompt, his AI agent searches production logs, closes incidents, and checks whether a pull request has shipped. Automating that kind of work turned out to be a matter of building the right agent skill.
  |  By Dejan Lukić
Cursor, Claude, and their fellow tools are great when they are speaking code, but once that code hits production, they are not exactly native. However, if your code is monitored by AppSignal, an MCP server can bridge that gap and allow agents to poke around the production.
  |  By Connor James
That's a wrap on Launch Week 2026. In case you missed a day, or you want the short version, here is everything we shipped.
  |  By Muhammed Ali
As developers, we sometimes find ourselves in situations where something feels slower than it should be. The first thing we tell ourselves is “Maybe I need a different tool.” And sure, at times, it might be due to the tool, I’ll give you that. But most of the time, it comes down to how you’ve implemented certain features. That’s one of the downsides that comes with having too much freedom.
  |  By AppSignal
In this video, we give a whistle-stop tour of some of AppSignal's key features to help get you started.
  |  By AppSignal
He covers installation and setup, how to troubleshoot and fix performance issues, specifically showing a common use-case with N+1 queries. He then shows AppSignal's Sidekiq integration along with its magic dashboard, managing and reporting anomalies, custom instrumentation, and how to handle error reporting.. Here's the timeline.

Made for teams that want to build high quality Ruby and Elixir applications, AppSignal offers amazing insights into errors and performance issues, plus host monitoring and an easy to use custom metrics platform.

AppSignal supports the Elixir language with an Elixir package. The package supports pure Elixir applications and frameworks including Phoenix, Plug & Erlang.

AppSignal supports the Ruby language with a Ruby gem. The gem supports many frameworks and gems including Capistrano, DataMapper, Delayed Job, Grape, MongoDB, Padrino, Rack, Rake, Resque, Ruby on Rails, Sequel, Shoryuken, Sidekiq, Sinatra & Webmachine.

AppSignal now supports Node.js! The package supports pure JavaScript applications and TypeScript applications, and can auto-instrument various frameworks and packages with optional plugins.

AppSignal also has amazing support for catching errors from Front-end JavaScript applications and sending them to AppSignal, including the React, Vue, Angular, Ember, Preact & Stimulus frameworks.

Packed with features:

  • Alerts in your tools: AppSignal integrates with Slack, Flowdock, HipChat, OpsGenie and more.
  • Control your notifications: AppSignal notifies you exactly when you want to. Get the first exceptions per deploy, all of them of never. Set thresholds for performance notifications.
  • Amazing support: We don't do "first line" and "second line" support: you get to speak with a developer, immediately.
  • Send to issue trackers: A single click creates an issue with all the necessary details in your issue tracker of choice.
  • Manage teams and users: Add users to teams and give them access to specific or all, existing and/or new applications you monitor.
  • Focus on design: Developer tools do not need to be complicated and ugly. Our interface is kept clean and easy to use.

Catch errors, track performance, monitor hosts, detect anomalies — all in one tool.