<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prometheus on Abhishek Walia</title><link>https://awalia.dev/tags/prometheus/</link><description>Recent content in Prometheus on Abhishek Walia</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Abhishek Walia</copyright><lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://awalia.dev/tags/prometheus/index.xml" rel="self" type="application/rss+xml"/><item><title>JMX Monitoring Stacks</title><link>https://awalia.dev/projects/jmx-monitoring-stacks/</link><pubDate>Sun, 01 May 2022 00:00:00 +0000</pubDate><guid>https://awalia.dev/projects/jmx-monitoring-stacks/</guid><description>&lt;p&gt;Most monitoring setups for Kafka require long and lengthy parsing configurations to get JMX metrics into your telemetry system. This project standardizes that pipeline across Prometheus/Grafana, New Relic, Elastic/Kibana, Datadog, and OpenTelemetry.&lt;/p&gt;</description></item><item><title>Topic-Level Kafka Cost Attribution with Prometheus</title><link>https://awalia.dev/blog/topic-level-kafka-cost-attribution/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://awalia.dev/blog/topic-level-kafka-cost-attribution/</guid><description>&lt;p&gt;&amp;ldquo;Which topic is costing us?&amp;rdquo; is the question every platform team gets, and nobody can answer it cleanly. SaaS providers bill you at the cluster level. Your finance team wants a line item per team. Your product managers want to know if their pipeline is the expensive one. You have a Kafka cluster, a bill, and no bridge between them.&lt;/p&gt;</description></item><item><title>Monitor Kafka Clusters with Prometheus, Grafana, and Confluent</title><link>https://awalia.dev/talks/confluent-blog-prometheus-grafana/</link><pubDate>Mon, 29 Mar 2021 00:00:00 +0000</pubDate><guid>https://awalia.dev/talks/confluent-blog-prometheus-grafana/</guid><description>&lt;p&gt;Published on the &lt;strong&gt;Confluent Blog&lt;/strong&gt;, March 2021.&lt;/p&gt;
&lt;p&gt;Self-managing a Kafka cluster means wiring up your own monitoring. This post walks through how to export JMX data from Confluent clusters into Prometheus and Grafana with minimal setup. It became the reference blog series for connecting Confluent ecosystems to Prometheus-based monitoring stacks.&lt;/p&gt;</description></item></channel></rss>