# report for service requests based on dynamic request content

**URL:** <https://community.dynatrace.com/t/report-for-service-requests-based-on-dynamic-request-content/21564>\
**Category:** Open Q&A\
**Tags:** services-classic\
**Created:** [February 23, 2021, 12:16pm UTC](https://community.dynatrace.com/t/report-for-service-requests-based-on-dynamic-request-content/21564 "2021-02-23T12:16:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rswarnka](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/rswarnka/32/10979_2.png) [@rswarnka](https://community.dynatrace.com/u/rswarnka)\
**Post date:** [February 23, 2021, 12:16pm UTC](https://community.dynatrace.com/t/report-for-service-requests-based-on-dynamic-request-content/21564/1 "2021-02-23T12:16:57Z")

</div>

Hi, we are looking to get the count and response time for dynamic web requests by capturing & bucketing by the dynamic value. Looks like there are is challenge with this:

1. global privacy setting to mask client IP addresses, URIs, and HTTP post parameters is on, hence the dynatrace is masking the dynamic part of the web/service request

Is there a workaround to configure this ? Please see screenshot:

The request pattern is something like:

```auto
/sites/ESCNNNNNN/.*/.*.aspx

```

 ![28326-1614082498031.png](https://global.discourse-cdn.com/dynatrace/original/3X/5/f/5ff98e73f671b48739f4e051d055e3a2d359d01f.png)

---

<div class="post-metadata">

**Author:** ![adam\_gardner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/adam_gardner/32/20087_2.png) [@adam\_gardner](https://community.dynatrace.com/u/adam_gardner)\
**Post date:** [February 24, 2021, 5:54am UTC](https://community.dynatrace.com/t/report-for-service-requests-based-on-dynamic-request-content/21564/2 "2021-02-24T05:54:53Z")

</div>

Create a request attribute (RA) to grab that portion of the URL. During creation there’s a checkbox that allows the RA to access unmasked data. This process is similar to what you’ve already done for your Business Transaction RA.

Then create a calculated service metric (settings \> server-side service monitoring \> calculated service metrics) with a condition where your request attribute exists. Split by the request attribute itself.

At this point you have a metric split by each request attribute value (eg. ESC111511) and you can chart it using hte Metrics view and / or alert on it using “custom events for alerting” (settings \> anomaly detection \> custom events for alerting)