How to see payload and header from Webpages requested?
Hi everyone,
Is there a way to see the payload and header from the pages that are showed in Web Requests?
Tks,
So there is no "out of the box" way of getting a correlation ID from the body of a post?
Not yet. But this feature is coming with Dynatrace 6.3 where you can parse any type of content of HTML responses through our JavaScript Agent - meaning - we can capture this on the browser!
Hi @Andreas, quick question: since Dynatrace 6.3 has been out for quite some time now, in your comment, were you referring to the MetaData capturing capability of the Javascript agent? Thanks a lot!
Valerio
Correct. it allows you capture content of HTML Elements identified via a CSS Selector. You can also capture the return value of a global JavaScript object or the content of a META Tag
How would one go about capturing the POST payload of a web request? I see for Request header, response header, and request parameter. Is it request parameter? Or is that only for the suffix after a URI like this www.example.com/index.php?<this part>
Dynatrace can only capture HTTP Parameters - for both GET and POST Requests. But if your POST body is e.g: XML or something other protocol then Dynatrace doesnt capture the full body. If you want to extract certain data out of the body you should try to capture it on the server-side code execution by defining sensors for methods that are processing the individual data parts of the POST BODY
Andi
Wildcard each of those choices. Then make sure you are looking at the details of a PurePath that is a POST request, not a GET request. When I first tried to figure this out myself, I was confused because it seemed like it worked for some PurePaths and not for others. Then I noticed (duh!) that some PP's were for GETs (thus no POST data).
Hi guys,
I did set the servlet configuration, but I am getting only the header... I am not seeing any payload information.
PS.: When I setted it, there were only four choices: Request Parameter, Request Attribute, Session Attribute and Request Header. Should I have more options?
tks
Check the description in Sensor Properties for more information on the ASP.NET and Servlet Sensor Configuration Options
Hi guys,
Thank you very much for answers!
But, I got another issue... I do not know if would be the best way to create another topic...
So, I need to do that in the web service agent (Apache one) to handle the these requests, but when I do the Hot Sensor Placement dT comes with that msg:
Performing Hot Sensor Placement on the agent 'agent_name:port' can lead to spurious crashes. Are you sure to perform a Hot Sensor Placement for this agent?
Is it a problem?
Hi Rafael
The Web Server Agent actually doesnt allow a Hot Sensor Placement. Is it possible you try this on your Application Server that also plays web server?
As this is a different topic feel free to create a new discussion topic on this - and - if you have more details on why you want to do a hotsensorplacement on your web server please let us know
Andi
Hi Andreas,
I wanted it because the apache is the frontend of the application, but even when I try to do it in the agents placed in the weblogic I get the same error.
Have you seen it before? Is it possible dT crashes the server?
I talked with the engineers.
This is a warning message we show on JRockit VMs only. The guys from JRockit told us that Hot Sensor Placement works - but - that there might be problems due to the JRockit Implementation.
In general there should be no problem. We placed this warning message just to let you know that there could be a problem.
Two items
a) I asked our engineers to make this warning message more descriptive
b) The advice from our engineers is that you can definitly do a Hot Sensor Placement in Pre-Prod. But be careful or ommit in Production Environments
Andi
Edit the servlet/ASP.NET sensor configuration in your system profile for the appropriate agent group. There is a table that allows you to specify which parameters you want to capture. You can use an asterisk to wildcard. There are different types of sources: cookies, headers, etc. You want "parameters" as your source. Be aware that it's not advised to wildard where you end up capturing all parms/values for all pages in a busy production environment.
I have small environment for testing and with the wildcarding, I capture all POST fields and their values in my PurePaths.
To see the captured values, right-click on the first method (web GET/POST entry point) in your PurePath and select details.
Ryan is right. I thought you need the response payload - thats why I told you to use the Browser Agent. For request parameters you should use the capture option we have for Servlet and ASP.NET
Hi Andi,
We don't have Browser Agent .
Can we capture Request Payload data in Purepath without Browser Agent?
Please find attached snapshot.
Regards,
Jalpesh Shelar
What exactly are you trying to see? You can capture quite a bit of information about the HTTP requests, including the headers, POST'ed data, cookies, etc. But this is for the incoming HTTP requests only.
Hi
The payload itself can only be captured using the dynaTrace Browser Agent. The Browser Agent is a browser add-on for IE and FF and captures Network Traffic (Headers + Body), JavaScript Execution, DOM Access and REndering Activity. It is comparable with the dynaTrace AJAX Edition whereas it provides specific additional features for cross browser testing, comparison and test automation. So - capturing Headers and Body Payload works with the Browser Agent and is suited for Pre-Production (Test, Dev, CI) environments
For production environments we can capture the response length - but do not right now capture the actual content. To capture response length you need to enable the "Capture Response Size" in the Servlet or ASP.NET Sensor Properties
Hope this helps
