In this tutorial, we will go through a working example of a NestJS application auto-instrumented with OpenTelemetry. In our example we will use a simple application that outputs “Hello World!” when we call it in the browser. We will instrument this application with OpenTelemetry’s Node.js client library to generate trace data and send it to an OpenTelemetry Collector. The Collector will then export the trace data to an external distributed tracing analytics tool of our choice.

After creating your Logz.io account, the first step for onboarding is to send you log, metric, and trace data. Logz.io makes this flexible – allowing for multiple ways to get data into your Logz.io account depending on your use case and technology stack. Today, we’re excited to announce another easy and fast way to get AWS metric data into Logz.io: by setting up a CloudWatch metrics stream and a Kinesis Firehose.

Regardless of economic conditions, IT usually operates under an axiom no one in business ever likes to hear: “We have to do more with less.” Doing more with less is essentially the default position for IT, but when it comes to security operations, that position can have real consequences.

When you migrated critical infrastructure to the cloud, what were your goals and expectations? Odds are, you hoped leaving on-premises infrastructure would produce significant organizational benefits. You probably figured you’d streamline operations and reduce management overhead. You felt you’d have an easier time meeting business goals. Perhaps most important of all, you likely expected your environment would become less complex, and even cost less to operate.

For the last five years, Logz.io has tracked and measured the pulse of DevOps, as well as adoption of key trends and technology, through our DevOps Pulse survey and report. One of the obvious focus areas for us, as a company whose products are based on industry-leading open source, is the increased rise of incredibly useful open-source observability solutions, in general.