• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home
  • Public Forums
  • Application Monitoring & UEM
  • AppMon & UEM Open Q&A
avatar image
Question by Keith D. · May 24, 2014 at 02:13 AM ·

Question around capturing servlet parameters in Servlet Sensor

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

4 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Christian S. · May 26, 2014 at 08:34 PM

hi Keith & Andi,

I just double-checked to be 100% sure and have to tell you that the documentation is not correct here.

the current (intended) behavior is as follows:

  • if the attribute is set to "*" or "" (empty string), then all headers/parameters/... are captured
  • if the attribute is set to a specific value, then exactly this header/parameter/... will be captured
    • there is no "contains", "starts with" or similar matching
    • request headers are handled case-insensitive

though this will not help you very much for your use case, this is the intended behavior.

more sophisticated behavior could be a potential RFE.

best, Christian

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Keith D. · May 24, 2014 at 02:48 AM

Yes, if I just use *, then all parameters are captured.  The issue then is that we see user credentials on logins, which is a big issue here from a security perspective.  The fact that parameter names are dynamically generated makes it difficult for us to come up with a list of specific parameters to capture, so being able to capture only those parameters that start with a certain string would solve the problem for us.

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Andreas G. ♦ · May 24, 2014 at 03:05 AM 0
Share

I will double check with engineering. But - if this really doesnt work for you i suggest opening a support ticket so that we can track this properly

avatar image

Answer by Keith D. · May 24, 2014 at 02:36 AM

Thanks for your response, Andreas.  I've tried this, but it does not appear to work. I should mention, I am working with a vendor product that generates dynamic names for a lot of the form fields/request parameters.  They all start with ~123~ though, so I am trying to capture those parameters that start with this value.  Is the "~" perhaps causing problems?

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Andreas G. ♦ · May 24, 2014 at 02:43 AM 0
Share

Have you tried keeping the field empty or just using the *? does dT then capture all your parameters with the names you expect?

avatar image

Answer by Keith D. · May 24, 2014 at 02:16 AM

I've seen variations of this question asked in the forum, but the documentation seems a bit ambiguous to me From Sensor Properties:

 

"A captured attribute may be specified explicitly by providing its name in the 'Attribute' column, capturing those that contain a certain name by providing a partial name in the 'Attribute' column or all available attribute may be captured by leaving the 'Attribute' column empty or fill it with '*'. "

 

This seems to imply that you can capture a parameter that contains a certain substring.  Is this the case?  I've tried this, but it doesn't seem to work.

 

Thanks.

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Andreas G. ♦ · May 24, 2014 at 02:22 AM 0
Share

Hi Keith

Yes. This should work. Instead of a partial name - can you try e.g: "*somevalue*". I think the * (asterisk) might be required

Andi

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

1 Person is following this question.

avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A