In this scenario we have an application that performs slowly and has high CPU usage. Typically pages take longer to load and sometimes might timeout. Start DebugDiag Collector and select “Performance” Select the second option to monitor the HTTP response times of your website Add the urls to the pages that are performing slowly to monitor their response times Enter the page urls and set the timeout after which the rule is triggered.
Application crash In this scenario we want to capture a memory dump at the exact moment the application has crashed. Start the “Debug Diag Collection” tool and select “Crash” Select a specific application pool, i.e the application pool that your site is running. Select the application pool of your website Leave the defaults selected. In DebugDiag 2.0 this will record the call stack for first chance exceptions and a full memory dump for second chance exceptions, i.
Debugging and troubleshooting problems in a production environment is always a tricky endeavour. You usually do not have the luxuries of having a debugger that allows you to step through your code and inspect you variables and stack trace. Some of the areas you might look at include the Event Viewer, to look for any error events or the application log files, to analyse any caught exceptions. If the application is crashing and there’s nothing obvious available in the logs, your best bet is to perform post-mortem analysis with DebugDiag/AdPlus and Windbg.
Some websites use security through obscurity as their main means of protection. This methodology relies on making the vulnerabilities hard to obtain by not making the system’s design known to the general public. As anyone knows, a secret is never a secret for very long. This is bad practice and careless. Concealing a vulnerability will only delay an attacker and not pass any form of security testing. The right approach is to have security as part of the design process of a system.
A global website needs to have relevant content for their multi-cultural, sometimes worldwide, audience. This content needs to be provided to a visitor as quickly as possible to engage them in a great experience. One solution is to deploy and mirror your application to several datacentres across the world. A much more cost effective solution is to use a CDN (Content Delivery Network) to serve your content from a geographical location close to your visitor.
