Log Cop Automation
Instrument your console error logging, ETL the data, automate Splunk error log analysis and integrate it into your ticketing system for an accurate and fast feedback loop which can reduce your production errors by 80% Quickly indentify and route problems as they are noticed in a a development environment well before acceptance test or production. Track production error trends so new production errors are spotted within minutes, routed to the correct engineer and resolution begun immediately.
Outline/Structure of the Talk
An API for error logging.
The pros and cons of error identification.
Ways to identify exceptions for trending and metric analysis.
Extract, transform and load using Spring Batch.
Reporting using Excel and Java POI Excel library.
Trending using Excel pivot tables.
Using code ownership, Splunk parsing and ticket automation to resolve within hours or minutes of occurrence.
Ensuring management visibility and support to gain 80% defect reduction.
Learn the 4 Cs of successful error logging: Counting, Correlating, Context, Causality,
Learn how to count and identify trending errors.
Learn what heuristics work best for eliminating false positives.
Learn how to gain management visibility and support necessary to gain 80% defect reduction.
devops, buildmasters, leads
schedule Submitted 6 years ago
People who liked this proposal, also liked:
Amy Silberbauer - Transforming How We Deliver Value: Agility at ScaleAmy SilberbauerSolution ArchitectIBM
schedule 6 years agoSold Out!
Continuous delivery in software development allows us to deliver incrementally, get quick feedback, and react. A key enabler is the adoption of agile techniques and methods; key inhibitors in the enterprise are size, scale, and complexity. In particular, within large government organizations, teams face immense challenges in both the adoption of Agile and Lean principles but also scaling that adoption to an enterprise level. The Rational ALM organization is a typical enterprise, and our teams have (mostly) adopted agile principles. But agility at enterprise scale is not the same as team-based agile development. Now we must coordinate work across multiple interdependent teams to deliver value, rather than focusing on developing a single product or application. Amy Silberbauer shares her experience of adapting SAFe in an enterprise organization and describes the struggles, mistakes, and successes throughout that process. Amy identifies the key challenges, including the need to identify value, provide the right data for various audiences, and the inherent required culture shift. Learn how to avoid some common pitfalls as you and your own organization embark on this same transformation.
Sanjeev Sharma - Applying Lean, Agile and DevOps for better business outcomesSanjeev SharmaIBM WW Lead - DevOps Technical SalesIBM
schedule 6 years agoSold Out!
In this session we will take a look at DevOps through a ‘Lean’ lens. If one takes a look at the principles behind DevOps, one sees the roots of Lean. These lean roots, when studied and well understood, provide a framework to start measuring and then using those measurements to instrument the delivery pipeline and eliminate the bottlenecks in the pipeline, making it more efficient and productive.
The goal of DevOps is to deliver software to production, in an efficient manner, minimizing risk, and striving for continuous improvement. Applying Lean principles and especially Lean measurements to a delivery pipeline or even better, the entire DevOps lifecycle, helps progress towards these goals, in a proven, and mathematically astute manner. Development teams and organizations that have adopted Agile have already started on this journey for Dev-Test. DevOps extends this Lean and Agile thinking to the entire delivery cycle, and all the stakeholders – from ‘Line of Business’ to Production.
This session will explore the key principles of Lean and Lean Measurements, how they applied to Agile, and how they can be extended to DevOps.