Amazing product. We use VictoriaMetrics for quite a while, and previously used Loki and our custom Clickhouse/Vector approach for logs and we have switched to VictoriaLogs. It is much better and faster than Loki, same goes with custom CH/Vector thing we had. Kudos to the team, we are waiting for VictoriaTraces to switch Tempo instance to it for opentelemetry stuff.
CubsFan1060 · 2h ago
Can you talk a little bit about your Victoria Logs setup? About how many logs are you ingesting and what kind of sizing do you have on your setup?
We have a couple of projects like this with similar usage and similar machine sizing.
Still running vmlogs-single, and we will until we see a need to move to vmlogs-cluster version.
PaywallBuster · 1h ago
personally Hetzner SX295 that has 14x 22 TB on a ZFS setup
It ingests 70k lines per second without a sweat
reads are just as fast
paffdragon · 2h ago
I use it in docker on a NAS - VictoriaMetrics, VictoriaLogs, Grafana - low resource usage, fast, so far zero issues.
ProofHouse · 5h ago
I’m actually working on something right now where this can be extremely useful to me and I didn’t know about VictoriaLogs was using Loki. I wonder if anyone knows if there are other better alternatives or how this stacks up?
yla92 · 5h ago
> VictoriaLogs was using Loki
Someone can correct me if I am wrong here - I don't think it's the case tho. Especially, it's competing against Loki and Elastic
I think the GP intended to put some punctuation between ‘victorialogs’ and ‘was’
pphysch · 2h ago
We recently dropped-in VictoriaLogs for an old rsyslog setup. Extremely easy to deploy and admin, integrates nicely with Grafana. Definitely recommend doing this and moving to structured logging formats if you aren't already / are hesitant about the complexity of Elastic stack, etc.
Ingested logs 24h: 428 Mil Ingested bytes 24h: 625GB Inser req/s: 6k/s
8vCPU, 16GB mem. Running standard-rwo PVC on GCP.
We have a couple of projects like this with similar usage and similar machine sizing.
Still running vmlogs-single, and we will until we see a need to move to vmlogs-cluster version.
It ingests 70k lines per second without a sweat
reads are just as fast
Someone can correct me if I am wrong here - I don't think it's the case tho. Especially, it's competing against Loki and Elastic
https://itnext.io/why-victorialogs-is-a-better-alternative-t...