Skip to content
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

Open
public opened this issue Oct 13, 2013 · 6 comments
Open

Setup sentry for error logging #11

public opened this issue Oct 13, 2013 · 6 comments

Comments

@public
Copy link
Contributor

public commented Oct 13, 2013

https://getsentry.com/welcome/

So we can track 500s better.

@pkqk
Copy link
Member

pkqk commented Oct 15, 2013

I'm currently using exceptional.io, can add you as a member too, unless sentry is better?

@public
Copy link
Contributor Author

public commented Oct 15, 2013

That sounds acceptable. Do I need to register first?

@jaylett
Copy link
Member

jaylett commented Oct 15, 2013

Does exceptional provide variable contents in the stack traces? Isn't clear from their intro site.

@pkqk
Copy link
Member

pkqk commented Oct 15, 2013

it doesn't have variable contents, I think it only gets the backtrace. If sentry is better then I'm perfectly happy to switch.

@jaylett
Copy link
Member

jaylett commented Nov 15, 2014

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.)

@abs0
Copy link
Contributor

abs0 commented Nov 16, 2014

I've had quite good experiences with the free tier of NewRelic (if you sign
in via a 'partner' like rackspace cloudtools - itself free - then you get
'standard free' rather than 'lite free' which gives you 7 days of history
and unlimited servers).

All the usual, exception monitoring, vm and even server agents, url uptime
with notification.

On 15 November 2014 15:32, James Aylett notifications@github.com wrote:

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.)


Reply to this email directly or view it on GitHub
#11 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants