The article explains how growing system complexity drives the need for observability, outlines the three pillars of logs, traces, and metrics, compares traditional stability stacks with modern observability, and details OpenTelemetry's design, advantages, and implementation considerations for cloud‑native environments.
This article explains how Apache RocketMQ 5.0 integrates standardized distributed tracing via OpenTelemetry, detailing the underlying span model, semantic conventions for messaging, automatic and manual instrumentation options, configuration steps, a complete example workflow, and how to export traces to Alibaba Cloud SLS and ARMS for observability.
This article explains the fundamentals of metrics, the evolution of dimensional data, and provides a deep dive into Prometheus' four metric types—Counters, Gauges, Histograms, and Summaries—complete with practical code examples, query patterns, and a comparison of their strengths and trade‑offs.
This guide walks you through installing the open‑source SigNoz APM platform on Kubernetes, configuring its components, exploring link tracing with a demo app, and setting up logging and alerting for comprehensive cloud‑native observability.
This guide walks you through installing and configuring the open‑source Odigos observability control plane on a Kubernetes cluster, showing how to automatically collect traces, metrics, and logs from applications without modifying code and how to visualize the data with Grafana.
The article surveys the 2023 cloud‑native landscape, highlighting the rise of cloud‑based IDEs, the mainstreaming of FinOps and GreenOps, the ubiquity of open‑source SBOMs, the maturation of GitOps and OpenTelemetry, the growing impact of WebAssembly, and several related forecasts for the industry.
Facing the challenges of distributed microservice architectures, a financial services company implemented a unified observability platform that combines metrics, tracing, and logging via OpenTelemetry and custom agents, enabling real‑time visualization, anomaly detection, and performance analysis across seven core business middle‑platforms.
This article explores the challenges of end‑to‑end tracing on mobile apps, explains why issues are hard to reproduce, and presents a four‑step solution using a unified OpenTelemetry standard, automated data linking, performance optimizations, and machine‑learning‑driven root‑cause analysis.
After rebuilding its transaction system in 2020, 得物 progressed from the basic CAT monitoring tool to OpenTracing with Prometheus, and finally adopted OpenTelemetry to unify metrics, traces, and logs via a custom vmagent‑Kafka‑Flink pipeline, dynamic sampling, and extensible javaagents, positioning the platform for a performance‑analysis‑driven future.
This article explains how RocketMQ's message lifecycle can be fully observed using OpenTelemetry‑based metrics, covering producer, broker, and consumer stages, and shows practical monitoring, alerting, and troubleshooting practices for cloud‑native deployments.
This guide walks you through creating a complete observability stack—exporting metrics, traces, and logs from a Go web service, collecting them with OpenTelemetry Collector, and storing them in Grafana Mimir, Loki, and Tempo, then visualizing everything on a unified Grafana dashboard.
This article details the design of Trace2.0, a next‑generation distributed tracing platform built on OpenTelemetry, covering its end‑to‑end architecture, tail sampling with hot‑cold storage, Bloom‑filter implementation, and a self‑built ClickHouse storage layer that reduces storage costs by two‑thirds while improving query performance.
RocketMQ 5.0 introduces a brand‑new unified API built on gRPC, refines client types, adds four message categories, pre‑fetches topic routes, embeds a telemetry channel, and provides OpenTelemetry‑based tracing and metrics, all while offering a cloud‑native SDK repository for developers.
This article describes how Bilibili redesigned its log service by replacing Elasticsearch with ClickHouse, introducing OpenTelemetry‑based logging, optimizing storage, query, and alerting components, and enhancing ClickHouse features such as configuration tuning, Map types, and implicit columns to achieve higher performance, lower cost, and better observability.
Bilibili redesigned its five‑year‑old ELK‑based log platform by replacing Elasticsearch with ClickHouse, adopting OpenTelemetry for unified log ingestion, and building a custom visualization and alerting system, achieving tenfold write throughput, one‑third storage cost, and dramatically faster query response times.
Bilibili’s Log Service 2.0 replaces its Elastic‑Stack pipeline with an OpenTelemetry‑driven architecture that writes logs via high‑performance Go/Java SDKs to ClickHouse, delivering ten‑fold write throughput, two‑fold query speed, one‑third storage cost, a custom query gateway, visualization UI, and advanced alerting.
Building probe capabilities on OpenTelemetry gives cloud‑native teams a vendor‑neutral, standardized way to extend monitoring into full observability—supporting large‑scale, language‑specific instrumentation, plug‑and‑play plugins, and seamless integration with APM backends—so developers and operators can detect, debug, and predict faults across distributed containers.
Trace2.0 is an OpenTelemetry‑based distributed tracing platform that collects billions of spans daily, routes data through a control plane, OTel Server, and Kafka to ClickHouse hot‑cold storage with tail sampling, achieving 66% cost reduction, 12× compression, sub‑second query latency, and plans to offload raw spans to object storage.
This guide explains why distributed tracing is essential for micro‑service architectures, introduces Jaeger as an open‑source APM solution, and provides step‑by‑step instructions for deploying and configuring Jaeger on Rainbond with OpenTelemetry, including environment variables, service naming, and topology generation.
This article introduces four CNCF‑graduated open‑source projects—Prometheus, Jaeger, OpenTelemetry, and Thanos—that together provide metrics, alerts, tracing, and long‑term storage to improve observability, reduce downtime, and streamline troubleshooting for workloads running on Kubernetes.
This article examines how F6 tackled growing stability demands by evolving from traditional ELK‑based logging to a cloud‑native observability stack that combines Grafana, Prometheus, eBPF, OpenTelemetry, and ARMS, illustrating practical steps, challenges, and lessons learned for modern microservice environments.
This article explains cloud‑native observability, defines its three pillars—metrics, tracing, and logging—details the OpenTelemetry tracing data model and Span structure, reviews industry implementations such as Jaeger and Alibaba Eagle Eye, and shares practical challenges and solutions from real‑world production use.
The Apache APISIX community announced the 2.13.0 LTS release, enhancing stability, adding observability plugins, a new OpenTelemetry tracing plugin, multi‑language (Wasm, Python, Go) support, and a comprehensive list of bug fixes and improvements.
OpenTelemetry unifies tracing, metrics, and logs by merging OpenTracing and OpenCensus into a cross‑language specification, collector, language SDKs, and instrumentation libraries, offering vendor‑agnostic, low‑maintenance telemetry collection that separates data gathering from business logic while requiring external back‑ends for storage and analysis.
Cilium 1.11 introduces a beta Service Mesh, Kubernetes Ingress support, OpenTelemetry integration, topology‑aware load balancing, BGP pod‑CIDR announcements, managed IPv4/IPv6 neighbor discovery, XDP multi‑device acceleration, graceful termination, scalable ID spaces, endpoint slices and several feature enhancements and deprecations.
The article explains how observability—through logs, metrics, and traces—transforms the opaque, complex day‑2 operations of micro‑service, Kubernetes, and serverless environments into a deterministic, diagnosable system, highlighting OpenTelemetry, practical collection methods, and real‑world implementation challenges and benefits.
This article describes how to model a complex Uber‑style ride‑hailing system using Domain‑Driven Design, implement it with Java Spring Boot microservices, instrument it with OpenTelemetry for full observability, and validate the observability pipeline through a gamified chaos‑engineering approach that reduces MTTR.
This article explains what distributed tracing is, why it is needed alongside logging and metrics for observability, how it works with trace and span IDs, and describes Liulishuo's implementation using OpenTelemetry, W3C Trace Context, and tail‑based sampling to improve backend debugging.
OpenTelemetry, a CNCF observability project, standardizes telemetry data models, collection, processing, and export, offering vendor‑agnostic APIs, SDKs, and a configurable collector; the article explains its problem domain, solution components, history, future outlook, and provides a practical Go demo with code and configuration examples.
This article reviews Ant Financial's cloud‑native observability journey, covering its origins, the three pillars of tracing, metrics and logging, community projects like OpenTelemetry, practical implementations, sampling strategies, and future directions for unified microservice, mesh, and serverless monitoring.
