Skip to main content
Vibgrate Graph: over 40% fewer tokens, same results
Back to Tags

Opentelemetry

17 items tagged with "opentelemetry"

Filter by type:

Best Practices2

Best Practice

OpenTelemetry Instrumentation Guidelines

Best practices for generating consistent traces, metrics, and logs using OpenTelemetry.

Best Practice

OpenTelemetry Semantic Conventions

Standardized names and attributes for telemetry (spans, metrics, logs) so observability data is consistent and portable across tools and languages.

Patterns1

Pattern

Distributed Tracing

Tracks a single request as it flows across many services by propagating context, producing an end-to-end timeline that reveals latency and failure sources.

Tutorials4

Tutorial

How to Instrument an Application with OpenTelemetry

Add OpenTelemetry traces, metrics, and logs to a service and export them through the OpenTelemetry Collector to your backend.

Tutorial

How to Set Up Distributed Tracing with Jaeger

Deploy Jaeger, send OpenTelemetry spans to it, propagate trace context across services, and analyze latency in the UI.

Tutorial

How to Store Traces at Scale with Grafana Tempo

Run Grafana Tempo as an object-storage trace backend, ingest OpenTelemetry spans, and query traces from Grafana.

Tutorial

How to set up LLM observability and tracing

Instrument an LLM application to trace prompts, responses, tokens, latency, and cost so you can debug and optimize in production.

Blueprints1

Blueprint

Ad-hoc Logging to OpenTelemetry Blueprint

Unify scattered logs, metrics, and traces under OpenTelemetry with the Collector, semantic conventions, and vendor-neutral export.

Products1

Product

Jaeger

Distributed tracing platform

Reference Architectures1

Reference Architecture

Observability and SLO Platform on Kubernetes

Unified metrics, logs, and traces platform with OpenTelemetry, Prometheus, and SLO-based alerting on Kubernetes.

Playbooks1

Playbook

OpenTelemetry Observability Rollout Playbook

A program to instrument services with OpenTelemetry for unified traces, metrics, and logs, replacing fragmented vendor-specific monitoring.

Stacks5

Stack

OpenTelemetry + Tempo + Grafana Tracing Stack

Vendor-neutral distributed tracing: OpenTelemetry instruments and collects traces, Tempo stores them cheaply in object storage, and Grafana visualizes them.

Stack

Jaeger Distributed Tracing Stack

CNCF distributed tracing stack: OpenTelemetry instrumentation feeds Jaeger, which stores spans in Elasticsearch or Cassandra and visualizes request flows.

Stack

New Relic Platform

A consumption-based SaaS observability platform unifying APM, infrastructure, logs, and browser monitoring on a single telemetry database with OpenTelemetry support.

Stack

Sentry + OpenTelemetry

An application monitoring stack pairing Sentry's error tracking and performance monitoring with OpenTelemetry instrumentation for vendor-neutral traces and metrics.

Stack

Jaeger + OpenTelemetry + Prometheus

An open-source observability stack combining OpenTelemetry instrumentation, Jaeger distributed tracing, and Prometheus metrics, visualized in Grafana.

Comparisons1

Comparison

OpenTelemetry vs Vendor Agents

OpenTelemetry is an open, vendor-neutral standard for collecting telemetry; proprietary vendor agents are tightly integrated SDKs from a single observability provider.