Monaco 2.0 - Dynatrace Configuration as Code Reloaded!

Monitoring, or better Observability Configuration, needs to be expressible as Code in order to scale and automate into DevOps platforms enabling a true shift-left approach of managing observability configuration like managing source code. #Dynatrace has been a pioneer by open-sourcing Monaco 1.0 (Monitoring as Code) years ago. As Dynatrace has evolved from a monitoring to an observability platform, it was time to rethink and expand Monaco towards all aspects of Observability configuration. To learn more In this observability clinic where Nico Riedmann, Sr. Software Engineer at Dynatrace, does a Recap on Monitoring as Code, gives a deep dive into Monaco 2.0 Features, and does an extensive best practice end-2-end demo of integrating Monaco into your automation practices. Here are the relevant links discussed: Monaco V1 Observability Clinic:    • Monitoring as Code - Empowering Developers...   Monaco V2 Documentation: https://dynatr.ac/3QWgtEF Monaco GitHub Repo: https://github.com/dynatrace/dynatrac... Download Monaco: https://dt-url.net/get-monitoring-as-... Terraform Observability Clinic:    • Getting Started with Dynatrace Terraform   Chapter List: 00:00 – Introduction 00:48 – What you'll learn today 02:05 – Why Monitoring as Code? 03:56 – Configurate Dynatrace as Code 07:00 – When to choose Terraform or Monaco? 09:14 – What is Monaco 2.0 11:35 – Commands of Monaco 2.0 13:24 – Projects and Manifests 14:57 – Structured Configuration in Monaco 2.0 19:08 – General Support for Settings 2.0 20:30 – Demo Overview 22:34 – LIVE Demo 48:40 – Outlook 52:00 – Appendix Subscribe to our channel → https://dynatr.ac/subscribeYT Stay up-to-date with Dynatrace! Follow us on: Facebook →   / dynatrace   Instagram →   / dynatrace   LinkedIn →   / dynatrace   Twitter →   / dynatrace   Twitch →   / dynatrace   Have a question about our platform? Visit our Dynatrace Community to connect with our experts and users → https://dynatr.ac/3FYfPB3