That can be time consuming but as far as cookbooks go I’d say it’s medium complexity. Also, there is a very well-developed chef cookbook so installation and configuration is very manageable once you get your ingestion configured along with rulesets. It’s comprehensive as it is an entire stack. It’s easy to set up alarms, integrate with RESTful APIs for tools like like Slack, perform complex data correlation, and make purdy dashboards for management. I found statistical capabilities similar as well, but Kibana does seem to be more actuarially adherent. As you might have guessed, I just completed a project where I moved from ELK to Sumo for production log data and metrics visualization and it is a world of difference from Kibana as far as how much easier it is to get useful output. It offers most of what I remember that Splunk does without being prohibitively expensive. Then you can focus on just feature configuration without having to maintain the core service. It’s important to know right right off that Sumo is a cloud solution, so as long as you’re okay with shipping your logs and metrics over HTTPS to their servers, it’s a good way to go. I’m just a DevOps guy who hates dealing with crappy and incomplete log collection.Īfter dealing with the complexity of ELK, which is admittedly is very powerful and flexible so I have read, ElasticSearch is not for the faint of heart, especially when you walk into a shop and their ELK stack is 4 years old. Let me also say am not a shill for this company. I also tried Logly and LogDNA which were nice but not as powerful and feature rich as Sumo. I am not sure if you are open to commercial solutions, but Sumo Logic is an excellent ingest-type solution.
0 Comments
Leave a Reply. |