elmah-io changelog elmah.io

I just wanted to give you an update on the work here at elmah.io HQ. We have been awfully quiet in the last month, but that doesn't mean that we aren't working. Some things are very well suited for this changelog, while others aren't. Currently, we are working on a lot of things that either don't have any direct impact on the UI or things that we will reveal in the future:

• Getting client-side logging out of beta (follow the changes here: https://github.com/elmahio/elmah.io.js).
• Upgrading to the recent version of Elasticsearch (we have been waiting for Elastic Cloud to launch Azure support, but we decided to stop waiting and make the upgrade).
• Better invoices that conform 100% with Danish, EU and international laws.
• Working on our internal support system, that we use to support you guys.

A month ago, we launched JavaScript logging in private beta. We are so happy with the current state of the feature, that we are ready to invite everyone to join. The installation is documented in the new help article Logging to elmah.io from JavaScript. The elmah.io.js script is available through manual download, CDN, npm, NuGet and the new Library Manager in Visual Studio 2017.8. Example code can be found in the elmah.io.js samples on GitHub. Let us know what you think.

https://blog.elmah.io/continuous-deployment-to-azure-in-visual-studio-team-service/

The new batch actions feature (available in the Daily Digest Email) has been extended with a new button: Ignore in the future:

When clicking this button, new instances of this error, won't be logged moving forward. As always when ignoring based on the uniqueness hash available in elmah.io, a new release of your software, will resume logging of an error. Check out Deployment Tracking for more details.

With the new batch actions available in the daily digest email, hiding, marking as fixed or deleting errors, are available from within the email:

We've introduced API key permissions. All of your existing API keys have been migrated. We recommend you to go through each key and enable the needed permissions only. For more info, check out this blog post: https://blog.elmah.io/api-key-permissions/

There's a new Filter in town: Burst detection. With the burst filter (currently in beta), elmah.io will ignore a log message, when the same message is logged 50 times already:

The filter is based on the new isBurst flag, available on all log messages. You can search for burst messages (as long as you haven't enabled the burst filter) through the search UI and/or Rules:

isBurst:true

Be aware that ignoring burst messages will cause some features on elmah.io to not work as intended. The spike detection will in most cases don't have enough data to send the Impact Increased Email. Also, graphs on elmah.io and in the Daily Digest Email won't show the full picture of your current errors. Burst protection is primarily created for users, where staying within the message limit is more important than getting the correct picture.

Check out the list of our favourite .NET tools (that we use to build elmah.io): https://blog.elmah.io/17-must-have-net-developer-tools-the-essential-list/

You may have noticed something new in your inbox the last couple of days. We released a new Daily Digest template with a new preview text, showing a summary of the email. To the right of each metric, we've included an arrow indicating if the metric is larger, same or lower than yesterday:

We've launched a closed beta of our new clientside error logger today. That's right! We now log JavaScript happening in your application to elmah.io as well. If you want to participate in the beta, let us know by logging into elmah.io and contacting us through the support widget.