4 ms·
I discovered netdata in 2016 and it's become a standard part of my server builds. Fast, low memory, and crucially it's pretty enough to satisfy/inform non-tech
by petecooper 8y ago
I discovered netdata in 2016 and it's become a standard part of my server builds. Fast, low memory, and crucially it's pretty enough to satisfy/inform non-tech people.
- leetbulb 8y agoSame here. It's on every standalone server I manage. I also use it on my workstation.
- nammi 8y agoI agree that the value it provides is really high for how simple it is to set up. At first, my only complaint was the relatively short data retention period, but I found that it was really easy to send the data into InfluxDB or Prometheus by following their wiki. That's not netdata's use-case anyway, and it's trivial to set up a backend db when I want to have long term metrics. https://github.com/firehol/netdata/wiki/netdata-backends https://github.com/firehol/netdata/wiki/netdata-backends
- manigandham 8y agoThe netdata metrics store is in-memory and works well for several hours, but there's a memory-mapped mode to keep larger amounts of data. There's also a future roadmap to eventually add on-disk compressed archives for even longer retention. https://github.com/firehol/netdata/wiki/Memory-Requirements https://github.com/firehol/netdata/wiki/Memory-Requirements
- nammi 8y agooh cool, thanks for sharing that link. In case I wasn't clear, I'm happy with using netdata for short-term data, and hooking up a db in the rare case I want long-term. But that link has a ton of interesting details, can't wait to read later