cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

URL Exception added to exclusion list but not being excluded

melissap
Guide

Hi

I've added a URL exclusion to the web server exclusion list (since the web request is taking place on the Apache) however this exclusion is not working however I've added exclusions for images and that is working fine.

URL is a .jsp - match is currently on equal but I have tried all matches and that doesn't work.

Please help.

Thanks!
Melissa

12 REPLIES 12

Joe_Hoffman
Dynatrace Leader
Dynatrace Leader

Melissa,

Can you show us the URL pattern from the Purepath dashlet or Web Request Dashlet, as well as show us the Exclusion rule you wrote.

I'm also curious as to whether the Apache instance is the correct tier for the exclusion. Perhaps the transaction is really going into the Java tier directly?

Keep in mind that exclusion rules take a few transactions to take affect as transactions in flight are still being processed thru the system. I assume you've waited several minutes to ensure your exclusion really was not working as expected.

melissap
Guide

Hi Joseph

URL pattern is /vitalitypartners/login.jsp
Exclusion rule is


I've excluded this is the Web Server exclusion as well as on the other agent groups on the java web Request exclusions.

I implemented this a couple days a go and it's still appearing.

c_schwarzbauer
Dynatrace Champion
Dynatrace Champion

hi Melissa,

based on your screenshot above:

  • you should check the checkbox on the very left (if you didn't already) to make this exclusion active
  • you should switch "equals" to "ends" as I'm pretty sure that the URL will not equal this pattern

HTH,
Christian

rmg
Organizer

I am also having the same issue.

The purepath I try to exclude end with "services/Version"

I add the excluding rule on both Java Web Request and Servlets. But it doesn't seem to exclude the /services/Version after I bounced the SUDs.

I notice that this servlet come from "org.apache.axis.transport.http.AxisServletBase"

Thanks,

-Ronald

c_schwarzbauer
Dynatrace Champion
Dynatrace Champion

could you show us also a screenshot of the PurePath that should be excluded, including the URL, please.

Christian

rmg
Organizer

Hi Christian,

This is the URL needs to be excluded. The screen earlier screen shot is the exclusion rule in servlet and java web request properties.

I would think that having exclusion rule in both servlet and java web request would have done the job. But it doesn't seem to be so.

Thanks,

-Ronald

c_schwarzbauer
Dynatrace Champion
Dynatrace Champion

mhm, interesting. do you maybe have a loadtesting script executing those requests with an added X-dynatrace header?

could you also show us the details of the web request node in the PurePath or maybe attach a session containing such a PurePath?

Christian

rmg
Organizer

Hi Christian,

No, I don't have any loadtesting script with added X-dynatrace header for this application. It is supposed to be a backend application.

I can't add the purepath session in here since it only allow file less than 1MB.

The purepath has only one method. (see below)

Node Details
Method: service(javax.servlet.http.HttpServletRequest req, javax.servlet.http.HttpServletResponse resp)
Class: org.apache.axis.transport.http.AxisServletBase
Argument:
Return:
Agent: dTa-perf-dsliveblk-pe-corp-xxx-xxx@pe-corp-xxx-xxxx.perf.autc.com:5038
API: Java Web Services
Thread Name: ajp-0.0.0.0-8109-2 <998342083>
Elapsed Time [ms]: 0.00

Time Details Total Exec %
Execution Time [ms]: 0.22 0.22 100.00
CPU Time [ms]: 0.22 0.22 100.00
Sync Time [ms]: - - -
Wait Time [ms]: - - -
Runtime Suspension Time [ms]: - - -
Source Information
File Name: AxisServletBase.java Statement number: 324

Web Service Details
C/S: S
End point or Class: -
Namespace or Method: -
HTTP Tag: -
Request Bytes: - Response Bytes: -

c_schwarzbauer
Dynatrace Champion
Dynatrace Champion

hi Ronald,

is that the only detail information on that node? because I'm missing the web request details in there. in this case it could be that you have a custom sensor on this method which is still creating this PurePath.

could you take a look in the agents overview -> deployed sensors, search for this method and then look at the column 'Sensors'. would be interesting to know which sensor(s) you see in there. if you see more than just 'servlet', then you have a custom sensor on that method (probably set to 'active and start PurePath') which creates this PurePath.

I would be a little confused that the PurePath name is still set to the URL, but this might still be the issue.

HTH, Christian

rmg
Organizer

Yes, that's the only detail information on that particular purepath. I look into the sensor from agent overview -> deployed sensors, and found the detail method that matches the sensor (see below). This doesn't seem like a custom sensor at all.

Details
Method: service
Class: org.apache.axis.transport.http.AxisServletBase
Arguments: javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse
Returns: void
Sensor: Webservice, Servlet
Flags: Pro
Source File: AxisServletBase.java
Line Number: 324

Thanks,

-Ronald

c_schwarzbauer
Dynatrace Champion
Dynatrace Champion

ok, based on this I'd say it's the web service sensor that starts the PurePath here. I suggest setting the web service sensor to active only and see what happens.

HTH, Christian

rmg
Organizer

Hi Christian,

Thanks. Looks like this resolve the issue. Before, I was having performance warehouse connection issue which couldn't update my sensor configuration.

Thanks,

-Ronald