Page MenuHomeDevCentral

Report exceptions to Sentry
ClosedPublic

Authored by dereckson on Mar 2 2016, 01:34.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Oct 28, 21:07
Unknown Object (File)
Mon, Oct 28, 20:47
Unknown Object (File)
Thu, Oct 17, 05:55
Unknown Object (File)
Sat, Oct 12, 16:08
Unknown Object (File)
Sat, Oct 12, 15:57
Unknown Object (File)
Fri, Oct 11, 13:16
Unknown Object (File)
Wed, Oct 9, 03:01
Unknown Object (File)
Oct 4 2024, 22:02
Subscribers

Details

Summary

We provide a new service provider, SentryServiceProvider,
bound to the 'raven' application container key, to provide
a Raven client.

The clien will connect to Sentry through a DSN configured in
SENTRY_DSN environment variable.

The exception handler sends exceptions to Sentry,
but not for unit tests.

Fixes T764.

Test Plan

Tested with the sentry.nasqueron.org installation (see T684).

The test procedure involved to check Sentry received something
in the following scenarii:

  • fire exception through a new HTTP route
  • explicitely call Raven facade through php artisan tinker
  • allow unit tests to report exceptions

Unit tests added for the service provider and the facade.

Diff Detail

Repository
rNOTIF Notifications center
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dereckson retitled this revision from to Report exceptions to Sentry.
dereckson updated this object.
dereckson edited the test plan for this revision. (Show Details)
dereckson added a reviewer: dereckson.
dereckson edited edge metadata.

More tests

dereckson edited edge metadata.

Allow test to succeed when SENTRY_DSN isn't set

dereckson added inline comments.
tests/Exceptions/HandlerTest.php
40

\n

dereckson edited edge metadata.
This revision is now accepted and ready to land.Mar 2 2016, 03:44
This revision was automatically updated to reflect the committed changes.