assembla airbrake webinar - production monitoring and continuous delivery - slides - may 2013

Production MonitoringThe Key Step Towards Continuous Delivery

PresentersMichael Chletsos● CTO @ Assembla.com● Previously DevOp for Assembla● Heavy interest in Continuous Delivery

Workflows

Justin Mares● Director of Growth @ Airbrake (acquired

by Rackspace)● Co-author of Traction Book ● Former co-founder of CloudFab

Questions & CommentsThere will be a Q&A session at the end.

To Submit Questions:● use the "Questions" area on the

GoToWebinar side panel-OR-

● use Twitter (hashtag: #assemblaQA)

Continuous Delivery is not a process that I can define for you, rather its a goal.

The Goal of being able to continuously deliver your code to QA/UAT or Production and react in real time to the results of the release.

How to perform this is dependent on your Ecosystem.

What is Continuous Delivery?

CD at Assembla

CD at Assembla

Iteration Planning

CD at Assembla

Continuous Delivery

Traditional Iteration Plans

Planning Coding Release

Stress Level Scope of Work

Traditional Iteration Plans

Planning Coding Release

Stress Level Scope of Work

Add More Requirements

Bug Fixes

Traditional Iteration Plans

Planning Coding Release

Stress Level Scope of Work

Add More Requirements

Bug Fixes& More Work

CD at Assembla

Problems of IterationsJust admit it -

Planning is Hard

Priorities Change

Unforeseen Problems Occur

Why Continuous Delivery?● More Frequent Releases

● Faster Issue Resolution

● Improved Productivity

● Better Quality of Code

● Less Stress on the Team

● Better Customer Experience

What's the Secret Key?If you want to start anything today that will help you immediately:Monitor Errors in Production

If you want to do nothing else but one thing to be able to Continuously Deploy:Monitor Errors in Production

Why Monitor?

Working software is the primary measure of progress.

- Agile Manifesto

Monitoring● Monitor Everything

● Monitor Everything

● Monitor Everything

● React to Anomalies not Thresholds

Errors in Production

Assembla Deploys● Automated

● Click of a Button Deploys

● Reliable

● Consistent

● Monitored

Assembla Process

Barebones CD

Code Production

Barebones CD

Code Production

That's Just Cowboy Coding!

Barebones CD

Code Production

Production MonitoringBugs

Barebones CD

Production

Production MonitoringBugs

Assembla Process

Assembla Process

Bad Release

Any Process

Production

Production MonitoringBugs

Airbrake.io

Airbrake.io

Why Monitor?

Airbrake

It's a Process

Code Production

Production MonitoringBugs

Must understand what's happening in production

ADD

Need Insight!Key Question: what broke??

Backtrace

Environment

Parameters

Bug Triage

If you only have a few tests (or even none at all), don't despair. Simply set up the CI server and agree to one simple rule: we'll add a new automated test every time we fix a bug.

- Eric Ries, author of the Lean Startup

Too Many Errors!

Too Many Errors!Prioritization is critical

● How many similar errors have occurred?● How often does this happen?● Who knows most about issue?

Too Many Errors!Track:● Errors since last deploy● Critical errors● Error rate (increasing or decreasing?)● Repeating errors

Stickermule

Implemented monitoring:● Permanent 3% conversion uptick

Deploy with Confidence

What To Do Now● Airbrake.io

● Assembla.comMichael ChletsosCTO Assembla.commpchlets@assembla.comblog.assembla.com

Justin MaresGrowth at Airbrakejustin@airbrake.ioblog.airbrake.io