We are excited to share the release of our new Cost Calculator to showcase just how much the wrong APM provider can add to your cloud hosting costs (try it now). Observability is vital, but it comes with computational overhead that shares the same infrastructure as your application. This is compounded in typical Node.js APM tooling due to the internal workings of Node.js itself.

Nearly a year ago, we launched N|Solid SaaS, and although there are still a few months to go before our anniversary, we wanted to share the top 10 features ofN|Solid that make us proud every day of what we have built.

N|Solid provides unparalleled performance and security monitoring for various deployments and team sizes. You can configure the N|Solid Console to notify you when new vulnerabilities are found in your applications. DevOps professionals looking after applications running in production can be notified of performance and security issues earlier and then collaborate wherever they want (Slack, Microsoft Teams, email, etc.) to resolve them.

One of the first needs of developers is debugging memory-based issues in Node.js applications quickly and effectively. Still, before we jump right into the Heap Snapshot concept, it's essential to understand what a memory leak is. A basic definition that I would apply in this context is: Memory leaks are quite common in production applications. Fortunately, they usually aren't difficult to find.

One of the more popular ways for developers to use Node.js is to leverage Worker Threads. Workers (threads) are useful for performing CPU-intensive JavaScript operations, according to the official documentation. They have proven to be the best solution for CPU performance due to the following features.

The role of app performance monitoring (APM) extends far beyond crash monitoring—it is an integral part of creating a top-notch user experience that keeps your users happy and coming back for more.

TL; DR: Based on the APM benchmarks results is evident that one of the main performance problems for a Node.js application in a production environment is the usage of the very same applications in charge of monitoring the performance for the application itself. This article explains the reasons with an in-depth analysis to show why using most APMs in a Node.js application is that expensive performance-wise.

In today’s times, Application Performance Monitoring has grown to become a necessity for most software organizations. At the same time, the term has evolved from tracking only the performance of an application to monitoring the infrastructure, user experience, latency, and much more. These factors, when put together, contribute to the overall growth of a product. There are so many things that can go wrong at the same time.

If you are trying to compare all of the best solutions for application performance monitoring and management you may have found that it can be highly complicated to compare all of the available observability tools whilst also trying to keep within a reasonable budget.

While monitoring is an important part of any robust application deployment, it can also seem overwhelming to get a full application performance monitoring (APM) stack deployed. In this post, we’ll see how operating a Kubernetes environment using the open-source Kong Ingress Controller can simplify this seemingly daunting task! You’ll learn how to use Prometheus and Grafana on Kubernetes Ingress to simplify APM setup.