Defining request naming rules Globally or at Service level?

Hi @Mikhail A. here is the best approach. Apply Scenario#1 with Service name/id as condition which is similar to creating the rules at Service level in terms of performance. As I mentioned earlier, advantage with this approach is you can duplicate the rules to other Environments using Request naming API. Hope this helps.

I was able to get the following info from dT support team.

  • Either way the naming rules are applied by the cluster after the request have been captured so there is no impact/overhead on the actual Applications.
  • There may be a small performance impact with the loading of the page Settings : Service-side service monitoring : Global request naming rules which contains the list of rules that have been defined through the API. This just affects the actual loading the page and not the rules themselves.
  • The team did emphasize that there is a significant productivity advantage (as you have identified) to being able to use the API on the global request naming rules.
  • We have other customers using 200+ naming rules without issue.
  • Be sure to review the Placeholder object. From our experience there are many case where the number of required rules can be significantly reduced with the correct usage of a placeholder. Request naming API - POST a new request naming rule — Dynatrace Docs