# Traces: Filtering out Requests executed in background threads

**URL:** <https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723>\
**Category:** Dynatrace Managed\
**Tags:** distributed-traces-classic, dynatrace-managed\
**Created:** [April 27, 2026, 1:02pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723 "2026-04-27T13:02:25Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\
**Post date:** [April 27, 2026, 1:02pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/1 "2026-04-27T13:02:25Z")

</div>

Hello all.

I am on Managed&nbsp;1.336. I have a service :&nbsp;Requests executed in **background** threads of cont.my\_process\_group . Dynatrace captures traces like :&nbsp;[http://localhost:0000/access/api/v1/system/readiness](http://localhost:0000/access/api/v1/system/readiness). I need to **not** capture these traces i.e. filter them out. I tried:

Settings :&nbsp;Server-side service monitoring \>&nbsp;Trace sampling for HTTP requests

- Path Equals readiness for any HTTP method is ignored
- Path Ends with /readiness for any HTTP method is ignored

Does not work. Traces still captured. I tried at all possible scopes : host groupe, process group… Nothing works. Note : no problem to filter out traces on non ~~background~~ &nbsp;service.

Any one got sucess ?

Regards.

---

<div class="post-metadata">

**Author:** ![MaximilianoML](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/maximilianoml/32/25038_2.png) [@MaximilianoML](https://community.dynatrace.com/u/MaximilianoML)\
**Post date:** [April 27, 2026, 2:24pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/2 "2026-04-27T14:24:08Z")

</div>

Hello, [@gilles\_tabary](https://community.dynatrace.com/user/27360)

I would first try matching the full path **/access/api/v1/system/readiness** , not only readiness. However, since this is a Requests executed in background threads service, it may not be treated the same as a standard incoming HTTP service. These services represent background activity from the process group, often outbound calls, so URL-based HTTP sampling rules can behave differently. If the same rule works on normal services but not here, I would raise it with Support with a trace example, because it may be a limitation or classification issue for background-thread traces.

---

<div class="post-metadata">

**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\
**Post date:** [April 27, 2026, 2:32pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/3 "2026-04-27T14:32:04Z")

</div>

I have a ticket indeed.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [April 27, 2026, 6:57pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/4 "2026-04-27T18:57:40Z")

</div>

As of now, you can only mute it. Since this is part of the background thread sensors, the URL exceptions do not apply; it’s in fact not a url, just the request is named as such. If you do not want to capture any request in a background thread, you can turn off the Java threading OneAgent feature for the process group.

---

<div class="post-metadata">

**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\
**Post date:** [April 29, 2026, 9:34am UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/5 "2026-04-29T09:34:07Z")

</div>

> [@Julius\_Loman](https://community.dynatrace.com/user/3364)&nbsp;wrote:
> 
> … you can turn off the Java threading OneAgent feature for the process group.

Would this preserve standard “real” request capture ?

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [April 29, 2026, 3:11pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/6 "2026-04-29T15:11:44Z")

</div>

Yes just not those background threads. Web services, web requests or messaging services will still work as those are different sensors.

---

<div class="post-metadata">

**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\
**Post date:** [April 29, 2026, 4:12pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/7 "2026-04-29T16:12:21Z")

</div>

Thanks for feed-backs.

My concern is threefold : those background traces

- generates lots of “noise” : make it difficult to dig through (let’s say) actual real business requests
- they consume DDU licences
- the fresh captures, will pop oldest captured traces and / or shorten traces retention time

Are these statement corrects ?

This is why I am wondering how to not capture them.

---

<div class="post-metadata">

**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\
**Post date:** [April 29, 2026, 5:00pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/8 "2026-04-29T17:00:22Z")

</div>

~~Turned off OneAgent feature java thread at Process Group level + process restart =\> zero service traces captured any more. I.e. not only background req are not captured but also all other are also not captured.~~ &nbsp;My mistake: deep monitoring was turned off entirely on that PG.

Yet. Now : I have deep monitoring on, OneAgent feature java threading off (at PG level) : still backgroud req are captured.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [May 3, 2026, 7:25pm UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/9 "2026-05-03T19:25:58Z")

</div>

[@gilles\_tabary](https://community.dynatrace.com/user/27360)&nbsp;I see there is now a separate OneAgent feature for that:, check “Background Requests for Services (HTTP/GRPC)” . Last time I did this, this was not yet available.

---

<div class="post-metadata">

**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\
**Post date:** [May 4, 2026, 9:32am UTC](https://community.dynatrace.com/t/traces-filtering-out-requests-executed-in-background-threads/55723/10 "2026-05-04T09:32:34Z")

</div>

Obvious. Why didn’t I see it ?! Jes… ! My web / ChatGPT / Doc searches did not yield this answer.&nbsp;😂&nbsp;Thanks.
