Courses

[NEW] Laravel Project PROCESS: From Start to Finish

Automated Bug Tracking: Sentry Example

Summary of this lesson:
- Setting up Sentry for error tracking
- Configuring error monitoring environment
- Testing error reporting
- Managing environment variables

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 16 lessons of this course? (105 min read)

You also get:

  • 69 courses (majority in latest Laravel 11)
  • Premium tutorials
  • Access to repositories
  • Private Discord