1.4 KiB
Service Naming Rules
A typical case could be that you access to Transaction & Services and you find two services that are exactly the same: DataDownloadV1 DataDownloadV1
If you drilldown into the service and you check in the process group, you may have a PROD and a E2E for each service.
Note: if you see that both process group are exactly the same, please contact a Dynatrace expert to create a Process Group detection rule
In the case the PG are PROD and E2E, then we need to create a rule that looks like this:
config:
- CDInfotainmentRule1: template.json
CDInfotainmentRule1:
- name: Infotainment Rule 1
- nameFormat: {Service:DetectedName} - {ProcessGroup:KubernetesNamespace/[^-]+$}
- tag: Infotainment
- skipDeployment: false
The rule will get the Service Detected Name (current name) and it will extract (with a regex) the part of the kubernetes namespace after the "-", so -prod or -e2e, resulting in: DataDownloadV1 - prod DataDownloadV1 - e2e
Now, services will be easy to identify.
You can create rules based on any property/metadata. Some other placeholder's eamples: {Service:DatabaseName} - E2E {Service:WebServiceName} - {ProcessGroup:Kubernetes:microservice} - {ProcessGroup:Kubernetes:environment} {Service:DetectedName} - {ProcessGroup:KubernetesContainerName} - {ProcessGroup:KubernetesNamespace/[^-]+$} {Service:DetectedName} - {ProcessGroup:SpringBootProfileName/[^\-]*$}