Why Splunk
To build a solid DevOps infrastructure, Yokogawa has brought in two practical tools — Chef for process management and Jenkins for test automation. However, it still faced challenges with monitoring and troubleshooting issues in a context where highly distributed and interconnected applications generate an ever-increasing variety, velocity and volume of logging data. It needed real-time DevOps visibility.
After trying a few solutions, however, Yokogawa was still unable to adequately analyze its various types of log data, while spending many man-hours to collect software development information. Developers had to export logs individually to Excel, then run analysis tools on source codes and report results manually, not to mention the inconvenience in sharing reports and insights across the company.
It was not until Yokogawa started using Splunk Enterprise that real change occurred. By integrating the software into its DevOps infrastructure and centralizing log data onto the Splunk platform, Yokogawa has successfully automated its data collection, analysis and reporting procedures, gaining proactive, end-to-end operational visibility on every DevOps process, and turning static data into dynamic insights.