Next-Level Observability with OpenTelemetry

1. jetbrains-otel-order-summary

   1 1 0 - Kotlin

   A Kotlin and Spring Boot application demonstrating next-level observability with OpenTelemetry.

   

   git clone --single-branch -b starter-template https://github.com/kimanikevin254/jetbrains-otel-order-summary.git

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. Spring Boot

   2 219 81,294 10.0 Java

   Spring Boot helps you to create Spring-powered, production-grade applications and services with absolute minimum fuss.

   

   In this tutorial, I'll walk you through how I moved beyond basic logging by instrumenting a Kotlin and Spring Boot backend service with OpenTelemetry. You'll learn how OpenTelemetry's tracing model gives you the execution context that logs alone can't provide. By the end of this guide, you'll have a working instrumented service and a clear mental model for building more observable backend systems.

4. opentelemetry-java-instrumentation

   3 25 2,600 10.0 Java

   OpenTelemetry auto-instrumentation and instrumentation libraries for Java

   

   mkdir -p agents curl -L https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/latest/download/opentelemetry-javaagent.jar \ -o agents/opentelemetry-javaagent.jar

5. prometheus

   4 516 65,632 9.9 Go

   The Prometheus monitoring system and time series database.

   

   The OpenTelemetry ecosystem has three main components: instrumentation, the Collector, and exporters. Instrumentation is how you integrate OpenTelemetry into your application, using language-specific SDKs to create spans, record metrics, and propagate context. The Collector is an optional middleware component that receives, processes, and exports telemetry data to one or more backends. Exporters are the plugins that actually send your data to a specific destination, like Prometheus or Jaeger.

6. opentelemetry-collector

   5 103 7,362 9.8 Go

   OpenTelemetry Collector

   

   In this tutorial, I'll walk you through how I moved beyond basic logging by instrumenting a Kotlin and Spring Boot backend service with OpenTelemetry. You'll learn how OpenTelemetry's tracing model gives you the execution context that logs alone can't provide. By the end of this guide, you'll have a working instrumented service and a clear mental model for building more observable backend systems.

7. jaeger-ui

   6 3 1,517 9.8 TypeScript

   Web UI for Jaeger

   

   The OpenTelemetry ecosystem has three main components: instrumentation, the Collector, and exporters. Instrumentation is how you integrate OpenTelemetry into your application, using language-specific SDKs to create spans, record metrics, and propagate context. The Collector is an optional middleware component that receives, processes, and exports telemetry data to one or more backends. Exporters are the plugins that actually send your data to a specific destination, like Prometheus or Jaeger.

Suggest a related project