cd_e2e_monitoring_config/BMW-Dynatrace-config/CD_lsc-hr/management-zone

Management Zones configuration

Excluding noisy services

If you find services that are not relevant for the analysis, you can exclude them from the MZ.

HealthResource, PingResource, PrometheusResource services

After the deployment of the OneAgent, your services should appear under Transactions & Services. A good practice would be to exclude the ones that are not relevant for monitoring. i.e. For some BMW's teams, HealthResource, PingResource, PrometheusResource have been excluded.

How to exclude HealthResource?

1. Open the file default.json configuration under the CD_<app_name>/management-zone/ folder.
2. Copy the following rule template:

   {
    "comparisonInfo": {
     "caseSensitive": true,
     "negate": true,
     "operator": "CONTAINS",
     "type": "STRING",
     "value": "HealthResource"
    },
    "key": {
     "attribute": "SERVICE_NAME"
    }
   }
   

3. Add it under the "type": "SERVICE" rule's conditions. It should look like this:

{
 "conditions": [
  {
   "comparisonInfo": {
    "negate": false,
    "operator": "EQUALS",
    "type": "TAG",
    "value": {
     "context": "CONTEXTLESS",
     "key": "Component",
     "value": "{{.tag}}"
    },
    {
   "comparisonInfo": {
    "caseSensitive": true,
    "negate": true,
    "operator": "CONTAINS",
    "type": "STRING",
    "value": "HealthResource"
   },
   "key": {
    "attribute": "SERVICE_NAME"
   }
  }
   },
   "key": {
    "attribute": "SERVICE_TAGS"
   }
  }
 ],
 "enabled": true,
 "propagationTypes": [
  "SERVICE_TO_PROCESS_GROUP_LIKE",
  "SERVICE_TO_HOST_LIKE"
 ],
 "type": "SERVICE"
}
  ```
  
3. Commit and pull request to merge the branch to the master:
  ```
  git add <changes>
  git commit -m "<app_name> configuration changes"
  git push -u origin <branch>
  ```
Note: you can use the same logic to exclude (or include) any other entity to your Management Zone.