Add support for viewing raw body requests
It would be great to see raw body request on analytics. Good for monitoring restful api calls (for example json payloads)
We are exploring how to implement this feature without compromising privacy. Thank you for all the feedback!
- Matt, Product Manager
Do we have an update on this?
Please let me know once this is implemented.
Has this been implemented yet?
definetely, I need this feature
Tim Hardy commented
Privacy? You do what is done everywhere else privacy is a concern - you make it a choice. Responsibility is now on the chooser. Done.
Tim Hardy commented
Api logging without request/response data is useless. Not sure how this got past MVP without this functionality. Makes me seriously question Microsoft's judgement (like I haven't done that before :).
I am using the approach as explained in my blog to solve the problem
Basically it involves storing the response in request message using message handler and retrieving the same in the class that implements ITelemetryInitialize.
This would be very helpful.
Mauricio Atanache G. commented
Speaking for everyone in my team +50
Marcelo Ramagem commented
Q: Are you using ASP.NET Standard or ASP.NET Core?
A: Neither - Node.js
Q: Would it help to see just incoming request bodies? Or is it outgoing requests too?
A: Incoming most important, outgoing just icing on the cake
Q: Would it help to see the response body too or is just the request fine?
A: Absolutely.. .body too please
Q: Do you only want to see the full body when there's a failure/exception?
A: Yes, absolutely.
Right now the transaction details aren't very useful when posting data (which is like 99% of our calls from react). We can see the path, but not the parameters being sent. this doesn't help at all when trying to find why a request is taking a long time because I cant see what the parameters were. Querystrings are not an option for us.
Jason Wisener commented
Would be great to be able to see the json response and request bodies, right now you can't really see the values that are getting sent to the server for an api endpoint call.
Edwardenis De Los Santos commented
I would be really usefull to trace where exceptions are coming from.
Kari Tuominen commented
This would help cases where you need to know what parameters client has send to API for example if exception occurs on server.
if I FTP into my App Service (running a Web API 2 stack), I can download the "failed request" XML files (e.g. fr000001.xml) and get a lot of insight (especially if I also grab the freb.xsl which formats the XML into a nice tabbed UI).
I discovered the request headers being used to POST to my api, and can see the JWT bearer token that was used.. but, I don't know what the JSON payload is. That's really important.
I get a lot of useless info about my 500 error, but.. no stack trace or anything really useful.
Guys, please add this
Please add this
Totally agreed with request, should be in there already. Essential for insight, now custom code is being written and rewritten over and over again to accomplish this.
Oh, god, please add this. Why isn't it there already?