3 ms·
Worth mentioning that Elastic.co has a commercial product called Watcher [1] which I think is a really nice way for making an automated alert system. The downsi
by yeukhon 11y ago
Worth mentioning that Elastic.co has a commercial product called Watcher [1] which I think is a really nice way for making an automated alert system. The downside is being a commercial product I can't use Watcher and would have to implement one myself.
I am still deciding between ES, a relational database and Cassandra for time series data. We use graphite now and are happy with it, but I think having a single database handling logs, events and metrics data would be much more ideal. Having logs already in ES does make ES a better choice.
[1]: https://www.elastic.co/guide/en/watcher/current/index.html https://www.elastic.co/guide/en/watcher/current/index.html
- chrstphrhrt 11y agoWe used elastalert on a project and it did the trick: https://github.com/Yelp/elastalert https://github.com/Yelp/elastalert
- yeukhon 11y agoThanks... and Python... I don't have to reinvent something... will take a look thanks!
- trjordan 11y agoWe used Cassandra for timeseries data for a while. My word of caution would be to set up a dedicated cluster for it. Cassandra is good at a lot of things, but if you have different workloads running on the same cluster, performance is hard to tune. We used it for raw document store (write once, read almost never) and timeseries in the same place (lots of appending, even more reads), and it wasn't great.
- yeukhon 11y agoYeah absolutely, points taken thanks. I think infrastructure's infrastructure :D should be dedicated. Yeah agree with metrics read is more than write, plus write in Cassandra is intrinsically quick.