How Soluto Cut Troubleshooting Time by 50%

Soluto once had no concrete logging system in place — manual log analysis was the name of the game. But as the company grew and the product changed to a more microservices-based architecture, it quickly became apparent that a reliable and easy-to-use log analysis platform was needed.

“When considering our options, we were torn between ELK and Splunk as possible log analysis alternatives. Splunk is very expensive, and ELK is open source, so we opted for the latter.”

Asaf Kotzer, Chief Architect

Soluto is an all-in-one support and protection service that integrates a mobile app, web portal, proactive communications system, and remote device management platform into one service. As a big adopter of open source technology, Soluto initially explored the option of setting up and maintaining an ELK Stack all on their own. They quickly found out that their needs could not be met by a self-maintained ELK setup.

“Very early on, we became aware of the problems and challenges associated with scaling an ELK stack.”

Asaf Kotzer, Chief Architect

Soluto’s large production environment meant they needed a fully reliable and scalable system that did not break under heavy loads. Initial testing of their ELK Stack showed a scalability weak point that could not be overlooked. Soluto also required a logging system that allowed developers to gain quick, easy, and complete visibility into how hundreds of microservices are behaving in development and production with fully informational messages that contained more than only lists of errors.

Soluto heard about the Logz.io ELK-as-a-Service log analysis platform at a community event and decided to use the solution after a short period of time spent proving the concept and implementing a log forwarding system of logs into Logz.io.

“Using Logz.io, we have cut troubleshooting time by 50% and speeded up the time to market of new features.”

Asaf Kotzer, Chief Architect

Soluto has implemented a log-driven development process in which the entire development team has become 100% DevOps-orientated with full access to the Logz.io ELK Stack. Each microservice that services the product is now bound to a log. Developers are now writing error, warning, and debug logs, ultimately making them full owners of the code they develop. That, together with defining stricter log levels, helps Soluto to create a noise-free DevOps and business environment in which developers no longer need to bother themselves with the logging infrastructure itself.