The latest News and Information on Log Management, Log Analytics and related technologies.
As organisations increasingly send their logs to one service, their metrics to another and their traces to a third location, they remain unable to gain a unified view across all of their data types. This is because as multiple tools are used to achieve similar goals for different data types the issue of tool sprawl quickly arises.
In the late 1960s, there was a rock band called Ten Years After and I liked the name the first I heard about them. I wanted to use "Splunk and the Financial Services Industry: Ten Years After" as the title of this blog entry, but it’s been more than ten years since I wrote the first Splunk Blogs entry on Splunk and the Financial Services Industry. As you can tell, a lot has changed since then and more than a decade is an internet lifetime in technology.
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.
