<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Opentelemetry on Agentic Engineering in Action (agentprose demo)</title><link>https://vibeprogrammer.github.io/agentprose-demo/tags/opentelemetry/</link><description>Recent content in Opentelemetry on Agentic Engineering in Action (agentprose demo)</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 08 Jul 2026 12:43:01 +0000</lastBuildDate><atom:link href="https://vibeprogrammer.github.io/agentprose-demo/tags/opentelemetry/index.xml" rel="self" type="application/rss+xml"/><item><title>You can't tune what you can't see: prompt‑cache observability for GitHub Copilot with OpenTelemetry</title><link>https://vibeprogrammer.github.io/agentprose-demo/posts/you-cant-tune-what-see-promptcache-observability-github/</link><pubDate>Wed, 08 Jul 2026 12:42:31 +0000</pubDate><guid>https://vibeprogrammer.github.io/agentprose-demo/posts/you-cant-tune-what-see-promptcache-observability-github/</guid><description>&lt;p&gt;Open VS Code, ask Copilot Chat one question, and if you crack open the debug view you can watch prompt‑cache tokens tick past for that single call. That&amp;rsquo;s exactly enough visibility for one developer, on one machine, for one prompt. It stops being enough the moment you want to answer a sharper question:&lt;/p&gt;</description></item></channel></rss>