Victoria logs is awesome and has put me at odds with my new devops hire who hates it and insists that Dynatrace can do the same thing for only $$$ a month. I tried using the their front end and it’s horrible. The API for Victoria is awesome and it’s fast.
VictoriaLogs Practical Ingestion Guide for Message, Time and Streams
11–18 of 18 posts
Re: VictoriaLogs Practical Ingestion Guide for Message, Time and Streams
#12Earlier quoted context omitted.
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?
Sure thing! 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.
That sounds like a lot of resources provisioned for 6k/s. 625GB/24hr is a small footprint.
Re: VictoriaLogs Practical Ingestion Guide for Message, Time and Streams
#13We 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.
There is no complexity in Elastic stack, only expensive footguns /s
Re: VictoriaLogs Practical Ingestion Guide for Message, Time and Streams
#14Earlier quoted context omitted.
Sure thing! 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.
That sounds like a lot of resources provisioned for 6k/s. 625GB/24hr is a small footprint.
I would have said it sounded pretty good. What technologies are you comparing it against, out of curiosity.
Re: VictoriaLogs Practical Ingestion Guide for Message, Time and Streams
#15Earlier quoted context omitted.
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?
Sure thing! 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.
That seems pretty good. Do you have any sort of HA solution?
Re: VictoriaLogs Practical Ingestion Guide for Message, Time and Streams
#16Re: VictoriaLogs Practical Ingestion Guide for Message, Time and Streams
#17Earlier quoted context omitted.
I would have said it sounded pretty good. What technologies are you comparing it against, out of curiosity.
ClickHouse
Can you share any additional details? What kind of ingestion do you have, with what dimensions of a clickhouse cluster?
I'm also curious how it handles structured vs unstructured logs.
Thanks!
Re: VictoriaLogs Practical Ingestion Guide for Message, Time and Streams
#18I’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?
> VictoriaLogs was using Loki
Where was this mentioned?