dengolius

victoriametrics?

> Grafana is fine to get to a selfhosted basic install. But once you try to actually connect logs, metrics, traces in selfhosted context and perhaps sprinkle some otel in...that sht gets out of hand very fast. It's modular in a way that seems like a win but once you start connecting stuff it starts adding complexity not easy.

Maybe because some open-source software has limitations? That seems reasonable to me.

Would you like to share your success story using this software?

What about InfluxDB? Speaking of standards, it’s worth noting that this system was created early on, when microservices were emerging as a concept. Another reason this “de facto standard” emerged is that there were almost no alternatives. This is what we need to understand about standards and who promotes them. But technology doesn’t stand still, and I wouldn’t call Prometheus the standard right now, because OpenTelemetry is already starting to be referred to as the standard in the field of observability. Some people like it, some don’t, but Zabbix and Nagios are still going strong; for some, they remain the standard for monitoring for a variety of personal reasons.

The answer to your question was deleted, so I'll post it again:

Vertically on a single machine, the two are quite similar, both fan work out across all CPU cores. The different is on scaling out.

ClickHouse scales by making you describe the cluster yourself. You decide how many shards to split the data into, how many copies (replicas) each shard keeps, which row goes to which shard. The copies are kept in sync by a consensus system ClickHouse Keeper. This is flexible but also more works on operators.

VictoriaLogs takes the opposite bet. When logs come in, the inserter just spreads them across all storage nodes on its own, so there is no sharding key for you to design. When a query runs, the selector asks every storage node in parallel and merges the results. There is no consensus system at all. If you want high availability, you run 2 independent clusters and send your logs to both, rather than having the database copy data internally. So this is simpler and less learning curve. See more here https://victoriametrics.com/blog/victorialogs-architecture-b...

I read somewhere that the owners have ties to russia, but the most important thing is that they’re marketing very aggressively through posts that slander GraphenOS.

Does anyone know when they'll sell their company and product to russia again?

Meh, I don't get it—what's stopping you from running the same benchmark on a Kubernetes cluster and sharing your own benchmark results, instead of just claiming that this benchmark is crap?

what about av1?

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

ClickStack also looks promising.

May I suggest trying VictoriaMetrics Observability Stack?

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

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

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

Maybe it because of using PHP?

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.

What is the reason to choose gohttpd? I mean there are a lot of non standard libraries for go that are pretty fast or faster then gohttpd - https://github.com/valyala/fasthttp/ as example

Yes, TigerData aka Timescale tried to make a fuss a few years ago comparing Clickhouse and TimescaleDB, but they failed.

VictoriaMetrics team member here.

Have you had a chance to play with VictoriaLogs? If not, then I highly recommend to test it. Our team is also working on implementing traces in top of Jaeger and VictoriaLogs, see https://victoriametrics.com/blog/dev-note-distributed-tracin...

Have you tried coroot?

What about https://github.com/mit-pdos/RVirt? "RVirt doesn't need KVM or Linux and can run on any sufficiently powerful 64-bit RISC-V processor with an MMU"

Do we really need another GUI for kvm/qemu? I thought https://cockpit-project.org cover the idea to develop something like Karton, but who am I to think so =)

My friend uses self-hosted open-source software to monitor all his home IoT devices[1] and copies important information to the cloud. I'm using StarFive VisionFive 2 to host my database for monitoring, but also have a copy of the data of a chip hetzner arm vps, as well as hosting backups on the two different clouds. I know users who are running[2] for years to monitor Solar panels, lawn watering and vegetable garden watering.

My question is: is it really convenient to use only SaaS now if there is always the possibility of losing your data? I am referring to the case described in the article.

[1]: https://vrutkovs.eu/posts/home-infra/ [2]: https://github.com/VictoriaMetrics-Community/homeassistant-a...

PS: I'm working at VictoriaMetrics company