Download the PHP package henzeb/event-horizon without Composer
On this page you can find all versions of the php package henzeb/event-horizon. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download henzeb/event-horizon
More information about henzeb/event-horizon
Files in henzeb/event-horizon
Package event-horizon
Short Description Enables seamless job monitoring and tag management across multiple Redis connections or databases
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package event-horizon
Event Horizon
Event Horizon fixes Laravel Horizon's job monitoring when you have multiple Redis connections. It makes sure job tracking data goes to the right place - where the job is actually processed, not where it was pushed from.
The Problem
Horizon gets confused when you use multiple Redis connections. Here's what happens:
You push a job from connection A, but it gets processed on connection B. Horizon shows the job as "pending" on connection A's dashboard, even though it's actually running on connection B. This makes your dashboards misleading and makes it hard to see what's really happening with your jobs.
This becomes a real headache when you're trying to monitor job performance, debug issues, or just understand what's going on in your application. You end up checking multiple dashboards, seeing conflicting information, and never getting a clear picture of your job processing.
The root cause is that Horizon was built assuming you'd use one Redis connection for everything. When you have multiple connections (which is pretty common in modern apps), its monitoring system doesn't know how to handle jobs that cross connection boundaries.
The Solution
Event Horizon fixes this by tracking jobs where they actually get processed. When you push a job to connection B, all the monitoring data (job status, tags, metrics) gets stored in connection B's Redis instance, not where you pushed it from.
This means your Horizon dashboards show the real picture - jobs appear where they're actually running, making it much easier to monitor what's happening. No more hunting across different dashboards or trying to piece together where your jobs really are.
The package works by extending Horizon's core monitoring classes to be connection-aware. It automatically detects which Redis connection a job is destined for and routes all monitoring data there. You don't need to change any of your existing code - it just works.
Installation
That's it! Works automatically once installed.
When You Need This
- Multiple Redis connections: Your app uses different Redis instances for different purposes
- Multi-tenant applications: Each tenant has their own Redis instance and you want isolated monitoring
- Microservices: Different services push jobs to different connections
- Load balancing: You're spreading jobs across multiple Redis instances
- Team separation: Different teams manage different queue connections and want their own dashboards
Example
Before Event Horizon, all these jobs might show up on the wrong dashboards depending on where you pushed them from. After installing it, each job appears exactly where you'd expect - on the dashboard for the connection that's actually processing it.
How It Works
Event Horizon extends three key parts of Horizon:
- Job monitoring: Tracks jobs in the correct Redis instance
- Tag storage: Stores job tags where the job is processed
- Event handling: Ensures monitoring events go to the right place
The package automatically replaces Horizon's default behavior with connection-aware versions. Everything happens behind the scenes - you don't need to change your existing job code or queue configuration.
Requirements
- PHP 8.2+
- Laravel Horizon ^5.0
- All Horizon instances must use the same
horizon.prefixconfiguration value
License
MIT License. See LICENSE.md for details.
