Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Prometheus 3.0

prometheus.io

Post reply on HN
Print view View original

21–30 of 44 posts

Re: Prometheus 3.0

#21

Post by therealdrag0 »

hinkley wrote: post #16
nine_k wrote: post #8

Earlier quoted context omitted.

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.

Developers tend to ignore C in order of complexity calculations but customers don’t. Game developers and HFTs seem to understand this, and very few regular devs I’ve interacted with do. I’ve seen customers say they switched to someone else for speed reasons. And I’ve worked on projects where the engineers were claiming this as fast as we can make it, and they were off by at least a factor of three. We like to think t…

Those margins also mean you have to pick your battles. Most software is not as performance sensitive as video games or HFT.

I take an efficient market hypothesis on this. Obviously devs can make stuff faster, and they do where it matters, as can be seen in games and HFT. In other software it’s a discussion with product of trade offs.

Re: Prometheus 3.0

#22

Post by never_inline »

> Native Histograms are still experimental and not yet enabled by default, and can be turned on by passing --enable-feature=native-histograms. Some aspects of Native Histograms, like the text format and accessor functions / operators are still under active design.

Ah, slightly disappointed :). Looking at major version I thought it was going to be all about Native histograms.

Re: Prometheus 3.0

#23

Post by never_inline »

the_duke wrote: post #15

I'm curios: are many people here actually still running mainline Prometheus over one of the numerous compatible solutions that are more scalable and have better storage? (Mimir, Victoria, Cortex, OpenObserve, ...)

I am curious to hear from people on this forum, at what point will people practically cross the limits of prometheus, and straightforward division (eg, different prometheus across clusters and environments) does not work?

Re: Prometheus 3.0

#24

Post by hagen1778 »

oulipo wrote: post #14
Fizzadar wrote: post #7

Earlier quoted context omitted.

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

Hmmm but the documentation seems poorly written, what is the team behind?

What makes you think that about docs? Of course, it was written by developers, not tech writers. But anyway, what do you think can be improved?

Re: Prometheus 3.0

#25

Post by never_inline »

dvh wrote: post #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

Sir, for thought leaders and CTOs they have a home page.

This is for DevOps minions.

Re: Prometheus 3.0

#26

Post by pentagrama »

I didn't know this tool, and looking the homepage, is not clear to me if is something like Google Analytics to get metrics of website traffic, or something more dev oriented.

Someone can explain to me please? Maybe I'm a bit lost because I'm not a dev. I'm a designer considering selfhosted Google Analytics alternatives and this one may be interesting to add to the research (so far I have Matomo, plausible, open panel, umami, open replay, highlight). Thanks

Re: Prometheus 3.0

#27

Post by trallnag »

oulipo wrote: post #14
Fizzadar wrote: post #7

Earlier quoted context omitted.

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

Hmmm but the documentation seems poorly written, what is the team behind?

Specifically the documention or VictoriaMetrics overall? The latter started with a small number of Ukrainians

Re: Prometheus 3.0

#28

Post by remram »

pentagrama wrote: post #26

I didn't know this tool, and looking the homepage, is not clear to me if is something like Google Analytics to get metrics of website traffic, or something more dev oriented. Someone can explain to me please? Maybe I'm a bit lost because I'm not a dev. I'm a designer considering selfhosted Google Analytics alternatives and this one may be interesting to add to the research (so far I have Matomo, plausible, open panel…

It's usually meant to monitor infrastructure, like memory and CPU usage of various processes and machines, request per seconds for servers, number of HTTP errors returned, etc.

https://prometheus.io/docs/introduction/overview/#what-are-m...

Re: Prometheus 3.0

#29

Post by aorth »

the_duke wrote: post #15

I'm curios: are many people here actually still running mainline Prometheus over one of the numerous compatible solutions that are more scalable and have better storage? (Mimir, Victoria, Cortex, OpenObserve, ...)

Using Victoria Metrics here. Very easy to set up and run. I monitor under 100 hosts and resource usage is low, performance is good.

One gripe is that they recently stopped publishing tarballs for LTS versions, which caused some grumbling in the community. Fair enough since they are developing for free, but felt like a bait and switch.

Re: Prometheus 3.0

#30

Post by ChocolateGod »

robinhoodexe wrote: post #20
the_duke wrote: post #15

I'm curios: are many people here actually still running mainline Prometheus over one of the numerous compatible solutions that are more scalable and have better storage? (Mimir, Victoria, Cortex, OpenObserve, ...)

We’re running standard Prometheus on Kubernetes (14 onprem Talos clusters, total of 191 nodes, 1.1k cpu cores, 4.75TiB memory and 4k pods). We use Thanos to store metrics in self-hosted S3 (seaweedfs) with 30 days retention, aggressively downsample after 3 days. It works pretty good tbh. I’m excited about upgrading to version 3, as is does take a lot of resources to keep going, especially on clusters with a lot of po…

> We use Thanos to store metrics in self-hosted S3 (seaweedfs) with 30 days retention, aggressively downsample after 3 days.

Any reason to not just use Mimir for this?

Post reply on HN