10 Feb 2023 07:58 AM - last edited on 10 Feb 2023 02:10 PM by Radoslaw_Szulgo
What's the best practice for migrating process-group detection rules?
Solved! Go to Solution.
10 Feb 2023 01:59 PM - edited 10 Feb 2023 02:03 PM
Dynatrace detects which processes are part of the same process groups using a default set of detection rules. Simple process-group detection rules enable you to adapt the default process-group detection logic for deep-monitored processes via Java system properties or environment variables.
We recommend utilizing Configuration-as-code to migrate process-group detection rules.
Evolved from the Monitoring as Code CLI (aka Monaco), we provide Observability and Security as Code to fully automate the configuration of the Dynatrace platform at any scale - from automating the configuration of all your Dynatrace environments to meeting specific demands for individual ones. Read more here: https://www.dynatrace.com/support/help/shortlink/configuration-as-code
How to?
Using Configuration-as-code, you can either download and deploy all configurations or focus on process-group detection rules configuration. In the simplest scenario it could look like that:
1. Download your process-group detection rules:
|
2. Validate configuration files and skip deployment. It will check whether your Dynatrace configuration files are valid JSON and whether your tool configuration yaml files can be parsed and used:
monaco deploy --dry-run
|
3. Deploy configurations to the environment(s) defined in a given deployment manifest file.:
monaco deploy
|