This folder is a reference implementation for onboarding applications into Dynatrace using Git, Azure DevOps, Ansible, and Dynatrace Monaco.
The Payment application is the reference workload: a Java service running on AWS EC2, monitored by Dynatrace OneAgent, using an AWS Environment ActiveGate to reach Dynatrace SaaS.
Application team
|
| pull request
v
payment-onboarding/<app>-<env>.yaml
|
v
Azure DevOps pipeline
|
+--> Validate onboarding contract
|
+--> Ansible --> EC2 --> OneAgent
| host group / network zone / host tags
|
+--> Monaco --dry-run
|
+--> Protected production environment approval
|
+--> Monaco deploy --> Dynatrace SaaS configuration
EC2 OneAgent --> Environment ActiveGate --> Dynatrace SaaS
Dynatrace/
├── README.md
├── monaco.md # consumer onboarding guide
├── azure-pipeline.yaml # Azure DevOps pipeline
├── payment-onboarding/
│ └── payment-prod.yaml # reference onboarding contract
├── ansible/
│ ├── ansible.cfg
│ ├── inventory/
│ │ └── prod.ini.example
│ ├── install-oneagent.yaml
│ └── roles/
│ └── oneagent/
│ ├── defaults/main.yaml
│ └── tasks/main.yaml
├── monaco/
│ ├── manifest.yaml
│ └── payment/
│ ├── config.yaml
│ ├── management-zone.json
│ ├── maintenance-window.json
│ └── slo.json
└── scripts/
└── validate-onboarding.py
| Layer | Tool | Purpose |
|---|---|---|
| AWS infrastructure | Terraform / cloud platform tooling | EC2, security groups, ActiveGate infrastructure |
| Host monitoring | Ansible + OneAgent | install OneAgent and apply host-level metadata |
| Dynatrace configuration | Monaco | management zones, maintenance windows, SLOs and other tenant configuration |
| CI/CD governance | Azure DevOps | validation, approvals, secret handling and deployment |
| Access | Dynatrace IAM / corporate IdP | user/group permissions and least privilege |
Do not commit Dynatrace tokens, OAuth client secrets, SSH private keys, or cloud credentials. Store secrets in Azure DevOps secret variables or Azure Key Vault.
The examples expect these secret/runtime values to be supplied by the pipeline:
DT_ENV_URL - Dynatrace platform environment URL, for example https://<environment>.apps.dynatrace.comPLATFORM_TOKEN - Dynatrace platform token with only the scopes required by the configurations being deployedDT_ONEAGENT_INSTALLER_URL - controlled OneAgent installer URL or internal artifact URLDT_ONEAGENT_INSTALLER_TOKEN - optional download token when required by your delivery mechanismscripts/validate-onboarding.py.monaco deploy --dry-run monaco/manifest.yaml.deployment job bound to a protected Environment.monaco deploy monaco/manifest.yaml.monaco deploy --dry-run validates the Monaco manifest, projects and resolved configuration. It does not make changes to Dynatrace. The actual monaco deploy stage performs the deployment.
The Payment example intentionally uses application metadata and tags as the stable contract. Do not build reusable configuration around transient Dynatrace entity IDs.
See monaco for the step-by-step procedure that another application team should follow. visit my repo: Github
My Page: Observability
Dynatrace : Main Page