Stop Logging Raw JSON: How I Built a Visual Audit Trail for Filament PHP

We’ve all been there. You need to track who changed what in your database. You install an audit package, and it works—but every time you need to check the history, you’re staring at a wall of raw JSON in a database manager or a cramped table.

I wanted something better for my Filament projects. I wanted to "Time Travel."

That’s why I built Chronos.

⏳ What is Chronos?

Chronos is a audit trail plugin for Filament V4 / V5 that focuses on one thing: Visibility.

Instead of just logging changes, it provides a beautiful, side-by-side comparison of your data. You can see exactly what changed, when, and by whom, all within a sleek slide-over UI.

🚀 The "Zero-Build" Challenge

One of my main goals was to make Chronos a "plug-and-play" experience.

Usually, when you build custom UI for Filament, you have to deal with Tailwind JIT, custom configurations, and running npm run build. For Chronos, I went a different route. I utilized native Filament classes and CSS variables.

The Result? You install it, and it immediately adopts your panel's primary colors and dark mode settings without touching a single JS file.

✨ Key Features

Visual Diffs: Color-coded highlighting for Created (Green), Updated (Blue), and Deleted (Red) events.

Context Aware: Automatically captures User data, IP addresses, and timestamps.

Polymorphic: It doesn't matter what your model is; if it’s Eloquent, Chronos can track it.

Dark Mode Support: Looks just as good at 2 AM as it does at 10 AM.

🛠️ How it looks in code

Integrating Chronos is intentionally simple.

1. Add the trait to your Model:
   

use Ianstudios\Chronos\Concerns\HasChronos;



class Product extends Model {

    use HasChronos;

}

1. Add the Action to your Filament Resource:
   

use Ianstudios\Chronos\Actions\ChronosHistoryAction;



// In your Header Actions or Table Actions

ChronosHistoryAction::make()

That’s it. No complicated setup, no overhead.

📦 Try it out!

I’ve just released v1.7.0, which brings improved native styling and better performance for large audit logs.

If you’re building CRMs, ERPs, or any data-sensitive application with Filament, Chronos might just be the "Time Travel" tool you’ve been looking for.

Check out the live demo and documentation here:

👉 https://creator.ianstudios.id

Final Thoughts

Building tools for the Filament ecosystem has been an amazing journey. The community focus on DX (Developer Experience) is what drives me to keep refining Chronos.

How are you currently handling audit logs in your Laravel apps? Let’s chat in the comments! 👇