Hacker Newsnew | past | comments | ask | show | jobs | submit | dengolius's commentslogin

> (I will need both) but I think that OpenObserve is even simpler.

ClickStack also looks promising.


May I suggest trying VictoriaMetrics Observability Stack?


Does anyone use Mullvad DNS servers? https://mullvad.net/en/help/dns-over-https-and-dns-over-tls#... I found them more acceptable.


Didn't know they have publicly available DNS servers. Thanks.

I've also started using/testing the DNS4EU servers: https://www.joindns4.eu/


I do (as a fallback), but they're extremely slow.

Did you know Wikimedia also runs a public DNS service?

https://meta.wikimedia.org/wiki/Wikimedia_DNS


They're pretty slow for me, 350ms on average:

https://i.imgur.com/7CeydnY.png


https://dns10.quad9.net/dns-query Unsecured: No Malware blocking, no DNSSEC validation (for experts only!)

Maybe it is fast because it is not secured at all? :D


https://dnsspeedtest.online/ a link with benchmarks for newer readers


I have had nothing but problems with their DNS service. Outages what feels like a daily basis.

But the VPN itself is great!


Maybe it because of using PHP?


Nope. Php is sufficiently fast.


404 Your browser hallucinated


> VictoriaLogs was using Loki

Where was this mentioned?


502 Bad Gateway

Does anyone know what's going on?


This article discusses why TiDB, a distributed SQL database, migrated its observability platform from Prometheus to VictoriaMetrics.

The Problem with Prometheus At scale, Prometheus started showing limitations, especially for large enterprise customers like Pinterest.The main issues were: - High resource consumption: Prometheus used a lot of CPU and memory, leading to frequent out-of-memory (OOM) crashes. - Long recovery times: After a crash, Prometheus needed a long time to recover, sometimes failing altogether. - Limited query performance: Large queries would often fail or be very slow.

The Solution: VictoriaMetrics

TiDB switched to VictoriaMetrics and saw significant improvements: - Better resource utilization: CPU and memory usage dropped significantly, eliminating OOM crashes. - Improved query performance: Large queries that previously failed in Prometheus now run efficiently in VictoriaMetrics. - Lower costs: Reduced resource consumption and better storage efficiency led to lower operational costs.


looks like iPhone SE 2025 should cover user needs for $800


AFAIK, OpenTelemetry has never been effective compared to Prometheus.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: