Showing results for 
Show  only  | Search instead for 
Did you mean: 

Losing keyrequests, namingrules, dashboards while services are functionally the same


Our supplier changed underlying technology of java application from Jetty to Tomcat.

Everything else stays the same.

But Dynatrace detects new procesgroups and then also new services.

This throws away all our namingrules and, even more important, the keyrequests and their history.

Not to think of all the dashboards that need adjustment because of this.

Question: is there a way to avoid this?




Frequent Guest

Hello Henri,

first of all you can use "Request naming API" instead of manually configure request naming. This approach gives you some advantages:
-in the case of case of new service detection, NR automatically apply in new service
-you can use one rule in multiple services
-you have control over you all rules in one place
-you can easy transfer rules to different environment(TEST/PROD)
The second part is more tricky, if you base on automatic detection rules and some significant change is happen(like technology change) dynatrace may create new service. You can use "Service naming rules" and define your own services. This approach gives you more control over services and you can avoid create new services in case of some changes, but when you apply new rule in your environment you create new service.
You are wrong about Key Requests History, it is avaiable. Once Service is detected it is never deleted from Dynatrace and Key Request in this service is available to check historically.
Key request is assigned to service and if new service is created you have to create new Key Request(unfortunately). You can use schema API to transfer definition of KeyRequests from old service.
Service naming rules | Dynatrace Docs
Settings API - GET a schema | Dynatrace Docs
Request naming API - POST a new request naming rule | Dynatrace Docs
Best Regards

Thanks Michael for your comments.

The old services were there for few years and merged through the deprecated Service Merging.

In the new situation we use the Full webrequest rules so next changes will have less influence on it.



By the way, Michael, it seems that Request Naming API is only for global naming rules.

At the moment I see no possiblility to extract naming rules on a specific service via API.



Featured Posts