From the Blogosphere
DevOps and App Supportability | @DevOpsSummit #DevOps #Microservices
Thoughts from an outback breakdown
By: Pete Waterhouse
Mar. 4, 2016 02:45 AM
On a recent road trip I was reminded about the importance of DevOps feedback loops and application supportability.
I enjoy driving into the Australian outback. This probably explains why I prefer to take the back roads. On my last trip I did just that; forgoing the fast highway for a more sedate but picturesque route. Deciding to fill up at a small country town gas station on my way home I hit a snag. The marvelous electronic park brake system wouldn't disengage. It was late and I was stuck up that proverbial creak without a paddle - 200+ miles from home.
Once the profanities had subsided and the cold realization that I was stuck took hold, I started some problem solving.
Being bushwhacked by lousy support
Sadly my euphoria subsided and the cursing returned - buried half way through the manual was a rude awakener - "in the event of a parking brake malfunction we recommend you contact your nearest dealer for an inspection." Solid advice, but the nearest dealer was 200 miles away and that'd involve a costly tow.
Lessons learned - by nature, software applications are complex, but supporting them doesn't have to be. As we develop more intricate applications put yourselves in the shoes of some poor schmuck who's being dragged out of bed at 3:00am to fix up a problem. Like me, they'll benefit from clearer documentation, instrumentation and monitoring methods that guide them to a solution in context of their position or role.
Always beware of automation myopia
Lessons learned - in the fast-paced digital world we increasingly put our faith in automation. So much so that we've lost touch with our tech skills and experience developed over many years - it's become atrophied. Automation is fine, but just like pilots who rely too much on autopilot, we can make errors when confronted with unexpected conditions. Therefore tools should be capable of being enhanced by the skilled folks who use them and also help broaden skills.
In high praise of feedback loops
Lessons learned - establishing and feeding back information and knowledge across teams is essential to improve the quality of software applications. In my predicament I only managed to acquire knowledge when one specialist had taken the time to document and publish it. Sadly in IT, knowledge is often withheld or the tools we use fail to leverage it in software development, testing and release processes.
Turning up the volume doesn't work
Lessons learned - in IT operations, staff are constantly dealing with alerts. Too often persistent alarms are ignored because they fall within established baselines, but over time they lead to systemic problems. This is due to operator "alarm fatigue," exacerbated by monitoring systems lacking the fine-grained analytical capabilities needed to distinguish real problems from false positives.
Modern applications are a lot like modern cars. They're complex to a point that no one likes looking under the hood when things go wrong. Never forget that in the quest for delivery speed, application supportability and continuous improvement through knowledge feedback is critical to success.
Reader Feedback: Page 1 of 1
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week