3 ms·
That was my experience exactly. The value of being able to search through ours logs was immediately apparent, so when it kept tanking every couple weeks it was
by Jgrubb 11y ago
That was my experience exactly. The value of being able to search through ours logs was immediately apparent, so when it kept tanking every couple weeks it was fairly easy to talk my boss into paying a tiny bit more for Loggly. AFAICT Loggly is the ELK stack with a different theme applied to the UI, and I don't have to worry that it's down when I need it.
The preceding has been an unpaid endorsement for Loggly.
- dozzie 11y agoI would prefer much more to have something hosted by me and being open source at the same time (I'm looking at you, Splunk). I'm desperate enough to write such thing myself (and I'm already doing some research on indexing semi-structured data), even if it would turn out not-too-scalable (I only have ~1.5GB/day of uncompressed logs), but I'm scared by the need of tolerance for abrupt shutdowns and hitting a free disk space limit, i.e., database recoverability.
- Jgrubb 11y agoHey, I looked at Splunk in the last few days as well, but it seems really expensive once you want to get beyond 500MB a day. They don't have an OSS "community" version, do they (?) because I totally feel you on that. Basically I need ELK, but I need it to be a lot more stable and documented better.
- packetized 11y agoLoggly is a five digit monthly bill at our present logging volume. No thanks.
- asafm 11y agoI suggest taking a look at the logz.io - it's essentially ELK as a service. We take care of many problems ES has and also have great features extra such as Alerting, Apps and Insights. I'm one of the core developers there so I'm fluent in pricing but last time I checked it's wasn't expensive and definitely worth your time and hosting costs. One the the great things about it is that you can simply migrate your dashboard and just ship to our Url.
- Jgrubb 11y agoWhat are you using? I'd rather run it myself, but like I said ELK was a bit too bleeding edge for me in the stability dept.
- packetized 11y agoHeka for ingestion/parsing/message routing, RabbitMQ as the queuing/delivery mechanism, Elasticsearch as datastore, Grafana for visualization.