Using Observers in Laravel to track model events

In modern applications, reacting to changes in your data in real-time is essential, whether it's logging changes, sending notifications, or tracking user behavior. Laravel makes this easier with Observers, which allow you to hook into model events and run code when specific actions occur—such as creating, updating, or deleting a model.

In this tutorial, I'll walk you through setting up Observers in Laravel and show how you can use them for tasks like tracking and logging data changes.

What are Laravel Observers?

Laravel Observers are classes that group event-listening methods for a model. These allow you to "observe" a model and react when something happens to it, such as:

• Created
• Updated
• Deleted
• Restored
• Force Deleted

By using observers, you can separate the logic for handling model events from the models themselves, making your code cleaner and easier to maintain.

Step 1: Creating an Observer

Let's start by creating a basic Observer. In this example, we'll track changes to a Post model when it's created and updated.

To generate an observer class, run the following Artisan command:

php artisan make:observer PostObserver --model=Post

This will create a PostObserver class in the app/Observers directory and automatically link it to the Post model.

Step 2: Defining Observer Methods

Next, open the newly created PostObserver.php file. You’ll see some predefined methods, such as created and updated. Here’s how you can fill them in to log messages whenever a post is created or updated:

<?php

namespace AppObservers;

use AppModelsPost;

class PostObserver
{
    /**
     * Handle the Post "created" event.
     *
     * @param  AppModelsPost  $post
     * @return void
     */
    public function created(Post $post)
    {
        Log::info("Post created: {$post->id}");
    }

    /**
     * Handle the Post "updated" event.
     *
     * @param  AppModelsPost  $post
     * @return void
     */
    public function updated(Post $post)
    {
        Log::info("Post updated: {$post->id}");
    }
}
?>

Here, we are simply logging the event for demonstration purposes. In a real-world application, you might want to trigger actions like sending an email or updating an analytics platform like EventScout.io.

Step 3: Registering the Observer

To have the observer listen for events, you need to register it in the AppServiceProvider.php file. Add this inside the boot method:

<?php
use AppModelsPost;
use AppObserversPostObserver;

public function boot()
{
    Post::observe(PostObserver::class);
}
    

Now, every time a post is created or updated, Laravel will call the corresponding method in the PostObserver and execute the logic you defined.

Step 4: Testing the Observer

Now that the observer is set up, you can test it by creating or updating a Post model. For example:

<?php
$post = Post::create(['title' => 'First Post', 'body' => 'This is the body of the post.']);

// Update the post
$post->update(['title' => 'Updated Post']);
?>

Check your logs, and you should see entries like:

[2022-01-01 12:00:00] local.INFO: Post created: 1
[2022-01-01 12:01:00] local.INFO: Post updated: 1

Why Observers are Perfect for Event-Driven Tracking

Observers allow you to track key events in your application seamlessly. You can build logging mechanisms, audit trails, or even integrations with external services. If you're looking for more robust event tracking—beyond just model events—consider checking out EventScout.io, a simple yet powerful analytics and automation platform designed for startups and developers.

With EventScout, you can track user behavior, product usage, and monitor events across your applications in real-time—all without building your own analytics infrastructure from scratch. Whether you're logging basic events in Laravel or need detailed analytics, EventScout has you covered.

Conclusion

Laravel Observers are an elegant way to handle model events, making your code more organized and your application more responsive to changes. They are an excellent tool for developers who want to implement event-driven architectures or logging systems. If you're interested in taking this to the next level with product analytics and automation, don't forget to explore EventScout.io.

Happy coding!