Skip to content

Code structure

This document will try and provide a good overview of how the code is structured within LibreNMS. We will go through the main directories and provide information on how and when they are used. LibreNMS now uses Laravel for much of it's frontend (webui) and database code. Much of the Laravel documentation applies:

Directories from the (filtered) structure tree below are some of the directories that will be most interesting during development:

├─ app
├─ database
│  └─ migrations
├─ doc
├─ html
│  ├─ css
│  │  └─ custom
│  └─ js
├─ includes
│  ├─ definitions
│  ├─ discovery
│  ├─ html
│  │  ├─ forms
│  │  ├─ graphs
│  │  ├─ pages
│  │  └─ reports
│  └─ polling
├─ LibreNMS
├─ logs
├─ mibs
└─ rrd


This is the location of all the documentation for LibreNMS, this is in GitHub markdown format and can be viewed online


Most Laravel and Eloquent classes should be under this directory.


Classes that don't belong to the Laravel application belong in this directory, with a directory structure that matches the namespace. One class per file. See PSR-0 for details.


All legacy web accessible files are located here. New pages should follow the Laravel conventions.


This is the API routing file which directs users to the correct API function based on the API endpoint call.


This is the main file which all links within LibreNMS are parsed through. It loads the majority of the relevant includes needed for the control panel to function. CSS and JS files are also loaded here.


All used CSS files are located here.


This is a directory you can put custom css files into that won't interfere with auto updates


All used JS files are located here.


This directory is quite big and contains all the files to make the cli and polling / discovery to work. This code is not currently accessible from Laravel code (intentionally).

includes/discovery/, includes/polling/

All the discovery and polling code. The format is usually quite similar between discovery and polling. Both are made up of modules and the files within the relevant directories will match that module. So for instance if you want to update the os detection for a device, you would look in includes/discovery/os/ for a file named after the operating system such as linux: includes/discovery/ Within here you would update or add support for newer OS'. This is the same for polling as well.


This is where the majority of the website core files are located. These tend to be files that contain functions or often used code segments that can be included where needed rather than duplicating code.


This directory contains all of the files that are dynamically included from an ajax call to ajax/form.


All of the functions and calls for the API are located here.


This contains the majority of functions used throughout the standard web ui.


This directory contains global and OS specific graph definitions.


In here is a list of of files that generate PDF reports available to the user. These are dynamically called in from html/pdf.php based on the report the user requests.


This directory contains all of the ajax calls when generating the table of data. Most have been converted over so if you are planning to add a new table of data then you will do so here for all of the back end data calls.


This directory contains the URL structure when browsing the Web UI. So for example /devices/ is actually a call to includes/html/pages/, /device/tab=ports/ is includes/html/pages/device/


Contains the main librenms.log file by default, but can also contain your web server's logs, poller logs, and other items.


Here is where all of the mibs are located. Generally standard mibs should be in the root directory and specific vendor mibs should be in their own subdirectory.


Simple enough, this is where all of the rrd files are created. They are stored in directory based on the device hostname.


Contains all the database migrations. See Laravel docs for additional info:

In general to create a new table you should run:

php artisan make:model ModelName -m -c -r