dcsimg

The 15 Most Common Web Server Tags and Real-Time Alerts

  • The 15 Most Common Web Server Tags and Real-Time Alerts-

    Setup Issues

    When you start to run a new application on a new or existing install of IIS and ASP.net, you often run into the following error: Handler "ScriptHandlerFactory" has a bad module "ManagedPipelineHandler" in its module list. One reason for this error may be that ASP.net was not completely installed during the IIS setup. Another reason this error may appear in your logs is due to a configuration issue when your application requires that it be run in integrated mode. By monitoring your logs for the specific error code 500.21, you can easily catch this error and correct it before it causes a real issue.

    "Error 500.21"

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18

The 15 Most Common Web Server Tags and Real-Time Alerts

  • 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18
  • The 15 Most Common Web Server Tags and Real-Time Alerts-14

    Setup Issues

    When you start to run a new application on a new or existing install of IIS and ASP.net, you often run into the following error: Handler "ScriptHandlerFactory" has a bad module "ManagedPipelineHandler" in its module list. One reason for this error may be that ASP.net was not completely installed during the IIS setup. Another reason this error may appear in your logs is due to a configuration issue when your application requires that it be run in integrated mode. By monitoring your logs for the specific error code 500.21, you can easily catch this error and correct it before it causes a real issue.

    "Error 500.21"

Log data is becoming an increasingly important indicator of companies' application, IT and overall business health. It is the go-to data when things go wrong.

More than ever before, companies are turning to logs to proactively troubleshoot in development, support real-time performance-monitoring efforts, analyze user behavior and assure security compliance. Based on Logentries' 25,000 global users who are actively analyzing and tagging critical log events in real time, the top tags fall into three critical categories: organization-wide exceptions (e.g., general browser and server issues); security-related tags (e.g., tracking SQL injection attempts to block breaches); and specific, application-level server exceptions.

In this slide show, Logentries Chief Scientist Dr. Trevor Parsons shares perspective on the 15 most common Web server tags and real-time alerts so any company can quickly start classifying log data and proactively identify common issues.