# URL-based sampling vs excluding web request URLs

**URL:** <https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113>\
**Category:** Open Q&A\
**Tags:** deep-monitoring, services-classic, web-monitoring\
**Created:** [April 12, 2024, 11:41am UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113 "2024-04-12T11:41:14Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [April 12, 2024, 11:41am UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/1 "2024-04-12T11:41:14Z")

</div>

Currently it seems there are two ways how incoming web requests can be excluded from monitoring globally:

1. via setting “Server-side service monitoring → URL-based sampling” and enabling option “Ignore URLs with specific path and/or query parameters”
2. via setting “Server-side service monitoring → Deep monitoring → Exclude specific incoming web request URLs”

Naively, I would say they do exactly the same although option #1 seems a bit more flexible as it allows to match HTTP methods and query parameters and also supports additional scopes (i.e. Process Groups).

So my question: Is there ANY reason one would still be compelled to choose option #2 over #1??

---

<div class="post-metadata">

**Author:** ![marina\_pollehn](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/marina_pollehn/32/39120_2.png) [@marina\_pollehn](https://community.dynatrace.com/u/marina_pollehn)\
**Post date:** [April 15, 2024, 7:02am UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/2 "2024-04-15T07:02:08Z")

</div>

I think it could be the level of when they are ignored, for example at storage or capture (limiting traffic).

Option 1 seems to ignore on capture level, maybe option 2 at storage (I could not find something verifying this yet)?

---

<div class="post-metadata">

**Author:** ![gbaudart](https://avatars.discourse-cdn.com/v4/letter/g/e47c2d/32.png) [@gbaudart](https://community.dynatrace.com/u/gbaudart)\
**Post date:** [April 15, 2024, 7:54am UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/3 "2024-04-15T07:54:28Z")

</div>

Option 1 is more recent. It allows you to completely ignore the capture of an endpoint, but also to simply reduce the capture rate, which can also be beneficial. Note also that if you see that you are unable to capture all of your traffic (ATM Dashboard), you can also configure the capture rate of priority endpoints to be increased (to be sure that they are captured).  
Dynatrace recently recommended using option 1 (url-based sampling) whenever possible (OA higher than v1.279).  
Note that as long as you are able to capture 100% of your traffic (see ATM), the rules of option 1 will not be triggered (this only changes with option 2, which is permanent).

Note that ignored captures are not saved and therefore do not use retention.

You can track the capture rate of an endpoint using the MDA for the ATM

---

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [April 15, 2024, 1:45pm UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/4 "2024-04-15T13:45:34Z")

</div>

> [@gbaudart](https://community.dynatrace.com/user/64996)&nbsp;wrote:
> 
> Note that as long as you are able to capture 100% of your traffic (see ATM), the rules of option 1 will not be triggered (this only changes with option 2, which is permanent).

That seems to contradict the pop-up info text:

 ![Enrico_F_0-1713188675703.png](https://global.discourse-cdn.com/dynatrace/original/2X/4/49a4879e9f232c2e00cb4687701119eeb845dd15.png)

Based on that info I would say there is no reason for choosing option #2 over #1. However, an official confirmation would be helpful.

---

<div class="post-metadata">

**Author:** ![gbaudart](https://avatars.discourse-cdn.com/v4/letter/g/e47c2d/32.png) [@gbaudart](https://community.dynatrace.com/u/gbaudart)\
**Post date:** [April 15, 2024, 1:57pm UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/5 "2024-04-15T13:57:09Z")

</div>

ATM is activated when there is too much traffic to capture. This is when the Url-Based Sampling rules are triggered.  
If the tenant can handle the full load, ATM will not be activated.  
This is what the Dynatrace ACE service told me.

---

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [April 16, 2024, 11:52am UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/6 "2024-04-16T11:52:37Z")

</div>

> [@gbaudart](https://community.dynatrace.com/user/64996)&nbsp;wrote:
> 
> ATM is activated when there is too much traffic to capture. This is when the Url-Based Sampling rules are triggered.  
> If the tenant can handle the full load, ATM will not be activated.  
> This is what the Dynatrace ACE service told me.

It looks like this is only partially true, namely when the option “Ignore URLs with specific path and/or query parameters” is NOT enabled because I just tested it on a tenant that has no active ATM and it seemed the setting was taking effect regardless.

As it stands now I must therefore assume option #2 has become completely redundant as it has been effectively replaced by option #1.

In any case, it would be helpful if this could be officially confirmed by a product manager or dev responsible for this feature.

---

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [April 29, 2024, 8:40am UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/7 "2024-04-29T08:40:26Z")

</div>

It seems there is one rather important difference between the two options:

Option #2 will only ignore the **root-path** &nbsp;of a captured distributed trace for a web request matching the URL pattern while option #1 will additionally ignore all potential&nbsp; **sub-paths** &nbsp;captured by any child-agents in correlated downstream processes.

In other words: With option #2 it might still be possible to see traces for any downstream web requests if their URL is not matched by any configured pattern (i.e. the entrypoint of the captured trace might get pushed downstream).

Disclaimer: This info is based on unofficial feedback we received from a member of the Dynatrace ACE team and not verified.

---

<div class="post-metadata">

**Author:** ![ben\_wrightson](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/ben_wrightson/32/34776_2.png) [@ben\_wrightson](https://community.dynatrace.com/u/ben_wrightson)\
**Post date:** [August 6, 2024, 3:17pm UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/8 "2024-08-06T15:17:40Z")

</div>

[@gbaudart](https://community.dynatrace.com/user/64996)&nbsp;is correct.

> ATM is activated when there is too much traffic to capture. This is when the Url-Based Sampling rules are triggered.  
> If the tenant can handle the full load, ATM will not be activated.

The URL-based sampling rules are indeed only triggered if ATM is active (i.e. there are too many requests to capture them all).

The documentation does not currently reflect that, but that is something that’s being improved at the moment.

---

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [August 12, 2024, 12:48pm UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/9 "2024-08-12T12:48:36Z")

</div>

Not according to my own specific tests for option “Ignore URLs with specific path and/or query parameters”&nbsp;dating back to April 2024 as well as the info given in the UI:

 ![Enrico_F_0-1713188675703.png](https://global.discourse-cdn.com/dynatrace/original/2X/4/49a4879e9f232c2e00cb4687701119eeb845dd15.png)

Has anything changed in this regards since OA 1.287 ?

---

<div class="post-metadata">

**Author:** ![ben\_wrightson](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/ben_wrightson/32/34776_2.png) [@ben\_wrightson](https://community.dynatrace.com/u/ben_wrightson)\
**Post date:** [August 12, 2024, 1:37pm UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/10 "2024-08-12T13:37:44Z")

</div>

You’re right, if you choose “Ignore URLs…”, then that is independent of Adaptive Traffic Management (ATM) and is applied always (then the dropdown to reduce the capturing factor also disappears).&nbsp;  
If you don’t turn on “Ignore URLs…” then the configured sampling kicks in only after ATM is active.

---

<div class="post-metadata">

**Author:** ![kuncarlos](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/kuncarlos/32/32091_2.png) [@kuncarlos](https://community.dynatrace.com/u/kuncarlos)\
**Post date:** [July 30, 2025, 7:18am UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/11 "2025-07-30T07:18:04Z")

</div>

Has this been updated in the docs as of July 2025?

---

<div class="post-metadata">

**Author:** ![ben\_wrightson](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/ben_wrightson/32/34776_2.png) [@ben\_wrightson](https://community.dynatrace.com/u/ben_wrightson)\
**Post date:** [July 30, 2025, 12:52pm UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/12 "2025-07-30T12:52:33Z")

</div>

The docs now (July 2025) say:

> If OneAgent is sampling and the capture rate is below 100%, you can advise OneAgent on the importance of specific HTTP and RPC requests in relation to others.

([Adaptive Traffic Management with Dynatrace Platform Subscription (DPS) — Dynatrace Docs](https://docs.dynatrace.com/docs/shortlink/url-sampling))  
So I’d say it’s clearer now that these settings only apply if the OneAgent is already sampling.

---

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [July 30, 2025, 1:01pm UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/13 "2025-07-30T13:01:23Z")

</div>

The only exception is the option “Disable tracing for matching HTTP requests”, which - according to the UI and doc - applies ALWAYS, even when the OneAgent is NOT sampling:

 ![Enrico_F_0-1753880452678.png](https://global.discourse-cdn.com/dynatrace/original/3X/d/3/d3253b451dc9fd64cf6fe3e1abe392936917fe61.png)

---

<div class="post-metadata">

**Author:** ![dave\_vos](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@dave\_vos](https://community.dynatrace.com/u/dave_vos)\
**Post date:** [November 14, 2025, 8:52am UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/14 "2025-11-14T08:52:00Z")

</div>

Hi, I have a question. A customer wants to use Dynatrace but DT must ignore specific web requests that contain sensitive data (names,etc). I managed to establish this with "2. via setting “Server-side service monitoring → Deep monitoring → Exclude specific incoming web request URLs”. However it appears that this does not work if the URL is in a sub-path. I tried the other option 1. via setting “Server-side service monitoring → URL-based sampling” and enabling option “Ignore URLs with specific path and/or query parameters”, but that did not work as well. Is there any solution for this problem?

---

<div class="post-metadata">

**Author:** ![AntonioSousa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antoniosousa/32/50_2.png) [@AntonioSousa](https://community.dynatrace.com/u/AntonioSousa)\
**Post date:** [June 27, 2026, 4:58pm UTC](https://community.dynatrace.com/t/url-based-sampling-vs-excluding-web-request-urls/45113/15 "2026-06-27T16:58:19Z")

</div>

Please notice that if you have OneAgent \>= 1.331, the default behavior has changed. With my experiences, these configurations are now much better!
