---
title: "#prometheus articles | Hashnode"
description: "Monitoring tool. Read the latest #prometheus articles and tutorials on Hashnode."
url: "https://hashnode.com/tag/prometheus"
---

Tag

# #prometheus

894 posts · 284 followers

[Waqas Shahid](https://hashnode.com/@practicaldevblog) · [1h ago](https://hashnode.com/posts/prometheus-tutorial-metrics-that-show-what-your-app-does/6afd3ec3052cdc4f4a77d754)

### [Prometheus Tutorial: Metrics That Show What Your App Does](https://practicaldevblog.hashnode.dev/prometheus-tutorial-metrics-that-show-what-your-app-does?utm_source=hashnode&utm_medium=feed)

Quick answer Prometheus is a monitoring system that pulls numbers from your app on a schedule and stores them as time series, so you can ask how many orders failed in the last hour or how slow checkou

10 min read · [practicaldevblog.hashnode.dev](https://practicaldevblog.hashnode.dev/prometheus-tutorial-metrics-that-show-what-your-app-does?utm_source=hashnode&utm_medium=feed)

[KIM KYUNGHWAN](https://hashnode.com/@kkhdevs) · [3d ago](https://hashnode.com/posts/prometheus-data-lost-after-pod-restart-how-to-set-kube-prometheus-stack-persistent-storage-a-storagespec-pvc-without-losing-the-emptydir-data/6af90d927893c5322a1054a4)

### [Prometheus data lost after pod restart? How to set kube-prometheus-stack persistent storage (a storageSpec PVC) without losing the emptyDir data](https://kkhdevs.hashnode.dev/prometheus-data-lost-after-pod-restart-how-to-set-kube-prometheus-stack-persistent-storage-a-storagespec-pvc-without-losing-the-emptydir-data?utm_source=hashnode&utm_medium=feed)

Prometheus data lost after pod restart? kube-prometheus-stack keeps the TSDB on an emptyDir unless storageSpec is set. How to check, and how to set persistent storage (a storageSpec PVC) without losing the emptyDir data.

24 min read · [kkhdevs.hashnode.dev](https://kkhdevs.hashnode.dev/prometheus-data-lost-after-pod-restart-how-to-set-kube-prometheus-stack-persistent-storage-a-storagespec-pvc-without-losing-the-emptydir-data?utm_source=hashnode&utm_medium=feed)

[Carmelo Buelvas Comas](https://hashnode.com/@cbuelvasc) · [4d ago](https://hashnode.com/posts/observing-ai-agents-grafana-dashboards-and-k6-load-tests-for-mcp/6af79105a87c70622a6271f9)

### [Observing AI Agents: Grafana Dashboards and k6 Load Tests for MCP](https://cbuelvasc.hashnode.dev/observing-ai-agents-grafana-dashboards-and-k6-load-tests-for-mcp?utm_source=hashnode&utm_medium=feed)

TL;DR Agents don't behave like humans: they call tools in bursts, in loops and in chains. If you can't see latency, errors and auth failures per tool, you can't run an MCP server in production. ⭐ Co

5 min read · [cbuelvasc.hashnode.dev](https://cbuelvasc.hashnode.dev/observing-ai-agents-grafana-dashboards-and-k6-load-tests-for-mcp?utm_source=hashnode&utm_medium=feed)

[Artem Senenko](https://hashnode.com/@slima4) · [5d ago](https://hashnode.com/posts/two-rejected-series-stalled-all-my-metrics/6af5fa210d3424f7c8464ed8)

### [Two rejected series stalled all my metrics](https://uptimepage.hashnode.dev/two-rejected-series-stalled-all-my-metrics?utm_source=hashnode&utm_medium=feed)

TL;DR. Three alerts fired while production was healthy. My metrics account had gone over its active series limit, because a rate limit plugin in Caddy publishes 13 series for every client address. The

10 min read · [uptimepage.hashnode.dev](https://uptimepage.hashnode.dev/two-rejected-series-stalled-all-my-metrics?utm_source=hashnode&utm_medium=feed)

[Sudhanshu Wani](https://hashnode.com/@TechBlog01) · [6d ago](https://hashnode.com/posts/measuring-latency-end-to-end-timestamp-chains-one-histogram-and-the-paint-time-trick/6af5b10a8eb11568125d02bc)

### [Measuring latency end to end: timestamp chains, one histogram, and the paint-time trick](https://techblog01.hashnode.dev/measuring-latency-end-to-end-timestamp-chains-one-histogram-and-the-paint-time-trick?utm_source=hashnode&utm_medium=feed)

Timestamps at every hop, one histogram, and honest percentiles down to the paint

12 min read · [techblog01.hashnode.dev](https://techblog01.hashnode.dev/measuring-latency-end-to-end-timestamp-chains-one-histogram-and-the-paint-time-trick?utm_source=hashnode&utm_medium=feed)

[Demuxer](https://hashnode.com/@demuxer) · [Nov 10](https://hashnode.com/posts/right-size-kubernetes-cpu-and-memory-requests-from-7-days-of-prometheus/6af388fc22fff8b635e73eb9)

### [Right-size Kubernetes CPU and memory requests from 7 days of Prometheus](https://demuxer.hashnode.dev/right-size-kubernetes-cpu-and-memory-requests-from-7-days-of-prometheus?utm_source=hashnode&utm_medium=feed)

Most CPU and memory requests are set once, by a guess, and never looked at again. At Demuxer we build Kuberniq, a desktop Kubernetes client for macOS and Windows, and this article shows how it compare

3 min read · [demuxer.hashnode.dev](https://demuxer.hashnode.dev/right-size-kubernetes-cpu-and-memory-requests-from-7-days-of-prometheus?utm_source=hashnode&utm_medium=feed)

[Marco Pedroza](https://hashnode.com/@mpedroza) · [Nov 9](https://hashnode.com/posts/building-a-high-performance-event-driven-rate-limiter-with-openresty-valkey-redis-prometheus/6af24665fb748db1724d6abf)

### [Building a High-Performance Event-Driven Rate Limiter with OpenResty, Valkey(Redis) & Prometheus](https://mpedroza.hashnode.dev/building-a-high-performance-event-driven-rate-limiter-with-openresty-valkey-redis-prometheus?utm_source=hashnode&utm_medium=feed)

A Practical Guide to protect your spring boot applications from a large number of concurrent requests.

13 min read · [mpedroza.hashnode.dev](https://mpedroza.hashnode.dev/building-a-high-performance-event-driven-rate-limiter-with-openresty-valkey-redis-prometheus?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/building-a-high-performance-event-driven-rate-limiter-with-openresty-valkey-redis-prometheus/6af24665fb748db1724d6abf)

[Abhijeet Shinde](https://hashnode.com/@abhijeet2005) · [Nov 8](https://hashnode.com/posts/slow-requests-grafana-internal-vs-public-address/6af09e772b2541f7d4d4c07b)

### [The Slow Requests Weren’t My Code. I Just Couldn’t See the Network Locally](https://weeklyupdate.hashnode.dev/slow-requests-grafana-internal-vs-public-address?utm_source=hashnode&utm_medium=feed)

What my internship taught me about production, Grafana, and a public address that sent traffic the long way round

5 min read · [weeklyupdate.hashnode.dev](https://weeklyupdate.hashnode.dev/slow-requests-grafana-internal-vs-public-address?utm_source=hashnode&utm_medium=feed)

[ZyVOP](https://hashnode.com/@zyvop) · [Nov 2](https://hashnode.com/posts/observability-on-a-budget-logs-metrics-and-traces-with-open-source-tools-zxgpm/6ae824538caaf19abed0e126)

### [Observability on a Budget: Logs, Metrics, and Traces with Open-Source Tools](https://blog.zyvop.com/observability-on-a-budget-logs-metrics-and-traces-with-open-source-tools-zxgpm?utm_source=hashnode&utm_medium=feed)

Build a lean observability stack with Prometheus, Grafana, Loki, Tempo, and OpenTelemetry while controlling data volume and self-hosting costs.

10 min read · [blog.zyvop.com](https://blog.zyvop.com/observability-on-a-budget-logs-metrics-and-traces-with-open-source-tools-zxgpm?utm_source=hashnode&utm_medium=feed)

[8](https://hashnode.com/posts/observability-on-a-budget-logs-metrics-and-traces-with-open-source-tools-zxgpm/6ae824538caaf19abed0e126)

[Nathanael FETUE](https://hashnode.com/@nathanael-fetue) · [Oct 31](https://hashnode.com/posts/a-metrics-endpoint-a-slow-client-cannot-stall-and-labels-that-cannot-explode/6ae66950a544f99eee44648e)

### [A metrics endpoint a slow client cannot stall, and labels that cannot explode](https://pegasus-nathanael-tech.hashnode.dev/a-metrics-endpoint-a-slow-client-cannot-stall-and-labels-that-cannot-explode?utm_source=hashnode&utm_medium=feed)

A timeout per read did not stop a client sending one byte at a time. How one deadline per connection and closed label lists protect a C++ agent.

4 min read · [pegasus-nathanael-tech.hashnode.dev](https://pegasus-nathanael-tech.hashnode.dev/a-metrics-endpoint-a-slow-client-cannot-stall-and-labels-that-cannot-explode?utm_source=hashnode&utm_medium=feed)
