Asked by:
How to monitor all outgoing request from asp.net web application which is hosted in IIS

Question
-
User639247119 posted
My asp.net application is deployed in IIS. This application will make some requests to 3rd party web services. I've implemented a httpmodule to capture all the http requests. But it capture only the incoming requests. How can I monitor all the incoming and outgoing requests of my asp.net application? I want to achieve it programmatically without using any tool like fiddler or wireshark.
Monday, June 25, 2018 12:07 PM
All replies
-
User475983607 posted
My asp.net application is deployed in IIS. This application will make some requests to 3rd party web services. I've implemented a httpmodule to capture all the http requests. But it capture only the incoming requests. How can I monitor all the incoming and outgoing requests of my asp.net application? I want to achieve it programmatically without using any tool like fiddler or wireshark.
Simply add code to the outbound requests. The current code base might need a little refactoring depending on how the code is designed.
Monday, June 25, 2018 1:04 PM -
User639247119 posted
Simply add code to the outbound requests. The current code base might need a little refactoring depending on how the code is designed.
Thanks
But I don't want to touch anything in my web application code. I'm looking for a solution something like Httpmodule which can be added to web.config whenever required and remove it when it is not needed, so that it won't impact the application performance when we don't want to monitor the requests.Monday, June 25, 2018 3:57 PM -
User475983607 posted
But I don't want to touch anything in my web application code. I'm looking for a solution something like Httpmodule which can be added to web.config whenever required and remove it when it is not needed, so that it won't impact the application performance when we don't want to monitor the requests.If the service is a SOAP service and a service reference was created then enable tracing. Otherwise, you'll need to clarify how your client works.
https://docs.microsoft.com/en-us/dotnet/framework/wcf/diagnostics/tracing/configuring-tracing
Also your network admin can help with logging.
Monday, June 25, 2018 5:18 PM -
User283571144 posted
Hi Tom mac,
According to your description, I suggest you could try to use application inslights to help you achieve your requirement.
The application insligths have the Dependency tracking feature.
A dependency is an external component that is called by your app. It's typically a service called using HTTP, or a database, or a file system. Application Insights measures how long your application waits for dependencies and how often a dependency call fails. You can investigate specific calls, and relate them to requests and exceptions.
More details about how to use application inslights in asp.net application, you could refer to below article.
https://docs.microsoft.com/en-us/azure/application-insights/quick-monitor-portal
Best Regards,
Brando
Tuesday, June 26, 2018 7:28 AM