4 ms·
Graphite is a mature system. It's a pain in the ass, but I generally find it essential for server monitoring. I'm working on a timeseries database aimed at rep
by yummyfajitas 12y ago
Graphite is a mature system. It's a pain in the ass, but I generally find it essential for server monitoring.
I'm working on a timeseries database aimed at replacing graphite. It's just getting started, so it probably won't work immediately, but contributions are welcome. Currently the write performance is already better than graphite [1].
https://github.com/stucchio/timeserieszen https://github.com/stucchio/timeserieszen
[1] This was one of the design goals. Whenever graphite receives a data point a disk seek is incurred - the data point must be appended to the timeseries file. Timeserieszen uses a WAL - data flowing in is immediately written, and periodically the WAL is rolled over into permanent storage.
- sciurus 12y agoCool project! I commented on some other graphite replacement projects at https://news.ycombinator.com/item?id=8368689 https://news.ycombinator.com/item?id=8368689
- yummyfajitas 12y agoI didn't realize graphite was officially dead. I must say, however, that it was the shittiest piece of software I've ever relied on and loved.
- general_failure 12y agoI didn't realize this either. In fact, we just moved to graphite :-(