Improvement #1 - HTTP method on URLs

This is the first post in the series 10 improvements in 10 days. Today, we wanted to improve the way URLs are shown on When dealing with web sites (especially Web APIs), not only the URL of an error is important, but also the HTTP method. A single resource URL can have multiple allowed methods. To make it more visible which resource that actually failed, we give you HTTP method on URLs:

HTTP method on URL

Notice the small label left of the URL in both the error details and the list? It may not look like much, but it makes a big difference when trying to get an overview on what's going on. Since HTTP method is now indexed in our Elasticsearch cluster as well, search for errors with a specific HTTP method is now possible:

Searching for HTTP method

Finally, creating rules and apps on top of HTTP method is also open for anyone up for the challenge.

Tomorrow, we will implement a minor but often requested improvement to Error logging and Uptime Monitoring for your web apps

This blog post is brought to you by is error logging, uptime monitoring, deployment tracking, and service heartbeats for your .NET and JavaScript applications. Stop relying on your users to notify you when something is wrong or dig through hundreds of megabytes of log files spread across servers. With, we store all of your log messages, notify you through popular channels like email, Slack, and Microsoft Teams, and help you fix errors fast.

See how we can help you monitor your website for crashes Monitor your website