cd_e2e_monitoring_config/onboarding/CD_managementZone/management-zone
qxz15oi 6b69d64273 guidelines / templates redefined 2021-03-31 13:02:29 +02:00
..
README.md guidelines / templates redefined 2021-03-31 13:02:29 +02:00
default.json guidelines / templates redefined 2021-03-31 13:02:29 +02:00
management-zone.yaml guidelines / templates redefined 2021-03-31 13:02:29 +02:00

README.md

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, you will be able to see all your services under Transactions & Services. For many other components, we have been required to exclude some noisy services such as HealthResource, PingResource, PrometheusResource

How to exclude HealthResource?

  1. Open default.json configuration under the management-zone folder
  2. Under the "type": "SERVICE" rule, add one extra condition: { "comparisonInfo": { "caseSensitive": true, "negate": true, "operator": "CONTAINS", "type": "STRING", "value": "HealthResource" }, "key": { "attribute": "SERVICE_NAME" } }The rule 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" }`

Note: you can apply the same logic for PingResource, PrometheusResource or any other entity it's intended to be excluded

  1. 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>