Logs are an important part of your application and logging shouldn’t be one of the last things you think of. You should configure your log system, formatter, and style as soon as you start the development of your app. Also, do your best to document the process and share how it works with the rest of your team. In this article, we’re going to demonstrate how logs work in Elixir. We’ll jump into Elixir’s Logger module, which brings a lot of power to logging features.

Do you know how many errors your Node.js application had last week? How many users were affected? Which servers were high on CPU/Memory/Disk? If you do know, how many different tools did you have to install, and how many hours you’ve spent configuring all those tools? AppSignal is here to change the way you monitor your apps and simplify your life as a developer. Today, we officially launch the 1.0 version of @appsignal/node.js.

Have you ever heard of Node.js async hooks module? If the answer is no, then you should get familiar with it. Even though it’s new stuff (released along with Node.js 9) and the module is still in experimental mode, which means it’s not recommended for production, you should still get to know it a bit better. In short, Node.js async hooks, more specifically the async_hooks module, provides a clear and easy-to-use API to track async resources in Node.js.

Application monitoring alone is not always enough to get the full picture of your systems. Frequently, services running in satellite apps (or supporting apps) can have an acute impact on your day-to-day operations. Database servers are well-known examples of this. Backup scripts and other background jobs can also slow systems and are often overlooked. AppSignal does not watch these satellite processes by default.

Setting up AppSignal isn’t as complex as rocket science. Developer experience is really important to us, as AppSignal started as a way to scratch our itch. We also put a lot of effort in providing you with a first-class developer support. In fact, our developers are the ones answering all of your your technical questions. This is why we’ve added a diagnose tool to our Node.js integration.

If you’ve ever used Ruby on Rails, you’ve probably come across the concept of concerns. Whenever you jumpstart a new Rails project, you get a directory app/controllers/concerns and app/models/concerns. But what are concerns? And why do people from the Rails community sometimes talk badly about them?

AppSignal now supports the next API version of PagerDuty. 🎉 One of our devs was on support rotation the other day, and a customer asked whether we could add support for the next API version of PagerDuty. We won’t tell you who it was, but this developer typically answers questions by solving things as quickly as he can. So, two days later, boom! The improved integration for Pagerduty went live.

In an ideal world where we reached 100% test coverage, our error handling was flawless, and all our failures were handled gracefully — in a world where all our systems reached perfection, we wouldn’t be having this discussion. Yet, here we are. Earth, 2020. By the time you read this sentence, somebody’s server failed in production. A moment of silence for the processes we lost.

For many freelancers and small business owners, moving from consulting or freelance development work to operating a SaaS product is the Holy Grail. That makes sense: running a SaaS scales better and makes for a stable income. While there’s no guaranteed path to success, here’s what we learned taking AppSignal from a “20% time side-project” to a business serving thousands of developers around the globe. This article isn’t a blueprint.

In this article, I’ll try to guide you through some examples and definitions that aim to clarify the Web Vitals landscape from a Next.js perspective. Let’s dive in!