-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup sentry for error logging #11
Comments
I'm currently using exceptional.io, can add you as a member too, unless sentry is better? |
That sounds acceptable. Do I need to register first? |
Does exceptional provide variable contents in the stack traces? Isn't clear from their intro site. |
it doesn't have variable contents, I think it only gets the backtrace. If sentry is better then I'm perfectly happy to switch. |
exceptional.io no longer exists; it's now airbrake.io — with similar pricing to Sentry AFAICT. I remain neutral on what approach we take, except that paying $$$ every month for projects that don't have active development seems a bit silly. Instead, maybe we should be running a /dev/fort Sentry instance somewhere? It has a good integration story with various languages (including Javascript) via the raven languages, so we aren't constraining future work in any way, and it's OSS. (Of course this then requires someone to install Sentry and integrate. But at the same time we could integrate some other fort projects, so the extra effort would be shared.) |
I've had quite good experiences with the free tier of NewRelic (if you sign All the usual, exception monitoring, vm and even server agents, url uptime On 15 November 2014 15:32, James Aylett notifications@github.com wrote:
|
https://getsentry.com/welcome/
So we can track 500s better.
The text was updated successfully, but these errors were encountered: