luceos MikeJones the free plan is great for most situations. Only when you need to give access to a team, need to log more events or need integrations do you need to upgrade. Also note they auto throttle most events logged to prevent your quota being used on one error.
luceos MikeJones I, for one, am absolutely thrilled it exists. I rather know in advance when stuff breaks than relying on the generosity and time availability of people to let me know.
tankerkiller125 luceos Indeed I discovered sentry about a year ago or so, I've used it on all my personal projects since then and I think I've convinced my workplace to implement it on our internal projects. We also discussed the possibility of implementing sentry on projects for customers but have yet to determine a best method for doing so.
datitisev 0.4.0 Use new error handling in beta 10 Should ignore PHP errors that Flarum ignores Hooks onto error view formatter & reporting NOTE: JS reporting is known to cause issues that prevent Mithril from redrawing, making views not update. This can be seen in https://nightly.flarum.site, so be aware of that. Updating composer require fof/sentry
sanwhere my log is full of this: [2019-09-24 01:45:51] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 01:47:12] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 01:49:15] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 01:49:20] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 01:49:20] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 01:49:22] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 01:54:56] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 01:58:43] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:01:29] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:05:24] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:05:47] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:09:01] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:09:17] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:12:26] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:13:36] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:14:22] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:17:38] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:21:05] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:25:38] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:30:18] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:32:11] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:33:03] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:33:10] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:34:11] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:35:21] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException [2019-09-24 02:40:58] production.DEBUG: [fof/sentry] ignoring exception of type Flarum\Http\Exception\RouteNotFoundException
datitisev sanwhere You are on beta 9 then. Those logs simply mark that the exception has not been reported to sentry as it can be safely ignored most of the time. I suggest updating to beta 10.
sanwhere datitisev thank you, i'll update beta10 soon. i have 1.5gb database, so i need some time to do it :/
datitisev 0.4.1 Fixed some redraw issues with Mithril Tested with the login & signup modals when they error, should hopefully fix all redraw issues Required removing the TryCatch integration Update Sentry to v5.7.1 0.4.2 Fixed IE support Updating composer require fof/sentry
MikeJones How do I set this up? I just registered on sentry. Do I need to install the SDK? Which language do I pick, Larvel, node.js php? And I do not see where to get my DSN number from..
datitisev MikeJones The language doesn’t matter, it simply is used for the icon. You don’t need to install the SDK, that’s already been done. You get the DSN by going to the project settings after creating it and there’s a section for it, can’t remember right now what it’s called.
datitisev 0.4.3 Catch PHP notices & warnings If not in debug mode, warnings & notices will now not show to the user This means that notices & warnings during posting will look post just fine on the frontend (and avoid doubleposting, for example) If in debug mode, the notice/warning is now thrown as an exception, so you'll have an actual stack trace to look at In both cases, it will be reported to Sentry as an info level error Sets PHP settings error_reporting to all and display_errors to off Updating composer require fof/sentry
datitisev 0.4.5 0.4.4 Ignore STMT_PREPARE warnings that Eloquent automatically reconnects from Fix issues with IE in admin area Updating composer require fof/sentry
clarkwinkelmann datitisev I think the screenshot shows the composer error. panteLx can you share the content of your composer.json? Either two extensions (or their dependencies) require different versions of php-http/curl-client, or maybe you manually installed a package that blocks that version. Also does running composer install without any argument triggers an error ?
datitisev clarkwinkelmann Oh, I didn't see that there was a screenshot... I get Cloudflare Access Denied when trying to view it. 🤷 EDIT: Try running composer why php-http/curl-client to see what's requiring it.
tankerkiller125 datitisev Same here, I also didn't see that there was an image, looks like a Geo block
