Purchasing top-ups have been available on elmah.io for a couple of years. But, if you wanted to purchase more than one, you would need to make multiple purchases and in result get multiple invoices for your accountant to worry about. With the new top-ups dialog, you can now purchase multiple top-ups in one go:
Did you know that elmah.io can be used on Windows Forms too? If you have some of those left, why not set up logging to elmah.io? We wrote a new guide explaining how: Logging to elmah.io from Windows Forms.
We released a new version (3.3.0) of the elmah.io.javascript package. The new version supports capturing console logging by setting the captureConsoleMinimumLevel option:
new Elmahio({
apiKey: 'YOUR-API-KEY',
logId: 'YOUR-LOG-ID',
captureConsoleMinimumLevel: 'error'
});
Messages logged through console are captured by elmah.io.javascript and stored on elmah.io:
console.error('This is an %s message.', 'error');
We published a new help article showing how to log to elmah.io from the popular headless CMS, Piranha: Logging to elmah.io from Piranha CMS.
We released a new version (3.7.66) of the Elmah.Io.Extensions.Logging package. The new version includes the following changes:
Elmah.Io.Client.We released a new version (3.10.122) of the Elmah.Io.AspNetCore package. The new version includes the following changes:
elmah.io.javascript updated to 3.2.0.UseElmahIo now throws an exception if AddElmahIo hasn’t been called.url field rather than only looking at Request.Path.Elmah.Io.Client.We released a new version (3.9.90) of the Elmah.Io.Client package. This version includes the following changes:
AggregateException. This version iterates the entire tree of aggregates and collects all properties and exception-specific information.All integrations work with this version. You can either upgrade Elmah.Io.Client manually or wait for the integration you use to depend on the new version.
We had a couple of requests for being able to update and remove a VAT number registered on a paying organization. Removing the VAT number is now possible for countries outside the EU. Updating a VAT number is now also possible, as long as the new VAT number still validates.
While looking at this we also improved the validation error to show an example from the chosen country to help you figure out the correct format to use:
To reduce the risk of someone getting access to your log data, we have integrated with Have I Been Pwned. This means that can no longer sign up for elmah.io, or change the password on an existing user, with a password appearing in one or more data breaches. We recommend you to use a password manager like LastPass or 1password to generate a unique and complex password for your elmah.io account.
You may know about the free tools we have on the elmah.io website like the Web.config Validator and the Stack Trace Formatter. As suggested in the name, the Stack Trace Formatter converts unformatted .NET stack traces to a pretty syntax-highlighted output that you can save as an image or copy for use on StackOverflow, your blog, etc.
We have extended the Stack Trace Formatter with a new Share button that will let you share a formatted stack trace as a link with a friend or colleague.
There’s a new dashboard for heartbeat errors available in the dropdown next to the Search tab:
The search result shows all open heartbeat errors.
We recently upgraded our API from Swagger v2 to OpenAPI v3. The upgrade was transparent to the clients, meaning that all existing versions worked on the new endpoints. We had to roll back to Swagger today since we found out that AutoRest (the tool we use to generate the Elmah.Io.Client package) doesn’t support OpenAPI v3 yet. No changes are required from your side.
We published a new issue of the elmah.io Newsletter: https://us7.campaign-archive.com/?u=66fdd2122e968863d381a26e1&id=fc568b1008
If you want to receive an email every 2-3 months with all of the recent goodies on elmah.io, make sure to subscribe here: http://eepurl.com/dE1hCn
The API endpoints for getting all logs in an organization and a single log from a log id have been extended with two new properties: color and environmentName. These will include the values for the log color and the environment chosen through the elmah.io UI.
An updated version of the Elmah.Io.Client package will follow asap.
We have added two additional fields to the Zapier app: LogId and Permalink. With these, you can build deep links to the elmah.io UI, add a permalink to an error when creating it in an issue tracker, and much more.
We just published one of the most requested features: Custom environments. Previously, there were 4 hardcodes environment names that you could group your logs by: Production, Staging, Test, and Development. With the new Environment admin on your organization settings page, you can create the environments you want and assign custom names:
The environments are grouped in the same order as on the admin page on Dashboard and on the left menu. You can drag and drop environment names on the admin page to reorder.
We pushed some improvements to the hashing algorithm used internally on elmah.io. The hash is used for various purposes like the isNew flag and Unique grouping on the elmah.io UI. With the recent changes, elmah.io is able to detect dates and similar in log messages.
As an example, the following log messages would both be marked as unique (isNew=true) with the old hashing algorithm but as the same log message with the new hash:
The last successful renewal completed at 2020-04-07T05:12:54.257Z
The last successful renewal completed at 2020-05-12T13:44:35.593Z
There’s a new endpoint on the API, able to mark one or more log messages as fixed:
https://api.elmah.io/v3/messages/LOG_ID/MESSAGE_ID/_fix
For details, check out the added section in the documentation: Fixing a message.