Jobs not showing in Horizon Dashboard

[T3chW1zard]

Currently the jobs aren't showing on the Horizon dashboard. Is it possible to update the package to show them in the dashboard?

If needed, I'll be able to assist with the PR.

[YanGusik]

Thanks for the feedback!

This is a known limitation, already documented in README. Let me explain why it's technically challenging to implement.

Why Horizon doesn't show pending jobs

Horizon expects jobs in a single Redis key queues:{name}, but Balanced Queue stores them partitioned:

Horizon expects:     queues:default (single LIST)
Balanced Queue:      balanced-queue:queues:default:user:123 (LIST per partition)
                     balanced-queue:queues:default:user:456
                     balanced-queue:queues:default:user:789
                     ...

Horizon's RedisJobRepository hardcodes this key structure with no interface to override.

Why it's hard to fix

Option 1: Duplicate data to standard keys

• Double memory usage
• Race conditions between two data structures
• Need to sync on every push/pop/delete
• Performance overhead

Option 2: Override Horizon internals

• Horizon doesn't expose interfaces for this
• Would require patching Horizon's ServiceProvider
• Any Horizon update could break the integration
• Too many methods to rewrite (pending, completed, failed, recent...)

Both options bring significant risks and maintenance burden for what is essentially a visual feature.

What already works

Feature	Status
Job execution via Horizon workers	✅ Works
Completed jobs in dashboard	❌ No Shows
Failed jobs in dashboard	✅ Works
Worker metrics	✅ Works
Pending jobs count	❌ Shows 0

Recommended alternatives

For production monitoring, I recommend:

1. CLI monitoring: php artisan balanced-queue:table --watch
2. Prometheus endpoint: Enable in config, connect to Grafana
3. Programmatic access: Metrics class for custom dashboards

In production with proper monitoring (Grafana/Prometheus), Horizon's pending count becomes less critical since you have real-time metrics anyway.

---

I'm open to discussing this further, but given the complexity vs benefit tradeoff, I'm leaning towards keeping the current approach with dedicated monitoring tools rather than fighting Horizon's architecture.

[YanGusik]

What exactly do you need to see in Horizon? Detailed job reports, pending count, or something else?

[T3chW1zard]

Hi @YanGusik, thank you for the detailed explanation. Currently i dont get any ingo on horizon. Even for completed, silent or failed jobs. I have tested it with a clean install if laravel 12 and horizon and tenancy.

Not sure if the tenancy is breaking it as it prefix in the redis.

I have followed the instructions in the readme and still not shoeing anything. The jobs does complete successfully wiyh horizon but not showing in there.

[YanGusik]

I tested on clean Laravel Sail + Horizon (no Tenancy):

• Workers: ✅ showing
• Failed jobs: ✅ showing
• Pending jobs: ❌ not showing
• Completed jobs: ❌ not showing

So it's not a Tenancy issue - this is expected behavior with the current architecture.

For completed jobs to show in Horizon, we'd need to duplicate job data to Horizon's internal Redis keys after each job finishes. This adds overhead and complexity for what is essentially a dashboard feature.

Is the completed jobs list critical for your use case, or would Prometheus/Grafana metrics work for you?

[YanGusik]

In theory, I could add an optional config flag (experimental) to sync completed jobs to Horizon's completed_jobs Redis key.

Implementation would listen to Laravel's JobProcessed event and call Horizon's JobRepository::completed() method. This adds a small overhead per job but should work.

Would you be interested in testing this if I implement it?

[T3chW1zard]

Hi @YanGusik,

I will definitely help testing it yes.

Possible Solution: Fire the Events Horizon Already Listens To

Rather than duplicating data to Horizon's Redis keys or overriding Horizon internals, we can hook into Horizon's own event system. Horizon tracks jobs by listening to events like JobPushed, JobReserved, JobDeleted, and JobReleased. If BalancedRedisQueue fires these events at the right lifecycle points, Horizon will automatically pick them up and display the jobs in its dashboard.