Traces: Filtering out Requests executed in background threads

[gilles_tabary]

Hello all.

I am on Managed 1.336. I have a service : Requests executed in background threads of cont.my_process_group . Dynatrace captures traces like : http://localhost:0000/access/api/v1/system/readiness. I need to not capture these traces i.e. filter them out. I tried:

Settings : Server-side service monitoring > 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 service.

Any one got sucess ?

Regards.

[MaximilianoML]

Hello, @gilles_tabary 

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.

[gilles_tabary]

I have a ticket indeed.

[Julius_Loman]

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.

[gilles_tabary]

---

@Julius_Loman wrote:

... you can turn off the Java threading OneAgent feature for the process group.

---

Would this preserve standard "real" request capture ?

[Julius_Loman]

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

[gilles_tabary]

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. 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.

[Julius_Loman]

@gilles_tabary 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.

[gilles_tabary]

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.