Skip to main content

Automated Bug Tracking: Sentry Example

Premium
5 min read

In the previous lesson, we fixed our first bug, reported by the client. But what if some bug happens for other users who wouldn't report it? Can we track those bugs somewhere, in addition to Laravel logs?

There are quite a few bug tracking/monitoring tools - the most popular in the Laravel community is Sentry. Here's a typical error list from Sentry.

In this lesson, we will show Sentry in action.

Other well-known bug-tracking alternatives are BugSnag and Flare. They all work similarly but with slightly different feature sets and pricing. Check their homepages for more details.

In addition to the list of issues, Sentry has a log viewer, too:

So, let's add Sentry to our app and simulate a bug locally.


Adding Sentry

Adding Sentry is easy - create an account at Sentry.io and start a new project. In there, select Laravel:

Once created, it will give you detailed instructions on...

The Full Lesson is Only for Premium Members

Want to access all of our courses? (30 h 33 min)

You also get:

55 courses
Premium tutorials
Access to repositories
Private Discord
Get Premium for $129/year or $29/month

Already a member? Login here

Comments & Discussion

No comments yet…

We'd Love Your Feedback

Tell us what you like or what we can improve

Feel free to share anything you like or dislike about this page or the platform in general.