Kibana + ElasticSearch was a mess for us. Was glad to get rid of it. Cost a fort... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		ohgr on March 19, 2025 \| parent \| context \| favorite \| on: Some notes on Grafana Loki's new "structured metad... Kibana + ElasticSearch was a mess for us. Was glad to get rid of it. Cost a fortune to run and was time consuming. Loki conversely doesn’t even show up on our costs report (other than the S3 bucket) and requires very little if any maintenance! Also out of box configuration sinks 1TB/hr quite happily in microservices mode.

valyala 12 months ago [–]

How much CPU and RAM do all the Loki components use for your workload?

Could you share Loki config, which can deal with 1TB/hr volume of logs?

ohgr 12 months ago | [–]

No idea. It’s their out of box microservices set up. I think the only thing we pumped up was the chunks cache to 30Gb.

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