We have been collecting Logplex data for our Heroku customers for a while now. With that data we create Magic Dashboards for Postgres and Redis integrations, and track Heroku Host Metrics. Starting today, we also extract error incidents from Heroku Logplex data and provide you with a magic dashboard for Heroku status codes.
Measuring and offsetting your carbon footprint may seem like a daunting task. In this post, we’ll explain how to easily and quickly perform the calculations in a DIY style. Let’s go!
Linting is the process of statically analyzing code in search of potential problems. What constitutes a problem, in this case, can vary across programming languages, or even across projects within the same language. I would put these problems under a few different categories: Let’s take a look at a few examples of each.
It’s easy to get lost with dozens of plugins and frameworks when starting a new project that requires basic authentication and authorization capabilities. It doesn’t have to be that way. In this article, we’re going to explore two valuable Node.js packages — Passport and CASL — that can help you boost the security of your application by providing both authentication and authorization functionality.
Koabamm! We now monitor Koa. This Node.js framework enables you to use cascading middleware, which can now also be shown in AppSignal. Let’s dive right in!
Today, we launch a new feature: sending metrics and errors to AppSignal over our “Public Endpoint” API. AppSignal has many web frameworks, databases and background job frameworks automatically instrumented when you want to monitor a Node.js, Ruby or Elixir app. If you have code running on serverless architecture such as AWS Lambda, you can’t run our agent, so our standard integration with all of the out-of-the-box magic won’t work.
In today’s post, we’ll dive into how we, at AppSignal, solved a daunting engineering challenge. Giving you a look into the kitchen, this post will show you how we tested a new database in production without having to worry about errors/downtime. Alright, let’s get cooking!
Setting up a proper monitoring overview over your application’s performance is a complex task. Normally, you’d first need to figure out what you need to monitor, then instrument your code, and finally make sense of all the data that has been emitted. However, with a few things set in place, and an APM that natively supports Ruby, it’s easier than ever to take this step. In this post, we’ll show you how you can do it too.
Regardless of the tech stack used, many developers have already used Redis or, at least, heard of it. Redis is specifically known for providing distributed caching mechanisms for cluster-based applications. While this is true, it’s not its only purpose. Redis is a powerful and versatile in-memory database. Powerful because it is incredibly super fast. Versatile because it can handle caching, database-like features, session management, real-time analytics, event streaming, etc.
Your wishes are being granted. Search is now available for all AppSignal customers. 🎉 You can now quickly find specific samples inside of AppSignal. This is especially useful when searching for an error/slow request for a particular customer in a specific revision or request ID. You can access the search in AppSignal from any screen in an application. It’s located in the dark top bar. Let’s take a look at the new search in action.
