The evolution of Devops in the age of AI
summary
Claims that Splunk delivers real-time Splunk analysis across Jenkins, SonarQube, Maven, Docker and Kubernetes logs to extract patterns; a data-driven experiment finds JIRA change requests correlate with production incidents at about 0.94–0.95 correlation; ML predicts resource trends for pod sizing on AWS and spots a surprising driver of falling click rates (image content) that proved actionable. Implementation needs months of data, Python/TensorFlow work, careful logging hygiene, iterative reduction of false positives, and treats ML as an assistant rather than a replacement.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:46Question
- 1:13Artificial Intelligence
- 2:49Automation vs Intelligent
- 4:10Challenges of AI
- 5:39Maturity of DevOps
- 6:44Rise of Complexity
- 7:22Jenkins Pipeline
- 9:12Data Quality
- 9:59Pipeline
- 10:58Data Discovery
- 11:54Machine Learning
- 12:38Questions
- 13:38Taxonomy
- 14:35Why application locks
- 15:27Machine learning alone are not enough
- 17:06Machine learning is an assistant
- 17:39Adaptive algorithms
- 18:18Better decisionmaking
- 18:51Measuring AI
- 20:15How to test AI
- 21:34What we found
- 27:14AI is useful
- 29:23Alan Turing
- 29:56Practical approach
related talks
34mDevOps at LLM Speed: Using an AI Copilot for Kubernetes and Jenkins
35mUsing the DevOps Pipeline to Generate Continuous, Valuable Insights
46mLeveraging AI and Automation in DevOps
12mThe Synergistic Impact of Artificial Intelligence on DevOps
39mSimplify, speed and improve development with DevOps
39mDevOps in the Age of AI: Human Powered Evolution
29mMeasuring Devops Success with Pipeline Analytics
42mData-Driven DevOps