Configuration as Code

Evolved from the Monitoring as Code CLI we provide Observability and Security as Code to fully automate configuration of the Dynatrace platform at any scale - from automating standard configuration of all your Dynatrace environments to meeting specific demands for individual ones.

Why Configuration as Code?

A Configuration as Code self-service model enables development teams to set up monitoring, observability and security policies quickly and efficiently, even for large-scale applications.

It eliminates the need for building custom solutions and reduces the manual work for observability teams.

The Dynatrace Configuration as Code approach enables you to manage your Dynatrace environment observability tasks through configuration files instead of a graphical user interface.

Configuration files allow you to create, update, and manage your observability configurations safely, consistently, and repetitively. They can be reused, versioned, and shared within your team.

How does it work?

Developers define a configuration file and check it into version control alongside the application’s source code. The code gets built and deployed with the next commit or pull request, automatically creating observability configuration like dashboards, synthetic monitors and alerting.

Features

Configuration as Code can do the following features:

Create configuration templates that can be reused in multiple environments.
Manage interdependencies between configurations without the need to retain unique identifiers.
Apply the same configuration to hundreds of Dynatrace environments and be able to update all of them at the same time.

Promote application-specific configurations across environments after deployments at each stage.
Support all mechanisms and best practices of git-based workflows such as pull requests, merging, and approvals.
Commit your configuration to version control and collaborate on changes.