Live data from Hacker News

Prometheus 3.0

prometheus.io

41–44 of 44 posts

Re: Prometheus 3.0

#41
post #33

Earlier quoted context omitted.

> I'm a designer considering selfhosted Google Analytics alternatives I wanted to ensure that you saw this currently on the front page: https://news.ycombinator.com/item?id=42270389 (Show HN: Vince – A self hosted alternative to Google Analytics; 66 comments)

That is timing. Thank you, adding to my list.

Also check out https://umami.is

Re: Prometheus 3.0

#42

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…

Hey robinhood, any feedback on Talos?

We've been using Talos for our internal clusters for a while, but with quite small ones (3 kube node, 5 worker nodes).

Upgrading has been generally a non event, and we're quite happy with them.

How do you deploy Thanos ? In one of the clusters ?

Re: Prometheus 3.0

#43
post #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.

I think when I looked it was still half closed source or something, or maybe I was mislead by something I read. To be honest I didn't take the time to properly investigate it.

Re: Prometheus 3.0

#44
post #42

Earlier quoted context omitted.

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…

Hey robinhood, any feedback on Talos? We've been using Talos for our internal clusters for a while, but with quite small ones (3 kube node, 5 worker nodes). Upgrading has been generally a non event, and we're quite happy with them. How do you deploy Thanos ? In one of the clusters ?

We’re extremely pleased with Talos. Much more secure than Azure (our cloud of choice, unfortunately) which run a full-blown Ubuntu underneath. We haven’t run into any issues with Talos and upgrading is super easy with the talosctl tool, both Kubernetes and Talos version.

We currently have a thanos instance in each cluster. We could move it to a separate cluster to reduce some overhead, but the current approach works. We’re ingesting about 60Gi per day of metrics into the S3 bucket, so we might have to optimise that.

Post reply on HN