Many of you guys have been following along in previous posts as we went through the details of the new features and enhancements coming with the next version of Exceptionless, V2.0.
To make things easier for everyone, we thought we'd do an overview post as well, so all the new features can be found in one location and people can click to read more on the specific ones they are interested in.
Many users have asked for ways to use Exceptionless to report additional types of events, rather than just errors. With version 2.0, we are moving to an event based system that will accommodate such requests.
2.0 will have a new, manageable API with tons of great documentation and examples. Take a look at the preliminary documentation at the below link, and make sure to give us any feedback you might have.
The new pluggable system will allow customization and translation throughout the Exceptionless platform, including integration with third-party services and more. Read on for more details and source code about event parsing, the event pipeline, and formatting.
The Exceptionless client has been completely rewritten to be highly simplified and extensible, work with Mono and Project K, include additional platform specific clients, and much more. Take a look at an extended event data usage example at the link below.
In an effort to improve scalability, allow for new functionality to easily be added to Exceptionless, make the system less coupled, process things more efficiently, go fully Async, and further support Azure, we’ve been working hard on a new message bus and queueing system.
A lot of time has been spent on enhancing the job system behind Exceptionless. From the ability to run jobs standalone, making testing easier, to more ways to run jobs and the ability to auto-scale jobs based on resource constraints, lots of great changes are coming!
If you've taken a look at the upcoming features and have any comments, please let us know! We're working on everything as fast and hard as we can, and will hopefully have an ETA to have everything finished soon.
We've had quite a few requests for pricing plans that support users, retention, and errors somewhere between our old medium and enterprise plans, so we crunched the numbers and came up with new large and extra large plans that find a happy medium.
Both plans include more users, more retention, and more errors. Check out the details on each package below or view the Pricing Page for a quick summary.
The free plan, which is great for trying things out or super small personal projects, includes provisions for one project, one user, three days of error retention, and three thousand errors per month.
It does not include premium features such as advanced notifications, web hooks, and other future premium features.
The medium Exceptionless plan offers fifteen projects and twenty-five users. You get ninety days of retention, 75,000 errors per month, and premium features.
The extra large plan was created to bridge the gap between large and enterprise by quadrupling the number of errors per month to 1,000,000. You still get unlimited projects and users, as well as 180 days of retention and premium features.
For those businesses and enterprise-level teams that have several large projects and need to handle huge numbers of errors, the Enterprise plan offers everything that the Extra Large plan offers, with 3,000,000 errors per month.
Summer means vacations and pool time, but we haven't stopped working on Exceptionless 2.0. Things are coming along nicely, and today we're here to talk about the job system and the code being written to enhance it.
After you read this article, check out the previous V2.0 feature and detail articles, if you haven't already. Good stuff in there!
Jobs can easily be run standalone now, which makes it much easier to test the system. You won't have to worry about your application pool shutting down prematurely and killing your job half way through it's long-running work item.
If you need to process more tasks, simply fire up more jobs. This will save resources and money when using Azure WebJobs, as you can auto-scale jobs based on resource constraints.
We use jobs to send emails, call web hooks, process events, and much more, so these enhancements will allow for better resource control when scaling, and in general.
We've thrown out a lot of information about Exceptionless 2.0 and all the new features, enhancements, and tweaks that it's going to get. We'd love to hear from some of the regulars out there and see if we've missed anything obvious. Check out the links to the other articles at the top of the page and let us know. Thanks!
In an effort to improve scalability, allow for new functionality to easily be added to Exceptionless, make the system less coupled, process things more efficiently, go fully Async, and further support Azure, we've been working hard on a new message bus and queueing system.
Lets take a look at a few of the details surrounding these new systems we're building for Exceptionless 2.0. Take a look and let us know what you think. If you've got questions or comments, we'd love to hear them!
The new queueing system allows us to enqueue expensive tasks that can be handled at a later time. This lets us greatly reduce the processing and latency times of the api.
We stream event data that is posted to the event controller directly into the queue without taking the IO or Memory hit of processing it. This means that we can process more errors, faster, with less resources.
The system also supports retrying and discarding of data.
We queue emails that need to be sent, as well as user defined webhooks that need to be called with data. Email servers on the sending and receiving can go offline or error out while sending, but by queuing the notification emails we can ensure you always get them by re-sending in the future, after a failure occurs. In the event that we can't send you an email after a few retries, we can discard the notification.
If you're just now learning about the upcoming Exceptionless 2.0, make sure to catch up on previous feature announcements and examples by reading the below articles.
As Exceptionless 2.0 continues to become a reality, we thought we would give everyone a little taste of what you will be able to do with the new, rewritten client. Continue reading for a glimpse at the primary features, along with a complete usage example for adding extra data to events.
After you check it out, let us know if you have questions or suggestions. We're listening!
The Startup method is specific for each platform and wires up to all relevant unhandled exception events so that they will be automatically sent to the server.
client.Startup();
Manually catch and report an error with a custom tag on it.
After checking out the above example, we hope you agree that we've drastically simplified and improved the process of adding data to events, allowing for much more flexibility.
As always, if you have any questions, comments, suggestions, or concerns, let us know!
In the last Exceptionless 2.0 article, we announced the upcoming simplified API. Today, we want to introduce another major piece of V2.0 - the pluggable system.
Plugins will allow customization and translation throughout the Exceptionless platform, including integration with third-party services and more. Read on for more details about pluggable details such as event parsing, event pipeline, and formatting.
We believe building a pluggable exception reporting system and allowing third-party service and app access will create one of the most flexible, usable, and friendly solutions on the market.
We're anxious to get Exceptionless 2.0 wrapped up, but we do not have an ETA currently. We are working hard and making good progress, so keep an eye out for more sneak peeks, feature announcements, and progress reports!
As always, please let us know if you have any feedback or questions.
Since going open source, we've wanted to simplify the API and make it easier to work with.
We're taking the time to do it now, and it's going to be awesome!
Exceptionless 2.0, coming soon, will have a new, manageable API with tons of great documentation and examples. Take a look at the preliminary documentation at the below link, and make sure to give us any feedback you might have.
Event POSTs take the raw data and use a plugin system to interpret that data and translate them into events.
This allows us to take literally any data and turn it into events in the system.
The POST data is captured as a raw bytes and added immediately added to a queue for processing.
Plugins can easily be created to support new data formats like system logs.
This simplified API will make creating libraries for other platforms dead simple.
The API lives in a separate project and can be hosted on high-performance systems like the new Helios IIS host.
Makes it easy for us to migrate the UI to a SPA app.
Now uses OAuth 2.0 in addition to supporting API tokens.
Highly consistent REST API modeled after GitHub and Stripe.
It's so simple you can just use CURL as a client.
We hope you're as excited as we are to have this new, improved, more complete, and more usable documentation. Stay tuned for more details on the upcoming Exceptionless 2.0, and don't forget to leave a comment letting us know what you think.
While we're on the march to Exceptionless 2.0, we're still making updates and fixing bugs on version 1. Today, we'd like to announce that Exceptionless 1.5 has been released, which includes several server changes and bug fixes, as well as major client code base optimization.
Please update your client to version 1.5 and take a look at the other changes and bug fixes, below. We've done quite a bit of work to notifications, added throttling to improve coverage on small and free plans, and improved performance in a few places.
Added throttling to accounts that are over their usage limits. If an account is sending a high number of errors, the errors will be throttled on an hourly basis so that the entire plan limit won’t be used up immediately. This allows for a distributed sampling of the errors instead of only capturing everything in a short period of time.
Added a site notification that shows you when error submissions are being throttled or if you are over your monthly plan limits.
Removed total count from most recent errors list as it was a very expensive to calculate while providing little value.
Fixed a bug with notifications that could cause some users to get spammed. Now notifications only send a maximum of 10 notifications per project every 30 minutes.
Greatly simplified the authentication logic for the web api pipeline.
Added the ability to print all content on the error occurrence page.
The pager will no longer scroll to the top of the current list when changing pages.
Updated the paged lists to only refresh the list data via push notifications when you are on the first page.
The list data will only be updated in real time if the data matches the current filter criteria.
Fixed a bug where the loading indicators would appear on the suspended and manage organization pages.
Fixed a bug where the save button on the manage organization page would have improper styling.
Fixed a bug where a HttpAntiForgeryException could be thrown when accessing the website.
Fixed a bug where a ArgumentException would be thrown if multiple model validation errors occurred on a single page.
Fixed a bug where a NullReferenceException could be thrown when signing up.
Added some additional checks to try and resolve the user profile when an invited user signs up.
Fixed a bug where an updated organization notification could be sent before the user was authorized to access the organization.
Fixed a bug where empty OS Name and Version values were being shown in the errors environment section even if they didn't exist. This could happen if the client was reporting from an azure website instance.
Changed billing plans to use per month error limits.
Fixed a bug where the BillingManager could throw a NullReferenceException for a newly added organization. This could happen because the primary node had not replicated the content to the secondary nodes or the data wasn't cached on creation.
Updated various MongoDB collections to not persist empty array fields.
Fixed a bug where some cache entries were not automatically expiring.
It's highly recommend that you update your clients to 1.5 as we did major optimizations to the client code base.
Greatly simplified how the client processes and sends errors. The client now properly handles the various status codes that can be returned from the service.
Added an event that allows you to customize the request object before it is sent to the service.
As always, please let us know if you have any questions!
We hinted that more details on the upcoming Exceptionless 2.0 release would get announced soon, and here we are! Lets dive in a bit further, shall we?
Many users have asked for ways to use Exceptionless to report additional types of events, rather than just errors. With version 2.0, we are moving to an event based system that will accommodate such requests.
What's an Event Based Real-Time Reporting Tool Look Like? #
The new system allows us to receive literally any data people want to send us instead of only allowing errors.
Event posts can be as simple as this:
You can send log messages or even entire log files.
Log messages can contain extended data objects just like errors can now.
You can post random JSON objects and the data within them will be treated as extended data.
You can post batches of events instead of only being able to send one at a time.
You can send feature usage events that let you see how often features of your application are being used. Think about how useful that will be!
You can send session start and end events that will enable you to know what percentage of users are affected by errors and enable you to better know what your priorities should be.
We will be gathering enough data to make it easy for us to begin putting together some very useful analytic reports.
We're pretty excited about the switch from error-only to send-us-any-event-you-can-think-of real-time reporting, logging, and notifications. We think it's going to be awesome, and it's almost scary how much of a playground Exceptionless is going to turn into for some of our customers. We're not pushing the limits, we're pushing for no limits!
Ideas? Concerns? Let us know. We're working hard to wrap up Exceptionless 2.0, but there's still a lot more bells and whistles we're polishing before launch! Keep an eye out for still more sneak peek material in the coming weeks!
It may seem quiet in Exceptionless land, but the truth is we've been writing, and re-writing, more code than you can point a cursor at. If it weren't a labor of love, our fingers would have mutinied long ago, but luckily they are in it for the long haul and are churning out some seriously sweet new features and rewrites.
Exceptionless 2.0 will include many of the feature requests that have come in since we launched, and will drastically expand on the current functionality. We know you'll love it, so continue reading for a high level view of what's coming in the near future.
Many users have asked for ways to use Exceptionless to report additional types of events, rather than just errors. With 2.0, we are moving to an event based system that will accommodate this.
Since going open source, we've wanted to simplify the API and make it easier to work with. We're taking the time to do it now, and it's going to be awesome. Watch out!
Version 2.0 is coming soon. In the mean time, look for more details and sneak peeks containing examples of functionality and usage. We can't wait to show the world!
Many users have asked for ways to use Exceptionless to report additional types of events, rather than just errors. With version 2.0, we are moving to an event based system that will accommodate such requests.
2.0 will have a new, manageable API with tons of great documentation and examples. Take a look at the preliminary documentation at the below link, and make sure to give us any feedback you might have.
The new pluggable system will allow customization and translation throughout the Exceptionless platform, including integration with third-party services and more. Read on for more details and source code about event parsing, the event pipeline, and formatting.
The Exceptionless client has been completely rewritten to be highly simplified and extensible, work with Mono and Project K, include additional platform specific clients, and much more. Take a look at an extended event data usage example at the link below.
Since 
While we're 
