Introducing Trace, a new add-on

If you’re used to code micro-services with Node.js, you may be familiar with the frustration of performance issues, finding the root cause of an error and hunting down memory leaks.

That’s why services like Trace are here. Trace is a Node.js performance monitoring tool which helps you to understand how your application behaves and lets you find performance bottlenecks with ease.

Today we are launching Trace as an add-on for Clever Cloud, which can be tried out for free until July 1st without any restrictions.






Distributed tracing

Trace comes with a unique feature called distributed tracing: It visualizes whole transactions (request-chains) in your microservices architecture and looks for errors.

This means that you can see on an interactive timeline:

  • which services were taking part in a transaction,
  • how big were the response network delays,
  • how long did a service handled a request,
  • where and when the errors happened in that transaction.

Trace connects services taking part in a request by attaching correlation IDs to them. This way you can visualize the exact data-flow of faulty transactions, see the dependencies between your microservices, look for bad status codes and localize ongoing issues.

Service mapping

Trace provides you with a dynamic service map, which is automatically generated based on how the services in your system communicate with each other, or with your databases and external APIs.

Thanks to this, you can see how your application really looks like, and understand what makes it to slow down. The service map also allows you to find out how many requests your services handle and how big are their response times.


Getting started

Adding Trace to your services is possible with just a couple lines of code, and it can be installed and used in under two minutes. There is a tutorial for the installation on Trace’s documentation: http://trace-docs.risingstack.com/docs/fix-crashing-nodejs-applications-with-trace

Some Use cases

Using Trace to fix crashing Node.js apps: http://trace-docs.risingstack.com/docs/fix-crashing-nodejs-applications-with-trace

Using Trace to investigate slow Node.js apps: http://trace-docs.risingstack.com/docs/fix-crashing-nodejs-applications-with-trace

Blog

À lire également

Elasticsearch Observability: logs, metrics, and traces explained

Modern architectures generate ever-growing volumes of data. Microservices, APIs, cloud workloads, and serverless environments multiply potential failure points. In this context, understanding what is really happening in production has become a central challenge.
Engineering

ELK Stack: what it is used for and how to use it for observability

Understanding what is really happening inside a modern application has become increasingly complex. Microservices, cloud environments, and the growing number of physical or virtual servers all contribute to an explosion of technical signals. This distribution makes so-called “traditional” log analysis—based on directly connecting to a single machine—hard to sustain at scale.
Engineering

Identity Access Management: pillar of security and compliance

Identity Access Management (IAM) is now one of the foundations of information system security and governance.…

Engineering