• 3 Posts
  • 29 Comments
Joined 28 days ago
cake
Cake day: September 11th, 2026

help-circle
  • See the “monitoring” namespace

    image

    kube-prometheus-stack plus VictoriaLogs for logs, about 100 pods on 2 nodes.

    The whole stack uses about 2.2 GB RAM. Prometheus takes about 1.1 GB of that and Grafana about 700 MB. CPU is basically idle, around 0.2 cores.

    Prometheus has about 150k series and uses about 7 GB for 15 days of metrics, so roughly 14 GB a month. Logs are about 3 GB a month. Grafana itself is under 1 GB.

    It’s mostly the default exporters, so a smaller lab would need less. A 20 GB volume would be plenty.

    Prometheus is set to retention: 15d and retentionSize: 18GB. Anything older than 15 days is dropped, and so is the oldest data if the total goes over 18 GB, whichever happens first. It’s sitting at a steady ~7 GB now that it has a full 15 days stored.











  • You’re explaining scenarios where you incorrectly use my setup.

    You can wire the switches so that if switched off it only kills power to that server and nothing else in the chain. You then basically have this, but modular:
    image

    Yea if you rip out a cord that you shouldn’t you’re going to lose power, that is true of any power strip.

    This has more components, so more things can fail, I will give you that, but that’s unlikely and for me at least, worth the trade off in making it modular.

    If the above picture was powering your servers, and you wanted to add a 7th plug, you’d have to unplug everything and buy a power adapter with more sockets, and deal with the rats nest of cables that follows, or add another of these that might have the same problem in the future.