Systems | Development | Analytics | API | Testing

Tracing

OpenTelemetry in N|Solid

N|Solid Runtime, the OSS runtime that powers N|Solid Pro, is an innovative, lightweight runtime for Node.js applications. It offers real-time insights into performance, memory usage, and CPU consumption, giving developers unparalleled visibility into their code without requiring any modifications. In today’s software landscape, understanding your application's production behavior is crucial. With cloud-native architectures, microservices, and distributed systems, pinpointing issues is challenging.

Tracing Slow Performance

You have built your performance test and executed the tests under load and your tests do not meet your requirements in terms of response times. Or you are unable to execute your tests with the number of concurrent users required. In this post we will give some insights into where you might want to start looking for the root cause of your performance issues.

Build A Simple Tracing System in Elixir

In this post, the first of a two-part series, we'll cover how Elixir applications can be traced using OpenTelemetry and how macros can make this process super easy and streamlined. First, we'll talk about tracing and OpenTelemetry in Elixir. Then we'll improve our custom tracing layer step-by-step until we get an easy and seamless tool to trace our application. Let's get started!

OpenTelemetry based Distributed Tracing for WSO2 API Manager

Tracing is one of the three pillars of observability. Tracing an API call in WSO2 API Manager is important to observe, identify possible bottlenecks in an API invocation path, and debug them. WSO2 API Manager facilitates tracing API invocation paths and publishing the traces based on the OpenTelemetry standard, using multiple tracers, namely: OpenTelemetry Protocol (OTLP), Jaeger, Zipkin, Log & Custom Tracer. This demo outlines important concepts of OpenTelemetry based distributed tracing in WSO2 API Manager, followed by a demonstration of publishing traces using the OTLP Tracer to Elastic APM, when invoking a sample API.

OpenTelemetry based Distributed Tracing for WSO2 Micro Integrator

Tracing is one of the three pillars of observability. Tracing artifacts of WSO2 Micro Integrator is important to observe, identify possible bottlenecks in a message flow, and debug them. WSO2 Micro Integrator facilitates tracing message flows and publishing the traces based on the OpenTelemetry standard, using multiple tracers, namely: OpenTelemetry Protocol (OTLP), Jaeger, Zipkin, Log & Custom Tracer. This screencast outlines important concepts of OpenTelemetry based distributed tracing in WSO2 Micro Integrator, followed by a demonstration of publishing traces using the OTLP Tracer to New Relic APM, when invoking a simple API.