---
title: "The lazy developer’s guide to observing your own code"
url: https://daily.dev/posts/the-lazy-developer-s-guide-to-observing-your-own-code-zvcqnpe8i
source_url: https://www.cncf.io/blog/2026/08/25/the-lazy-developers-guide-to-observing-your-own-code
type: article
source: "CNCF"
published: 2026-08-25T11:35:53.526Z
updated: 2026-08-25T11:36:19.729Z
tags: ["observability", "ai-coding", "opentelemetry", "docker-compose"]
reading_time: 19
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The lazy developer’s guide to observing your own code

**[CNCF](https://daily.dev/sources/cncf)** · 19 min read · 0 upvotes · 0 comments

## Summary

Developers are increasingly asked to instrument their own code with OpenTelemetry, and this piece makes the case for why that benefits developers directly: faster debugging, quicker shipping, better code quality, clearer understanding of distributed systems, and easier untangling of AI-generated code. It covers common instrumentation pain points (SDK maturity gaps, lack of auto-instrumentation for languages like Rust/Elixir, verbose APIs, cardinality issues), practical tips (start with zero-code instrumentation, supplement manually, practice observability-driven development, use AI carefully), what to instrument (spans, logs, latency metrics, home-grown frameworks), and how to use AI coding assistants effectively for instrumentation. It also walks through setting up the OpenTelemetry Collector with sample YAML configs and compares three open-source desktop visualization tools: OTel Desktop Viewer, otel-tui, and OTel Front, including Docker Compose setups and their respective trade-offs.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.cncf.io/blog/2026/08/25/the-lazy-developers-guide-to-observing-your-own-code>

## Questions this post answers

### What open source desktop tools can I use to view OpenTelemetry traces, logs, and metrics locally without a SaaS vendor?

Three open source desktop tools exist for locally visualizing OpenTelemetry signals: OTel Desktop Viewer (traces only, web UI, started October 2022), otel-tui (traces, logs, metrics plus a service topology view, terminal UI, started March 2024), and OTel Front (traces, logs, metrics, web UI with a non-clickable dashboard, started November 2025). All three can be run via Docker Compose alongside an OpenTelemetry Collector instance.

_daily.dev surfaces practical comparisons like this for developers choosing local observability tooling._

### Which programming languages support zero-code OpenTelemetry instrumentation?

Zero-code (auto) instrumentation for OpenTelemetry is available for Java, .NET, Python, JavaScript, PHP, and Go. Languages like Rust and Elixir lack zero-code support, meaning developers must write manual code-based instrumentation from scratch for those languages. Even where zero-code instrumentation exists, manual instrumentation is still needed to fill in gaps specific to an application.

_Track which languages gain OpenTelemetry auto-instrumentation support as teams plan their observability rollout on daily.dev._

### What is the SpanMetrics connector in the OpenTelemetry Collector and what does it do?

The SpanMetrics connector calculates the duration of an OpenTelemetry span and feeds that duration into a metrics pipeline as a receiver, acting as an exporter in a traces pipeline and a receiver in a metrics pipeline simultaneously. This helps developers spot latency issues when a span takes longer than usual to complete, without needing a separate metrics instrumentation step.

_Developers configuring Collector pipelines can find setup details like this through daily.dev._

## Similar posts on daily.dev

- [Introduction to instrumentation with OpenTelemetry for Developers – Key Concepts A \(maybe not so\) quick introduction to the universe of instrumentation and observability.](https://daily.dev/posts/introduction-to-instrumentation-with-opentelemetry-for-developers-key-concepts-a-maybe-not-so-qu-zvvnihl7j) · The Miners · 1 upvotes · 0 comments
- [What is OpenTelemetry: A Leader's Guide to Fixing System Blind Spots](https://daily.dev/posts/what-is-opentelemetry-a-leader-s-guide-to-fixing-system-blind-spots-uaenglcwi) · Netguru · 0 upvotes · 0 comments
- [How Observability and Telemetry Can Enhance the Practice of Software Engineering](https://daily.dev/posts/how-observability-and-telemetry-can-enhance-the-practice-of-software-engineering-xf1p9gwkg) · InfoQ · 0 upvotes · 0 comments

---

Tags: [#observability](https://daily.dev/tags/observability), [#ai-coding](https://daily.dev/tags/ai-coding), [#opentelemetry](https://daily.dev/tags/opentelemetry), [#docker-compose](https://daily.dev/tags/docker-compose)

[View this post on daily.dev](https://daily.dev/posts/the-lazy-developer-s-guide-to-observing-your-own-code-zvcqnpe8i)
