# Key requests filtering is not possible with bg-deploy

**URL:** <https://community.dynatrace.com/t/key-requests-filtering-is-not-possible-with-bg-deploy/41682>\
**Category:** Open Q&A\
**Tags:** sap, extensions, key-requests\
**Created:** [September 18, 2023, 3:12pm UTC](https://community.dynatrace.com/t/key-requests-filtering-is-not-possible-with-bg-deploy/41682 "2023-09-18T15:12:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![BoazW](https://avatars.discourse-cdn.com/v4/letter/b/a3d4f5/32.png) [@BoazW](https://community.dynatrace.com/u/BoazW)\
**Post date:** [September 18, 2023, 3:12pm UTC](https://community.dynatrace.com/t/key-requests-filtering-is-not-possible-with-bg-deploy/41682/1 "2023-09-18T15:12:36Z")

</div>

Hi,

After we have changed our deployment to bg-deploy, the key requests that were defined in our Dynatrace environment have stopped functioning, because they depend on the service Id, which changes every deployment.

Therefore, we request that the key requests will be based on the service **name** instead of the Id.

Kindly assist

Thanks,  
Boaz

---

<div class="post-metadata">

**Author:** ![JamesKitson](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jameskitson/32/22460_2.png) [@JamesKitson](https://community.dynatrace.com/u/JamesKitson)\
**Post date:** [September 19, 2023, 11:56am UTC](https://community.dynatrace.com/t/key-requests-filtering-is-not-possible-with-bg-deploy/41682/2 "2023-09-19T11:56:58Z")

</div>

I moved this to the Dynatrace Open Q&A because service detection is not related to or handled by extensions.

Key requests have to be associated with a single service and service names are not guaranteed to be unique, so grouping them by a service name is not an option. You may need to look at some of the service detection options that are available to find a way of ensuring that new services are not detected in such scenarios where you would prefer to keep them the same.

> **[Service Detection v1](https://docs.dynatrace.com/docs/observe/application-observability/services/service-detection/service-detection-v1)**
>
> Find out how Dynatrace Service Detection v1 detects and names different types of services.

---

<div class="post-metadata">

**Author:** ![BoazW](https://avatars.discourse-cdn.com/v4/letter/b/a3d4f5/32.png) [@BoazW](https://community.dynatrace.com/u/BoazW)\
**Post date:** [September 21, 2023, 3:10pm UTC](https://community.dynatrace.com/t/key-requests-filtering-is-not-possible-with-bg-deploy/41682/3 "2023-09-21T15:10:21Z")

</div>

Hi James,

We have a service naming rule, which aggregates all the blue-green services to a single service. Hence, we were expecting that the key request feature will work, because the service name is unique. The filtering is important for us, because we need to opt-out irrelevant customer-related info.

---

<div class="post-metadata">

**Author:** ![tim\_gerlach](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tim_gerlach/32/18295_2.png) [@tim\_gerlach](https://community.dynatrace.com/u/tim_gerlach)\
**Post date:** [March 7, 2024, 11:35am UTC](https://community.dynatrace.com/t/key-requests-filtering-is-not-possible-with-bg-deploy/41682/4 "2024-03-07T11:35:46Z")

</div>

Hi&nbsp;[@JamesKitson](https://community.dynatrace.com/user/6226)&nbsp;,

Thanks for your idea to use service naming rules.

Unfortunately, I don’t think it will solve this case, because configuring a key request requires the Service ID.

Generally speaking,&nbsp;we believe that the only way to make “key requests” transportable (config as code) will be to allow mapping key requests to services by some filters or rules since the Service ID is not stable enough.

I’m wondering how Dynatrace attempts to approach this problem with monaco?

---

<div class="post-metadata">

**Author:** ![thorsten\_roth](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thorsten_roth/32/26774_2.png) [@thorsten\_roth](https://community.dynatrace.com/u/thorsten_roth)\
**Post date:** [April 17, 2024, 6:49am UTC](https://community.dynatrace.com/t/key-requests-filtering-is-not-possible-with-bg-deploy/41682/5 "2024-04-17T06:49:22Z")

</div>

Hello,

we are currently working on a solution to remove the above-mentioned limitations.

Here in a nutshell what you can expect:

- No longer having a key request subscription approach, as endpoints will completely replace this.
- No dependency between service ID and endpoint.
- New endpoint detection rule (related to the span attributes), enables monitoring as code.
- And much much more

The goal is to provide superb out of the box experience and detection (services & endpoints) with zero or less config effort. In case modifications are needed, then this is of course doable.

There is no final ETA yet, but we’re already working on it.

Thanks,  
Thorsten
