locked
Help me out to know more iis/asp.net troubleshooting tools RRS feed

  • Question

  • User576560837 posted

    Hi Folks,

    Currently i am using browser dev tools and fiddler tracing, failed request tracing for troubleshooting asp.net iis hosted application on pre prod and prod environments. Is there any more tools where i can use for troubleshooting. Please share more ideas and your answer is really appreciated!

    Thanks!

    Friday, April 2, 2021 12:35 AM

All replies

  • User1535942433 posted

    Hi pegiis,

    There are different troubleshooting tools for different problems, for example, error messages can usually be viewed in the Event Viewer, for Network problems, we usually use Microsoft Network Monitor, and there is also the Debug Diagnostic Tool, the Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or memory fragmentation, and crashes in any user-mode process.

    Best regards,

    Yijing Sun

    Friday, April 2, 2021 6:40 AM
  • User753101303 posted

    Hi,

    If the problem happens server side start (ie http 500.x status code) start by checking the logs found at https://stackify.com/beyond-iis-logs-find-failed-iis-asp-net-requests/

    The IIS log allows to see the exact http status code (500.0 and 500.19 have a different meaning) and exception details should be written by default to the Windows event log.

    Friday, April 2, 2021 7:29 AM
  • User576560837 posted

    @yij sun

    Thanks for your reply. One more as i know network monitor is for network related and debugdiag is for slowness things. I would like to know prod or pre prod live web pages at browser level if you want to troubleshoot how can we do?

    Suppose if it has bad code or bad un responsive service calls. As i know visual studio debugger it needs visual studio dot net IDE apart from that if we want to troubleshoot/debug web applications, which are hosted on iis web server how can we do that? Please let me know. Currently i am doing fiddler and browser dev tools for that. I would like to know is there any more tools for troubleshooting of hosted web application requests?

    Friday, April 2, 2021 8:01 AM
  • User576560837 posted

    @PatriceSc

    Thanks for your information. Its really helpful. I would like to know more on this. Is there anything else still remaining. I mean is there any more tools helpful to trace bad code or bad service calls or unresponsive service calls of web requests, which hosted on iis web server. Please let me know.

    Thanks!

    Friday, April 2, 2021 8:06 AM
  • User753101303 posted

    If you try to solve an actual performance problem it could be best to discuss directly about it.

    On the client side you could also use https://developers.google.com/web/tools/lighthouse A common problem when being new to the web is  rendering a huge HTML page (for example showing thousands of rows right away rather in a "grid" rather than using paging or filtreing to show the user only the rows he needs iright now).

    If this is a production app rather than using the debugger on the server to find performance issues you could collect traces to better understand what happens. Point 4 in my earlier link allows to keep a low level trace for long  http queries but this is quite low level.

    You can also add a trace to your app or even use an APM application such as https://docs.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview

    You also have https://michaelscodingspot.com/performance-counters/ etc (in addition to the other tools mentioned in other responses)...

    Friday, April 2, 2021 10:11 AM
  • User576560837 posted

    @PatriceSc

    Thanks Patricesc for explaining performance related issues troubleshooting and why we use dot net code profiler tools. which is the best free code profiler tool? I just wanted to clarify on this. please understand me.

    Thanks!

    Friday, April 2, 2021 3:42 PM
  • User576560837 posted

    @PatriceSc

    Let me more clear. I am actually take care of issue troubleshooting of production and non production asp.net mvc code behind c# web application, which are hosted on iis web server.  We use fiddler trace and browser dev tools to check request response drop issues and backend service call failure issues, some bad code issues too. I would like to know more what other free tools i can use to do my tasks in better way. Please list out tools information if you can add in this regarding for issues troubleshooting of bad code, response failures, service call failures...other asp.net mvc issues.

    Thanks!

    Friday, April 2, 2021 3:51 PM
  • User-103922977 posted

    Few more

    LogParser

    https://docs.microsoft.com/en-us/iis/troubleshoot/performance-issues/troubleshooting-iis-performance-issues-or-application-errors-using-logparser

    Windows performance counters

    https://docs.microsoft.com/en-us/windows/win32/perfctrs/using-performance-counters

    Apart from the above and what others suggested, does your application write error logs to a log file, database or application insights.If not, I would suggest to implement code to write error logs and include additional diagnostic information like request and response parameters as part of the logs.This will be really helpful in investigating issues that cannot be replicated in lower environments like interface errors, errors due to inconsistent data in production etc. 

    Sunday, April 4, 2021 9:42 PM
  • User1535942433 posted

    Hi pegiis,

    As far as I thin,there are no free browser code profiler tools.

    But you could try these tools:

    1.Visual Log Parser.It's a  free Visual tool for the Microsoft LogParser engine.

    2.ELK stack

    3. Stackify Retrace

    4. Splunk 

    Best regards,

    Yijing Sun

    Tuesday, April 6, 2021 2:41 AM