2022 Gartner® Magic Quadrant™ SIEM
Get the reportMore
With DevOps currently at the peak of the hype curve according to Gartner’s Hype Cycle for Enterprise Architecture, 2015, there’s little question that DevOps has become a highly charged, and some would argue, over-marketed term, giving rise to confusion and misunderstandings of what DevOps really is. Organizations in turn risk time, resources and money attempting to solve the wrong problem.
As you’ll hear in the book, DevOps is a strategy for developing what is becoming a universally recognized process for managing continuous delivery, but it is not that process. Continuous Delivery (CD) is the process whereby software is developed iteratively and delivered in stages along a deployment pipeline. The benefits of CD for larger IT organizations are clear and widely embraced.
As you’ll learn, DevOps is the culture, process and tools used in the CD cycle. From an agile perspective it facilitates teams to work harmoniously together with the goals of software quality and continuous improvement. The process, as just stated is continuous delivery, but the goals are similar: To deliver quality software more often while teams increase their velocity. That leaves tools.
Tools used along the CD pipeline range from compilers, debuggers, and build tools to configuration management, monitoring and deployment tools. Depending on whether the platform is on-premise or in the cloud, tools can be categorized into team collaboration, application development, system level, and API-level tools. These tools include:
While increasing code coverage for unit tests and automated testing have greatly improved the quality of software, clean code doesn’t mean software always behaves as expected. A faulty algorithm or failure to account for unforeseen conditions can cause software to behave unpredictably. Within the CD pipeline, troubleshooting can be difficult, and in cases like debugging in a production environment it may not even be possible.
The good news is that virtually all of the tools across the CD pipeline emit machine data, which are typically captured in log files. At the applications level, logs capture the stream of events of your app’s running processes including events generated by the application server and libraries. System logs capture events such as restarting a crashed process, and API logs can provide useful information when deploying new code.
Sumo Logic provides developers and others on DevOps teams with visibility into critical issues across the DevOps tool chain using event logs. Gone are the days of setting breakpoints in a debugger and stepping through code. Once a collector is configured for your app, logs are fed through the Sumo Logic service. Sumo Logic delivers out-of-the box dashboards, reports, saved searches, and field extraction for popular data sources. When an app is installed in Sumo Logic, these pre-set searches and dashboards are customized with source configurations and populated in a folder selected by the user.
Through Sumo Logic’s LogReduce® pattern-matching algorithm selects patterns as well as outliers that help developers quickly spot patterns in event logs, CI server logs and troubleshoot their applications in real time. So they can spend less time troubleshooting and more time developing code.
Sumo Logic address five common use cases:
The following articles in this eBook first appeared on devops.sumologic.com, and are written by members of the Sumo Logic DevOps community. This eBook looks not only at DevOps, but technologies like containerization that are changing how DevOps teams configure environments for deployment. The opinions are theirs: We hope you’ll find useful insights to problems DevOps teams are challenged with today.
Build, run, and secure modern applications and cloud infrastructures.Start free trial