Node.js logging is an important part of supporting the complete application life cycle. From creation to debugging to planning new features, logs support us all the way. By analyzing the data in the logs, we can glean insights, resolve bugs much quicker, and detect problems early and as they happen. In this post, we will talk about the who, what, when, where, how, and why of Node.js logging. Later in this post, the “how” section will give insights into using code.

In the past, managing IT infrastructure was a hard job. System administrators had to manually manage and configure all of the hardware and software that was needed for the applications to run. However, in recent years, things have changed dramatically. Trends like cloud computing revolutionized—and improved—the way organizations design, develop, and maintain their IT infrastructure.

Microservices are increasingly used in the development world as developers work to create larger, more complex applications that are better developed and managed as a combination of smaller services that work cohesively together for more extensive, application-wide functionality. Tools such as Service Fabric are rising to meet the need to think about and build apps using a piece-by-piece methodology that is, frankly, less mind-boggling than considering the whole of the application at once.

An advanced, open-source technology called Kubernetes is used to manage, scale and deploy containerised applications automatically. Kubernetes offers a strong architecture that enables development and operations teams to effectively manage applications of several containers. Kubernetes was made by Google engineers. They shared it for free in 2014, and now a group called CNCF takes care of Kubernetes. People really like using Kubernetes to manage apps inside containers.

Docker: it’s one of those technologies that seems to be everywhere. Whether you’re a junior developer just starting out or a seasoned.NET developer, at some point in your career, you’ll most likely come across Docker for.NET. So, what is Docker?

Just conducting one type of testing is generally not enough. For example, let’s say you decide to perform unit testing only. However, unit tests only verify business logic. Many other types of tests exist to verify the integration between components, such as integration tests. But what if you want to measure the maximum performance of your application? Or what if you want to know how the application behaves under extreme stress?

In today’s rapidly evolving software landscape, ensuring observability is crucial for building robust and reliable applications. One of the critical components of observability is metrics, which provide valuable insights into the performance and behavior of our systems. OpenTelemetry, an open-source observability framework, offers a standardized approach to capturing, exporting, and analyzing metrics. This blog post explores seven OpenTelemetry metrics for tracking better visibility.

As exciting as it can be to write new features in your ASP.NET Core application, our users inevitably encounter failed requests. Do you know how to troubleshoot IIS or ASP.NET errors on your servers? It can be tempting to bag on your desk and problem your annoyance. However, Windows and ASP.NET Core provide several different logs where failed requests are logged. This goes beyond simple IIS logs and can give you the information you need to combat failed requests.

A PHP application might produce many different levels of warnings and errors during its execution. Seeing these errors is crucial for developers when troubleshooting a misbehaving application. However, many developers often encounter difficulties displaying errors in their PHP applications, leading to silent app failures.

If you are trying to figure out how to measure the performance of your application, you are in the correct place. We spend a lot of time at Stackify thinking about application performance, especially about how to monitor and improve it. In this article, we cover some of our most important application performance metrics you should be tracking.