News for hackers. Stuff that matters.
Re:Systems Monitoring with Prometheus and Grafana by EdwardDiego on Tuesday August 11, 2020 @07:51PM (#24127278)
We've used Thanos to aggregate multiple Prometheus (Promethii?) across our clusters to enable us to scale, each Prometheus deals only with a subset of scrape targets.

Biggest issue I've had was an app that was accidentally publishing several thousand metrics which caused the default scrape timeout of 15s to kick in.

(It was publishing Kafka lag per consumer group per topic, which was fine and dandy, until someone released an app that runs about 500 instances at peak, and scaled up and down frequently, and had incorporated the pod id into the consumer group names, which led to Kafka tracking many, many, many consumer groups. Given that the consumers were low value anyway, we now just exclude them from having their lag tracked.)

Re:Systems Monitoring with Prometheus and Grafana by fnord123 on Tuesday August 11, 2020 @11:56PM (#24128467)
>Promethii

Prometheuses.

ii is for latin words. Prometheus is/was Greek. I guess you could use Prometheoí but it would quickly derail any conversation. :)

Re:Systems Monitoring with Prometheus and Grafana by rollulus on Wednesday August 12, 2020 @02:18AM (#24129075)
There was a talk on Promcon 2016 about this subject [1]. The conclusion was: in English, indeed, Prometheuses. In Ancient Greek: Prometheis.

[1]: https://www.youtube.com/watch?v=B_CDeYrqxjQ

Re:Systems Monitoring with Prometheus and Grafana by unixhero on Wednesday August 12, 2020 @08:07AM (#24131188)
I kind of like the Ancient Greek version.