This article compares three Go observability solutions—SDK instrumentation, eBPF‑based monitoring, and compile‑time code injection—explaining their mechanisms, open‑source implementations, trade‑offs, and why Alibaba Cloud's Instgo compile‑time approach offers a low‑overhead, non‑intrusive APM alternative.
This guide explains how Alibaba's open‑source Golang Agent enables full observability for Go applications without modifying source code, covering download, compilation, endpoint configuration, and examples of trace, metric, and log correlation using Docker and OpenTelemetry.
This guide explains how to use Alibaba’s open‑source Golang Agent to automatically instrument Go applications for tracing, metrics, and log correlation without modifying source code, covering binary download, build replacement for go build, endpoint configuration, and step‑by‑step examples with Docker‑based dependencies and Jaeger visualization.
This article explores the challenges of linking Real User Monitoring (RUM) with backend tracing, presents a comprehensive end-to-end traceability solution based on OpenTelemetry and the W3C Trace Context protocol, and offers best-practice guidance for integrating RUM into full-stack observability pipelines.
Observability turns a black‑box application into a system by gathering logs, metrics, and traces, using alerts to spot anomalies, then linking trace IDs to logs; OpenTelemetry standardizes this with instrumented client agents, a Collector (receivers, processors, exporters), and backend storage, while Java agents, span propagation, exemplars, eBPF, and bundles like SigNoz or OpenObserve let teams choose between a custom OTel stack or a solution.
Prometheus 3.0‑beta introduces a completely redesigned UI, Remote Write 2.0 with native support for metadata and histograms, built‑in OpenTelemetry metrics handling, UTF‑8 label support, native histograms, and several feature‑flag removals, while encouraging community testing before production use.
This article explains why Real‑User Monitoring (RUM) is ideal for linking front‑end experience to back‑end tracing, compares major trace‑propagation protocols, and presents practical OpenTelemetry‑based solutions—including RUM‑to‑Span and Span‑to‑RUM patterns—to enable full‑stack observability and impact analysis in cloud‑native environments.
The new OpenTelemetry Java instrumentation adds client and server request‑size metrics to gRPC by injecting a tracing interceptor via Byte‑Buddy bytecode enhancement, extracting payload sizes from protobuf messages, recording them with custom attributes and histograms, and applying analogous handler‑based logic for Go.
This article explains why the newly released OpenTelemetry Golang Agent from Alibaba Cloud offers a compile‑time, non‑intrusive alternative to manual SDK instrumentation and eBPF auto‑instrumentation, detailing its architecture, code examples, plugin support, context propagation improvements, and future roadmap for Go observability.
This article explains the challenges of manual OpenTelemetry SDK instrumentation and eBPF auto‑instrumentation for Go applications, introduces the Alibaba Cloud OpenTelemetry Golang Agent that performs compile‑time automatic instrumentation, details its architecture, code examples, plugin support, and future roadmap.
This article explains how to create OpenTelemetry instrumentation for the PowerJob distributed scheduler by implementing a Java agent with ByteBuddy, covering background, prerequisite knowledge, entry point discovery, version selection, implementation details, common pitfalls, Muzzle validation, and unit testing.
This tutorial walks through setting up OpenTelemetry tracing from scratch for both Java and Go microservices, covering collector and Jaeger deployment, required dependencies, configuration parameters, code examples for automatic and manual instrumentation, and how to add custom span attributes and spans.
This article walks through collecting, storing, and querying distributed tracing data with OpenTelemetry, ClickHouse, and Grafana, covering schema design, OTEL Collector configuration, materialized views, query patterns, visualization techniques, performance benchmarks, and future optimization directions.
This article walks through a complete, reproducible setup for collecting, storing, querying, and visualizing Kubernetes logs with ClickHouse and Grafana, covering architecture choices, agent configurations (OpenTelemetry Collector, Vector, Fluent Bit), schema design, compression results, query examples, performance tuning, and dashboard integration.
This article explains how Alibaba Cloud's ARMS team collaborated with the language and compiler team to create an OpenTelemetry‑based, compile‑time automatic instrumentation solution for Golang applications, detailing its background, technical workflow, key optimizations, and practical impact on cloud‑native monitoring.
The article explains how Helm simplifies deploying complex Kubernetes applications with a single YAML chart but cannot manage runtime operations, while Kubernetes Operators—built on custom resource definitions and webhook logic—automate tasks such as scaling, upgrades, and side‑car injection, offering higher‑level lifecycle management.
This article explains the challenges of deploying large language model (LLM) applications, outlines the need for end‑to‑end observability, and details Alibaba Cloud ARMS' LLM‑specific tracing, metrics, and Python agent solutions for monitoring, debugging, and performance optimization.
This article explains how Alibaba Cloud engineers tackled the challenges of long startup times and high memory usage in Java serverless workloads by designing a static Java Agent instrumentation that works with GraalVM Native Image, preserving OpenTelemetry observability while dramatically improving performance.
This article explains what OpenTelemetry is, its core components, key terminology, benefits, usage steps, and detailed architecture—including APIs, SDK pipelines, and the collector—providing a comprehensive overview for developers and operators seeking vendor‑neutral observability solutions.
This guide explains how to use Alibaba Cloud Service Mesh (ASM) to create isolated, on‑demand environments for cloud‑native microservices across multiple ACK clusters, leveraging traffic‑lane (permissive mode) and OpenTelemetry automatic instrumentation to achieve efficient development, testing, and progressive gray‑release workflows while reducing resource consumption.
Jaeger is an open‑source, CNCF‑graduated distributed tracing system built by Uber, and this guide explains its core concepts, architecture, sampling strategies, and various deployment options—including all‑in‑one, Kubernetes, and OpenTelemetry—plus how it compares with other tracing tools.
This article explains the background of metrics in cloud‑native systems, shows how to expose custom Prometheus metrics using OpenTelemetry's MeterProvider, compares different exporters, and provides a complete Pulsar client example with code snippets and configuration for end‑to‑end observability.
This article details Huya's transition from fragmented, non‑standard monitoring solutions to a unified OpenTelemetry‑based platform, covering project background, pain points, design decisions, SDK architecture, data pipeline, storage, alerting, root‑cause analysis, and future plans, highlighting the benefits of standardization and zero‑cost service integration.
This article explains why distributed tracing is essential for modern cloud‑native systems, outlines the three toughest problems—instrumentation, data collection, and context propagation—and shows how Alibaba Cloud ARMS and OpenTelemetry provide a comprehensive, multi‑language solution for end‑to‑end traceability.
This guide explains how to use OpenTelemetry's automatic instrumentation to propagate baggage headers, enabling a loose‑mode traffic‑lane (gray‑release) strategy in Alibaba Cloud Service Mesh without modifying application code, covering prerequisites, operator deployment, service setup, lane configuration, weight‑based routing, and verification steps.
The article explains how a custom java.net.spi.InetAddressResolverProvider SPI that works in a regular Spring Boot 3.x JAR fails when the OpenTelemetry Java agent is added because the agent’s JarLoader cannot read the SPI configuration inside the BOOT‑INF layout, and resolves the issue by disabling the agent’s own resolver resource so the custom provider is used.
The article walks through building a custom OpenTelemetry Java‑agent extension for Pulsar client metrics—migrating from SkyWalking, setting up a Gradle project, using ByteBuddy to instrument methods with advice, registering gauge metrics, packaging the jar, handling common class‑loader pitfalls, and configuring deployment via the OpenTelemetry operator.
By introducing the unified tRPC scaffolding tool trpcx and embedding OpenTelemetry‑generated observability configurations, the Tencent Docs backend team streamlined service creation, standardized directory structures, migrated metrics and logs to ClickHouse for cost‑effective performance, and established best‑practice workflows that dramatically improve development speed and fault‑diagnosis efficiency.
This guide walks you through deploying OpenTelemetry in Kubernetes, covering the purpose of otel‑collector, installation via manifests or Helm, the three deployment patterns (No‑Collector, Agent, Gateway), running the otel‑demo, and detailed configuration of receivers, processors, exporters, connectors, extensions, and service pipelines.
Trace2.0 is an OpenTelemetry‑based application monitoring system that processes petabyte‑scale trace data using multi‑channel client protocols, gRPC, load‑balancing optimizations, ZSTD compression, Kafka pipelines, ClickHouse storage, and a JDK 21 upgrade with virtual threads, achieving significant performance and cost improvements.
MySQL 8.3.0, released on January 16, 2024, adds enterprise masking refresh, OpenTelemetry telemetry, GTID extended format, automated Windows upgrades, and a new EXPLAIN JSON version while removing several legacy server options and replication variables.
At the 21st GOPS Global Operations Conference, New Oriental's senior operations manager Qi Chen detailed the demand, technical, and focus pressures that drove a phased, full‑process observability standardization, leveraging OpenTelemetry, Telegraf, Loki and CMDB tagging to achieve cost reduction and higher stability.
The article explains how Tencent Cloud APM implements full‑link tracing using OpenTelemetry standards, addresses challenges such as protocol compatibility, massive trace storage, and bytecode overhead with solutions like conversion gateways, tail sampling and thread profiling, and showcases best‑practice scenarios for topology analysis, front‑end/back‑end integration, and log‑trace correlation within the broader TCOP observability suite.
The article explains the importance of CI/CD observability, outlines common pipeline problems, introduces Grafana's GraCIe plugin built on OpenTelemetry, and discusses how enhanced visibility can improve reliability, decision‑making, and future standardization across CI/CD platforms.
The missing trace data in two Go services was caused by the GoFrame tracing middleware recording the gzip‑compressed /metrics response body as a UTF‑8 string, which the OpenTelemetry exporter rejected as invalid UTF‑8; disabling Prometheus compression or decompressing the body before logging resolves the issue.
Thread profiling uses threshold‑triggered tasks on business threads to capture stack snapshots, which a dedicated profiler thread sends via high‑performance gRPC to a server that queues them in Kafka, enriches and stores them in ClickHouse, correlates with OpenTelemetry traces, and provides metrics that let developers quickly pinpoint latency bottlenecks and improve system stability.
This guide walks through deploying Loki via Helm, configuring the OpenTelemetry Collector to use a filelog receiver and Loki exporter, and enabling Kubernetes event collection, providing step‑by‑step commands and YAML snippets for a complete logging pipeline in a Kubernetes cluster.
This article details Bilibili's evolution of its log system from an Elastic Stack‑based solution to a ClickHouse‑backed architecture with OpenTelemetry, describing the challenges of cost, stability, and scalability, the new components such as Log‑Agent, Log‑Ingester, and a custom visualization platform, and the performance gains and future directions.
This guide walks through installing OpenTelemetry Collector on a Kubernetes cluster using Helm, configuring DaemonSet and Deployment collectors, integrating Prometheus for metrics, and customizing receivers, processors, and exporters to achieve comprehensive observability of nodes, pods, containers, and cluster resources.
This guide explains how to enable OpenTelemetry in Apache Airflow, configure an OTel collector, use Prometheus as a metrics backend, set up Grafana dashboards, and visualize sample DAG metrics, providing a complete observability stack for Airflow pipelines.
This article details DeWu's evolution from a sneaker marketplace to a full‑stack e‑commerce platform and explains how its cloud‑native monitoring system, based on OpenTelemetry, ClickHouse, and object storage, was architected, optimized, and scaled to handle billions of spans daily.
This article analyzes a sporadic loss of trace information when using OpenTelemetry’s non‑capturing lambda tasks in a Java ThreadPoolExecutor, explains the underlying cause related to Runnable reuse and lambda caching, and presents the community‑driven patches that correctly propagate context across threads.
This guide demonstrates how to collect and store metrics, traces, and alerts in OpenObserve by configuring Prometheus remote_write, integrating OpenTelemetry SDKs and Collector, and setting up alert templates and destinations, complete with Kubernetes deployment examples, dashboard creation, and query techniques.
In modern cloud‑native applications, distributed tracing is essential for pinpointing errors across microservices, and OpenTelemetry provides a standardized framework for collecting and analyzing trace data, with a hands‑on Go implementation demonstrated in an upcoming expert-led workshop.
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 tutorial introduces full‑stack developers to distributed tracing, explaining core concepts such as spans, traces, identifiers, and trace context, and walks through a concrete JavaScript example that generates and propagates trace metadata across a browser app, API server, and background worker, while also covering logging challenges, OpenTelemetry, and Sentry’s monitoring features.
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.
