Live data from Hacker News

Prometheus 3.0

prometheus.io

1–10 of 44 posts

Re: Prometheus 3.0

#2
That's good news, especially the reduced memory usage and OTLP ingestion support look nice. I have experimented with OTLP metrics before but eventually fell back to prometheus to avoid adding another service to our systems.

Re: Prometheus 3.0

#3
Migration to victoria metrics has been on my list for nearly a year, but the licensing of it always scared me a bit. My main issue is CPU and memory usage of prometheus, so maybe this upgrade will fix that.

Re: Prometheus 3.0

#6
post #3

Migration to victoria metrics has been on my list for nearly a year, but the licensing of it always scared me a bit. My main issue is CPU and memory usage of prometheus, so maybe this upgrade will fix that.

Apache 2 is scary? Maybe I'm missing something.

Re: Prometheus 3.0

#7
post #3

Migration to victoria metrics has been on my list for nearly a year, but the licensing of it always scared me a bit. My main issue is CPU and memory usage of prometheus, so maybe this upgrade will fix that.

VM was a game changer for us, 7x reduction in memory and 3x CPU, plus the scaling flexibility.

Re: Prometheus 3.0

#8
post #3

Migration to victoria metrics has been on my list for nearly a year, but the licensing of it always scared me a bit. My main issue is CPU and memory usage of prometheus, so maybe this upgrade will fix that.

It's a reminder to us all that when we think: "Hey, why sweating over this memory layout or that extra CPU expenditure, it's small and nobody will notice", there will be times when everybody will notice. Maybe notice as much as to switch to our competitors' products.

Re: Prometheus 3.0

#9
I've read entire page and still don't know what it is. Release notes are communication tool and this was a failure as such. You are losing random passerbys by not telling what your product is in first sentence of release notes, especially x.0
Post reply on HN