- Consistent use of configuration management tools.
- Reuse of deployment patterns.
- Allowing teams to configure monitoring and alerts.
So, you’re new to DevOps. Maybe you were attracted to the field’s promise of high salaries, or maybe you really liked the idea of combining your development and operations knowledge. Maybe nobody else at your company wanted the role, and so you stepped up, figuring you’d learn on the job—that’s cool, too (good luck!). But now you have a big challenge on your hands: How do you even start installing a proper DevOps culture? That’s something much, much easier said than done. Remember, DevOps specialists oversee everything from software integration to automating parts of a company’s IT stack (with a particular emphasis on automation, at least these days). That means a lot of software to monitor, and many stakeholders to manage—especially if a company has never embraced such a culture before. Fortunately, Puppet’s annual State of DevOps report offers some useful advice (along with tons of survey data) for just that very thing. Specifically, the company recommends three foundational things for any organization hoping to embrace DevOps: