Question around capturing servlet parameters in Servlet Sensor
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.
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
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?
Have you tried keeping the field empty or just using the *? does dT then capture all your parameters with the names you expect?
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.
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
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
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
