Operations | Monitoring | ITSM | DevOps | Cloud

NodeJS

How to use VSCode to debug a Node.js application

Debugging is an essential step in software development, as it allows developers to fix errors before releasing the software to the public. Debugging tools can be integrated into code editors, making the debugging process more efficient. This tutorial will show you how to debug node.js in Visual Studio Code.

Get more insights with the new version of the Node.js library

We’re thrilled to announce the release of a new update to the Cloud Logging Library for Node.js with the key new features of improved error handling and writing structured logging to standard output which becomes handy if you run applications in serverless environments like Google Functions!

Node.js Performance Monitoring

Many software developers utilize Node.js to create high-performance backend web applications. It has numerous advantages, including ease of application deployment, asynchronous request handling, great performance, and more. Integrating a solid monitoring solution into your Node.js application is critical since it gives you visibility into what's going on in your application at any given time or over a specific time.

A Complete Guide to Node.js Process Management with PM2

Process management refers to various activities around the creation, termination, and monitoring of processes. A process manager is a program that ensures that your applications always stay online after being launched. Process managers can prevent downtime in production by automatically restarting your application after a crash or even after the host machine reboots. They are also useful in development: they auto-restart an app once its source files or dependencies are updated.

Implementing distributed tracing in a nodejs application

In this article, we will implement distributed tracing for a nodejs application based on microservices architecture. To implement distributed tracing, we will be using open-source solutions - SigNoz and OpenTelemetry, so you can easily follow the tutorial. In modern microservices-based applications, it is difficult to understand how requests are performing across multiple services, infrastructure, and protocols.

Debugging Node.js Memory Leaks: How to Detect, Solve or Avoid Them in Applications

In this article, you’ll learn how to understand and debug the memory usage of a Node.js application and use monitoring tools to get a complete insight into what is happening with the heap memory and garbage collection. Here’s what you’ll get by the end of this tutorial. Memory leaks often go unnoticed. This is why I suggest using a tool to keep track of historical data of garbage collection cycles and to notify you if the heap memory usage starts spiking uncontrollably.

Malware Civil War - Malicious npm Packages Targeting Malware Authors

The JFrog Security research team continuously monitors popular open source software (OSS) repositories with our automated tooling to avert potential software supply chain security threats, and reports any vulnerabilities or malicious packages discovered to repository maintainers and the wider community. Most recently we disclosed 25 malicious packages in the npm repository that were picked up by our automated scanning tools.

Node Congress Lightning Talk: Monitoring errors and slowdowns with a JS frontend and Node backend

We've got a JavaScript frontend hitting a Node (Express.js) backend. Join Chris Stavitsky in this quick 7-min demo as he goes through how to know which party is responsible for which error, what the impact is, and all the context needed to solve it. This lightning talk took place at Node Congress on Feb. 17, 2022.

Node Congress Workshop: Tracking errors and slowdowns in Node + JavaScript using Sentry

Join Neil Manvar, Sales Engineer Manager, as he sets up Sentry step-by-step to get visibility into our frontend and backend. Once integrated, he will show you how to track and triage errors + transactions surfaced by Sentry from our services to understand why/where/how errors and slowdowns occurred within the application code. This workshop took place live at Node Congress on February 15, 2022.

Better Way To Write Async Function in Node/Express/Next - Handle catch(err) Only Once.

Avoid Writing a Lot of Try Catch by Catching The ‘catch()’ Just Once. How annoying it is to write a lot of try-catch for each async function in an express app? What if you never need to write a try catch block for all async functions and still be able to handle the errors?