Coding agents write the code and AI SRE agents operate it, so telemetry is the source of truth between them. Rose now brings low-volume, high-quality OpenTelemetry instrumentation to every repository.
All Blog Posts
Coding agents write the code and AI SRE agents operate it, so telemetry is the source of truth between them. Rose now brings low-volume, high-quality OpenTelemetry instrumentation to every repository.
Trust store passwords in resource attributes, OAuth tokens in query strings, tax IDs in metrics: what we found in real pipelines, why tools cause most of it, and what privacy laws allow.
OllyGarden and Bronto on where AI agents help with instrumentation and analysis today, and why they only work when the telemetry is intentional and reachable.
OpenTelemetry still does not make dashboards portable, but agents, CLIs, and MCP servers have made switching observability backends noticeably less painful.
A wrong metric scrape interval inflates ingest, egress, and compute. Learn how to measure DPM and match intervals to the decisions each metric supports.
We’re releasing our Agent Skills for OpenTelemetry as a mature, open source set: 14 skills that give any coding agent accurate, current OpenTelemetry knowledge.
When you configure two exporters in one pipeline, does the Collector send to them in parallel? The honest answer is "sequentially, but it usually doesn't matter." The part that does matter changed defaults underneath a lot of advice still floating around.
Tulip gives you a commercially supported OpenTelemetry Collector with a curated component set. When you need more, you can derive your own distribution while keeping support for the core pipeline. This post walks through how.
When your collector configuration grows beyond a few hundred lines, you start feeling the friction. This post examines practical strategies for decomposing collector configurations into maintainable, testable units.
When I asked the community about their pain points with OpenTelemetry, one response kept appearing: 'it's complicated.' I think the framing is wrong.
KubeCon + CloudNativeCon Europe 2026 in Amsterdam was a big week for OllyGarden. Our team delivered five recorded talks across Observability Day and the main conference, co-chaired the Observability Day program committee, ran a Prometheus Contribfest session, and announced the general availability of Rose.
Confused about logs, traces, and metrics? Learn when to use each telemetry signal in OpenTelemetry and build a stronger observability strategy.
High observability costs are rarely a volume problem. Learn how to fix bad telemetry at the source before relying on sampling.
Your logs are probably at least 80% repetitive noise. Connection retries, health checks, heartbeat messages: the same log line repeated thousands of times per day.
We analyzed 10,000 messages from the OpenTelemetry community Slack to find the most common adoption challenges, from Collector config to instrumentation.
Imagine the perfect observability world: There is an incident, the on-call team gets paged in the middle of the night, wakes up and thanks to your telemetry, resolves it fast.
OllyGarden Tulip is a commercially supported OpenTelemetry Collector distribution: stable quarterly releases, LTS every 18 months, open source and free.
Discover how to manage spans effectively using the Variability Principle to improve trace readability and control costs in OpenTelemetry.
Learn how to name OpenTelemetry metrics: follow semantic conventions, keep the 'who' in attributes, and apply units and naming patterns that scale.
A practical guide to naming OpenTelemetry span attributes: when to use semantic conventions, how to namespace custom attributes, and pitfalls to avoid.
Good span names make traces readable. Learn the {verb} {object} pattern for naming OpenTelemetry spans and avoid the most common naming mistakes.
The NGINX Ingress Controller has no knob for the OpenTelemetry service.instance.id attribute. Here's how to inject a unique ID per pod with the Helm chart.
OllyGarden comes out of stealth with pre-seed funding to fight bad telemetry: helping teams understand, score, and improve the telemetry they generate.
The Instrumentation Score is an open, standardized measure of OpenTelemetry instrumentation quality, scoring OTLP data against best-practice rules.
From NASA-grade telemetry design to code-level tips: concrete techniques for applying purposeful instrumentation in real-world OpenTelemetry systems.
Purposeful instrumentation means gathering the right telemetry, not all of it. Cut noise, troubleshoot faster, and lower observability costs.
Most telemetry is never queried. Learn what separates good telemetry from bad, what bad data costs you, and how to start improving quality at the source.
Learn More
Check our posts, videos, and much more in our social media. See our latest videos.
