Much easier time while debugging API requests involving multiple services while reducing the number of logs by 85%? All that thanks to distributed tracing!
Status: Stable for the trace, metric and log signals. Development for the profiles signal. The OpenTelemetry Protocol (OTLP) specification describes the encoding, transport, and delivery mechanism of telemetry data between telemetry sources, intermediate nodes such as collectors and telemetry backends. OTLP is a general-purpose telemetry data delivery protocol designed in the scope of the OpenTelemetry project. Protocol Details OTLP defines the encoding of telemetry data and the protocol used to exchange data between the client and the server.
Much easier time while debugging API requests involving multiple services while reducing the number of logs by 85%? All that thanks to distributed tracing!
Specifications for OpenTelemetry. Contribute to open-telemetry/opentelemetry-specification development by creating an account on GitHub.
MuleSoft Documentation Site
Display observability events in the console, which can be useful for debugging purposes
Official MLflow documentation for LLM tracing, agent evaluation, prompt management, experiment tracking, model registry, and beyond.
Building and configuring syslog, HTTPS log drains and Telemetry drains
query OpenTelemetry metrics, logs, and traces (OTLP) in duckdb - smithclay/duckdb-otlp
Welcome to the Holy Dev newsletter, which brings you gems I found on the web, updates from my blog, and a few scattered thoughts. You can get the next one into your mailbox if you subscribe.What is happeningI have spent all my free time with Rama, which resulted in the posts Rama: How to achieve a transactional update across partitions and Hands on Rama, day 3: Foreign keys and data integrity, macros, queries. Sadly, I did not have much time for Wolframite, but that will need to change, as our Clojurists Together sponsorship quarter is coming up 🙀.
The J*, a blog about Java, JVM, JavaScript and Gentoo Linux
Imagine a world where a pilot would have to fly an over 500-ton, 4-engined Airbus A380 with virtually no flight instruments, only a primitive joystick and maybe a headlight for night landings. Imagine a captain navigating through a coral reef full of underwater ridges, or maneuvering beneath the polar ice sheet, all while commanding a submarine without sonar and basic instruments. Imagine a construction equipment operator required to excavate a 400m long, 3m deep ditch - although the excavator they are manning only has a number of peepholes in solid metal cabin walls instead of proper windows.
OpenTelemetry Report
Per-talk notes from PyTexas 2026 in Austin: Hynek on domain modeling, Dawn Wages on specialization, MCP security, PEP 810 lazy imports, free-threading, Ruff, ty, uv, supply chain.
Distributed Tracing is scary and complicated... right?
OpenTelemetry is not perfect, but the value of having one shared standard for instrumentation and telemetry is huge
Protobuf schemas get overlooked because most developers have only ever worked with JSON
How to filter business events from raw OpenTelemetry telemetry, store them in tiered object storage, and make them searchable with DuckDB — no vendor lock-in and no per-query cost.