Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Error logging services and frameworks

Error logging

Why? Because this is the only way to find all errors your users see but you don't. Only thing left that could fail without you knowing about it is the service or framework itself so let's hope that's well tested or... errorception!

I guess it should possible to log something like "okay, I'm loaded and ready to catch them errors" to make sure everything works as expected but I degress.

You can also read something like http://blog.meldium.com/home/2013/9/30/so-youre-thinking-of-tracking-your-js-errors about JS error tracking.

Below you will find some resources I collected during a very not extensive Google search, I might add more later.

Services

Services do all the logging for you and give you a nice (hopefully) GUI to use. Included some pricing information but for the full picture visit their websites.

Frameworks

Frameworks are only the client side code, you need to do all the logging yourself. At least these are free!

@CrocoDillon
Copy link
Author

CrocoDillon commented Jan 16, 2015

I think tracking JavaScript errors will be a big thing because they allow you to focus on code instead of browser quirks, which you can solve as they appear later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment