Weave Code
Zabbix Bundle Laravel Package
flowti/zabbix-bundle
flowti/zabbix-bundle offers a PHP integration layer for Zabbix, letting your application query hosts, items, triggers, and events through the Zabbix API. It wraps common monitoring calls in a simple, framework-friendly service so you can surface alerts and metrics without hand-writing raw API reques...
Zabbix integration for Symfony
Frequently asked questions about Zabbix Bundle
- Is flowti/zabbix-bundle a Laravel package?
- No. It is a Symfony bundle built around Symfony's Bundle class, DependencyInjection extension, and YAML or XML service wiring, none of which Laravel's kernel bootstraps. Laravel has no auto-discovery, publishable config, or facade for it. Only the underlying Zabbix JSON-RPC service classes are candidates for reuse in a Laravel application.
- Can I install flowti/zabbix-bundle in a Laravel project with Composer?
- You can require it via Composer, but installing it does not integrate it with Laravel. There is no Laravel service provider, no package discovery, and no config publishing. You would have to manually instantiate or wrap the service classes and manage configuration yourself. Expect to fork or extract code rather than use the bundle as-is.
- Does flowti/zabbix-bundle support Laravel 10 or Laravel 11?
- There is no confirmed Laravel support. The bundle targets Symfony, and its Composer constraints are unverified but likely Symfony 4 or 5 and PHP 7.x era. Those constraints can conflict with the Symfony components bundled in Laravel 10 and 11. Treat Laravel compatibility as unproven until you test a fork against your target versions.
- Does flowti/zabbix-bundle send metrics to Zabbix via the trapper or zabbix_sender protocol?
- No. The v0.0.1 release documents seven JSON-RPC methods: user.login, user.logout, event.acknowledge, host.get, hostgroup.get, event.get, and trigger.get. That is a pull and acknowledge client, not a trapper or zabbix_sender implementation. If you need metric push, this package does not provide it and you will need to build a sender.
- Which Zabbix API methods does flowti/zabbix-bundle cover?
- It covers authentication with user.login and user.logout, event acknowledgment, and read calls for hosts, host groups, events, and triggers. It does not include host.create, item.*, problem.get, or history.get. So it cannot provision hosts or items and does not fetch history data. Scope is read-plus-acknowledge, not configuration management.
- Does flowti/zabbix-bundle work with Zabbix 6.0 or 7.0 API tokens?
- Likely not without rework. The client uses legacy user.login and user.logout session-based authentication rather than the API-token model introduced in Zabbix 5.4 and 6.0. Modern Zabbix deployments also changed response envelopes, which the client may not handle. Expect to modify authentication and parsing for Zabbix 6.x or 7.x.
- Is flowti/zabbix-bundle production-ready or actively maintained?
- Treat it as high risk. It is a v0.0.1 pre-1.0 release with a single maintainer, negligible dependent ecosystem, and no visible security triage or test and CI signal. Pre-1.0 semver means method signatures, return shapes, and exception types can change without notice. Fork it, pin the version, and review the code before relying on it.
- How do I use flowti/zabbix-bundle services in Laravel without the Symfony bundle layer?
- Extract or wrap the underlying service classes and instantiate them through Laravel's container. You will need to replicate configuration manually and handle session lifecycle, including login, session hold, logout, and expiry, yourself. Be careful in queue workers, where stored credentials and shared session state can fail silently. Budget a short spike to confirm the services are constructor-injected and container-free.
- What are alternatives for sending Laravel health metrics to Zabbix?
- For metric push, implement the Zabbix trapper protocol with zabbix_sender or a small PHP sender, or use Zabbix native checks and scheduled scripts. For read and acknowledge workflows, a maintained Zabbix API client or direct JSON-RPC calls may be safer than a pre-1.0 Symfony bundle. If you only need health checks, a dedicated Laravel health package plus a sender is usually simpler.
- How much effort is it to adapt flowti/zabbix-bundle for a Laravel app?
- The assessment estimates a one-to-two day spike to validate reuse, down from earlier estimates because the method list bounds the surface. You still need to fork and pin, strip the Symfony bundle layer, replace legacy auth for modern Zabbix, and add tests. If your requirement is metric emission rather than read or acknowledge, stop early and build a sender instead.
Weaver
How can I help you explore Laravel packages today?