Requesting Confirmation that it is not possible (in DT 5.6) to capture specific request Parameter or Session Attribute or
Since the doc states that instrumenting with all may introduce overhead, I hope that I am just misunderstanding the doc.
Our application is a Java Application running on WebSphere 8.x .
Used the following approach from the doc referring to attributes and tried to apply it to Parms and Session attributes with no luck
Parameters and Attributes ( ): Capture values of certain parameters & attributes (i.e. Request Headers, Session Attributes, Request Attributes, Request Parameters) as Strings. 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 '*'. See screenshot on the left side.
Complete Details contained in attached doc:
Hi Mary Ann
IT IS possible to capture these types of things. You can capture all Session Attributes, Parameters or Headers. The thing that was discussed on that forum topic is capturing a specific Cookie. You can capture all Cookies by specifying to capture the Cookie HTTP Request Header. That will capture all cookies. You can then use our special Web Request Header Measures to extract a single cookie value. This is a little more convenient for ASP.NET but still works for Java
If I understand your question correctly though you are looking into general Parameters and attributes. This should work just fine by adding the names to the Servlet Sensor Settings. The following is a screenshot showing how to capture this type of data. This configuration will capture
- the HTTP Request Parameter "username" (regardless whether posted as GET or POST parameter)
- capture the value that getUsername() returns from the session object with the name user
- capture all Request Headers
Once you make these changes NEW PurePaths will capture this information on the Servlet Nodes such as doFilter, doGet, service. So - after you make the change look at your new PurePaths that just came in and click on the Details on one of these Servlet specific nodes
If you want to learn more - we have a recorded webinar on how to capture additional Context Information with dynaTrace. It also covers capturing Servlet data: http://apmuonline.compuwareapm.com/mod/page/view.php?id=15627
Thanks, I have been able to specify both specific request params and specific session attributes EXCEPT for the if I have a request parameter named searchCriteria.CarrierCode. The "." special character seems to cause an issue (as if it was being interpreted as an accessor)
Handling other special characters works fine (grid_rec2_0 works fine, for example).
Do you have a recommendation for this?
Hi
Is the parameter really called "searchCrtiera.CarrierCode"? If that is the case I got a question for you: Can you try and specify a *? I want to know whether we can capture that parameter if we instruct the servlet sensor to capture all parameters. If it works like that but not with specifying the full name including the . (dot) in the name then I suggest you open a support ticket.
Andi
Andi, yes, if I specify "*" for all request params, the tool returns it properly (see below). It seems as if it is treating the "." as an instruction to use an accessor for request params.....
BTW, I tried the following without success: searchCriteria.carrierCode, "searchCriteria.carrierCode", searchCriteria*, searchCriteria/.carrierCode.
ANy news, Andi?
