Weave Code
Librenms Laravel Package
librenms/librenms
LibreNMS is an open-source network monitoring system built on PHP and Laravel. It auto-discovers devices via SNMP, supports a broad range of hardware, and provides alerting, billing, distributed polling, an API, and a web UI for tracking network health.
LibreNMS is a fully featured, open-source network monitoring system built with PHP and Laravel, offering auto-discovery and SNMP-based monitoring for a wide range of network hardware. It provides a modern, intuitive web interface for tracking device health, performance metrics, and alerts across your infrastructure.
- Auto-discovery of network devices and services via SNMP, with support for a vast array of vendors and platforms
- Flexible alerting with configurable rules, transports, and integrations for proactive incident response
- Distributed polling and horizontal scaling to monitor large, geographically spread networks
- Rich visualization including graphs, dashboards, and historical performance data
- Extensible API and integrations for automation and interoperability with existing tooling
Frequently asked questions about Librenms
- Can I install librenms/librenms as a Composer package in a Laravel application?
- No. LibreNMS is a full network monitoring application, not a Laravel library, so requiring it as a Composer dependency is a category error. Integrate with it as a sidecar service through its REST API and alert transports instead. Keep your Laravel application's schema and dependencies separate from LibreNMS.
- How do I integrate LibreNMS with a Laravel application?
- Use LibreNMS as a sidecar service: it owns SNMP discovery, polling, and threshold evaluation while Laravel owns customer workflows and reporting. Read monitoring data through token-authenticated REST API endpoints and receive events via alert transports or webhooks. Buffer incoming events in an internal table and build a stub consumer before defining a stable payload contract.
- Does LibreNMS support Laravel 10 or Laravel 11?
- LibreNMS is not a Laravel package, so Laravel version support does not apply. It runs on its own PHP 8.x, MariaDB, RRDtool, and net-snmp runtime matrix that you must pin and operate. Your Laravel app can be on any supported version as long as the integration uses HTTP APIs and webhooks.
- What are the GPL licensing risks of using LibreNMS in a proprietary Laravel product?
- LibreNMS is GPL-licensed, and the repository reports NOASSERTION, so legal review is required before design. Linking, forking, or shipping modified LibreNMS code inside a proprietary product creates copyleft exposure. The safer pattern is operating LibreNMS as a separate internal service and integrating over its REST API and webhooks, but confirm this with counsel.
- How do I send LibreNMS alerts to a Laravel webhook endpoint?
- Configure an alert transport in LibreNMS that POSTs to a Laravel route, then validate the incoming payload and queue processing for retries and deduplication. Start with one transport pointed at a staging endpoint and prove the event schema before scaling. Keep the webhook consumer idempotent because alert delivery can repeat.
- Can I reuse LibreNMS Eloquent models or database tables in my Laravel app?
- No. LibreNMS's Eloquent models and schema are internal, undocumented, and change between releases, so coupling to them is fragile. Isolate the database and never co-tenant it with your application schema. Consume the REST API instead of querying LibreNMS tables directly.
- What are the installation requirements for LibreNMS?
- LibreNMS requires PHP 8.x, MariaDB or MySQL, RRDtool, net-snmp, and a web server, plus poller daemons for discovery and polling. It is installed as an application, not via Composer into Laravel. Pin a specific release tag and a tested OS/runtime image rather than tracking master.
- How does LibreNMS scale for large device and port counts?
- RRDtool file storage can behave poorly at high device and port cardinality, so plan for Graphite or InfluxDB from day one if you expect large scale. Use distributed polling to spread load across pollers. Validate your 12- and 36-month device counts before committing to RRDtool.
- How should I test and upgrade LibreNMS API integrations in CI?
- Freeze the API version you consume and add contract tests against it in CI so upgrades surface breaking changes before the NOC sees them. Pin a specific LibreNMS release and runtime image; do not track master. Run a pilot cohort and validate alert round-trips before scaling to the full estate.
- What are alternatives to LibreNMS for Laravel-based infrastructure monitoring?
- Alternatives include Zabbix, Nagios, and PRTG, each with different licensing, API, and operational models. If you need an embedded monitoring experience, LibreNMS forking or iframing is unattractive, so evaluate API-first tools. For Laravel teams, the cleanest approach is a sidecar monitor integrated through REST and webhooks rather than a Composer dependency.
Weaver
How can I help you explore Laravel packages today?