We're happy to announce that we just deployed the last step in our efforts to launch country support on elmah.io. Three months ago we started putting ISO 3166-1 alpha-2 country codes on all log messages. It was a poor-mans solution based on looking at HTTP headers, which only works in some cases and never when logging client-side errors. What was more interesting about that feature, was the new search capabilities through both full-text search and search filters. Searching for log messages generated from a certain country is possible using the new
For easier filtering, the search filter feature can be used as well:
Having country codes on log messages, also allows you to create rules based on the origin of the log message.
Last week we released country flags on log message details. Showing a flag next to the client IP address, gives a quick overview of the origin of the log message:
Today, we've released the third and final feature (for now) for the country support. While we still support the HTTP header based approach for mapping a log message to a country, we now look up countries in an IP to country database. With this change, we are able to put a country code on a lot of previously unmapped log messages, including log messages generated through client-side logging.
We monitor your websites
We monitor your websites for crashes and availability. This helps you get an overview of the quality of your applications and to spot trends in your releases.
We notify you
We notify you when errors starts happening using Slack, Microsoft Teams, mail or other forms of communication to help you react to errors before your users do.
We help you fix bugs
We help you fix bugs quickly by combining error diagnostic information with innovative quick fixes and answers from Stack Overflow and social media.