https://sagarpanda.com/tags/new-relic/Recent content in New Relic on Sagar Panda | DevOps & Cloud Infra EngineerHugoenSat, 20 Jun 2026 07:45:10 +0530https://sagarpanda.com/blogs/monitoring/otel-on-eks/Sat, 20 Jun 2026 07:45:10 +0530https://sagarpanda.com/blogs/monitoring/otel-on-eks/<h2 id="why-this-setup">Why This Setup?<a href="#why-this-setup" class="heading-anchor" aria-label="Link to this section"><svg class="h-4 w-4" aria-hidden="true" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><g fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2"><path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71"/><path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71"/></g></svg></a></h2><p>Before getting into the architecture, a few quick notes. Telemetry goes to both <strong>New Relic</strong> and <strong>Honeycomb</strong> to test OpenTelemetry&rsquo;s backend-independence promise and compare the two. New Relic wins on day-to-day usability — dashboards, APM, and alerts work intuitively. Honeycomb takes more getting used to, but its MCP server is where it genuinely shines: connected to Claude, you can ask plain-English questions against live telemetry — no NRQL or PromQL required. That&rsquo;s the part worth <a href="#ask-claude"><em><strong>jumping to</strong></em> 👇</a> first if you&rsquo;re short on time.</p>https://sagarpanda.com/projects/k8s-otel-proj/Sat, 20 Jun 2026 00:00:00 +0000https://sagarpanda.com/projects/k8s-otel-proj/GitOps infrastructure and Kubernetes platform for an OpenTelemetry observability demo, provisioned on Amazon EKS.