Operations | Monitoring | ITSM | DevOps | Cloud

4 best practices for breaking down silos and establishing a culture of shared responsibility toward reliability.

In my past experience as an SRE I’ve learned some valuable lessons about how to respond and learn from incidents. Declare and run retros for the small incidents. It's less stressful, and action items become much more actionable. Decrease the time it takes to analyze an incident. You'll remember more, and will learn more from the incident. Alert on pain felt by people — not computers. The only reason we declare incidents at all is because of the people on the other side of them.

A couple of days ago, I was pleasantly surprised to suddenly see a tweet come in from Viktor Farcic. Viktor now works at upbound.io who developed Crossplane, and he also runs his own popular YouTube channel and co-hosts DevOps Paradox podcast. He’s well respected in the cloud native community. When I saw the tweet and noticed that Viktor had recorded a review of Civo on YouTube, I was just hoping he was kind to us...and I am pleased to say he was!

CircleCI pipelines are defined in configuration files using the YAML syntax, which has been widely adopted by many software tools and solutions. YAML is a human-readable declarative data structure commonly used in configuration files and in applications where data is being stored or transmitted. The data in pipeline configuration files specifies and controls how workflows and jobs are executed when triggered on the platform.

AIOps is a DevOps strategy that brings the power of machine learning to bear on observability and system management. It’s not surprising that an increasing number of companies are now adopting this approach. AIOps first came onto the scene in 2015 (coincidentally the same year as Coralogix) and has been gaining momentum for the past half-decade. In this post, we’ll talk about what AIOps is, and why a business might want to use it for their log analytics.

Ever since Google made Kubernetes open-source in 2014, it has enjoyed incredible growth, helping businesses of all sizes to successfully manage their containers and ultimately make the most of all that our cloud native world has to offer. Individual users certainly initially led the charge with Kubernetes, identifying issues, and generally exploring the best ways to intelligently test, manage, and deploy workloads.

DORA metrics come from an organization called DevOps Research and Assessment. This was a team put together by Google to survey thousands of development teams across multiple industries, to try to understand what makes a high performing team different than a low performing team. What they ended up settling on are these four metrics.

With DevOps teams moving at ever greater speed, it’s vital for security teams to be deeply involved at all stages of the software development and delivery lifecycle. Breaking down silos between development, operations, and security teams ensures that security considerations are not overlooked, that vulnerabilities are caught early, and that security checkpoints do not slow down the delivery process.

In this episode of the Break Things on Purpose podcast, we speak with Taylor Dolezal, Senior Developer Advocate at HashiCorp.