3 ms·

But I just setup Elasticsearch and Kibana yesterday!

• hathawsh 8y ago
  A few years ago, I set up centralized logging with Elasticsearch and Kibana on a site with very little traffic (less than 100 requests per minute). After a few months, it apparently fell behind on indexing and worked the logging server's hard drives 24x7. After a few more months, the server died. (It refused to power up and I wasn't interested in going deeper.) I freely admit that I don't know how to configure Elasticsearch correctly, but I feel like it should have been able to handle the indexing load in its default configuration. I think I'll try out this new logging solution. I only want basic indexing.
  • sandstrom 8y ago
    I try to stay away from long-lived processes written in Java. Maybe it's just me, but I think they consume insane amounts of memory.
• outworlder 8y ago
  No you didn't. You brought an ELK cluster up. Now the fun begins. Unless you have a small load, six months from now you'll say "I've spent the last 6 months setting up and tuning an ELK cluster. It looks like it might be ready for production workloads now, but let's make it a beta for the time being – I don't want to see a crash like we had last time..."
  • windowsworkstoo 8y ago
    Yeh, the trick with ELK is to spin it up on fewer, but beefier physical servers. We've had great success with this, compared to our first attempts, after failing by following internet memes about running ELK across lots of small virtuals....