# Monitoring as code for modern DevOps teams

**URL:** <https://discourse.sensu.io/t/monitoring-as-code-for-modern-devops-teams/2839>\
**Category:** Sensu Go\
**Created:** [March 22, 2022, 2:34pm UTC](https://discourse.sensu.io/t/monitoring-as-code-for-modern-devops-teams/2839 "2022-03-22T14:34:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![iryna](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/iryna/32/771_2.png) [@iryna](https://discourse.sensu.io/u/iryna)\
**Post date:** [March 22, 2022, 2:34pm UTC](https://discourse.sensu.io/t/monitoring-as-code-for-modern-devops-teams/2839/1 "2022-03-22T14:34:56Z")

</div>

Software engineering teams that adopt “as-code” practices, like using configuration files and automated workflows instead of manual configuration and tools, gain major improvements in velocity. But even companies that enjoy the success of as-code practices for development and delivery lag behind in applying them to operational concerns like [monitoring and observability](https://sensu.io/blog/monitoring-as-code-what-it-is-and-why-you-need-it).

Sensu brings monitoring into the as-code fold and allows you to codify complex business requirements into repeatable steps.

Like many initiatives, monitoring as code requires people working in organizational alignment, a process of repeatable workflows, and a facilitating tool like the [Sensu observability pipeline](https://sensu.io/resources/whitepaper/monitoring-as-code-with-sensu).

[Check out our latest blog post to learn how to implement monitoring as code in your organization!](https://sensu.io/blog/monitoring-as-code-for-modern-devops-teams)