# Defining request naming rules Globally or at Service level?

**URL:** <https://community.dynatrace.com/t/defining-request-naming-rules-globally-or-at-service-level/21065>\
**Category:** Dynatrace API\
**Tags:** services-classic, dynatrace-api\
**Created:** [December 14, 2020, 11:35pm UTC](https://community.dynatrace.com/t/defining-request-naming-rules-globally-or-at-service-level/21065 "2020-12-14T23:35:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![sureshKumarK](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/sureshkumark/32/11469_2.png) [@sureshKumarK](https://community.dynatrace.com/u/sureshKumarK)\
**Post date:** [December 15, 2020, 6:22pm UTC](https://community.dynatrace.com/t/defining-request-naming-rules-globally-or-at-service-level/21065/5 "2020-12-15T18:22:58Z")

</div>

Hi [@Mikhail A.](https://answers.dynatrace.com/users/28656/view.html) 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](https://www.dynatrace.com/support/help/shortlink/api-request-naming-post-new#parameters)

---

_[View the full topic](https://community.dynatrace.com/t/defining-request-naming-rules-globally-or-at-service-level/21065)._
