Network and Host Monitoring: NEMS Mesh and What's Next

For those new to the project, NEMS Linux is a turnkey, pre-configured Nagios Core appliance. It wraps the proven Nagios Core engine in a complete, unified platform: no raw config files (web-based management with automated syntax validation before changes go live), an out-of-the-box NOC tactical display with real-time status monitoring and spoken audible alerts, a RESTful API for programmatic control, and native alerting to Microsoft Teams, Slack, Discord, Telegram, Email, Pushover, SMS, and more without writing custom scripts. The Enterprise edition is a flat annual subscription covering unlimited hosts and services with zero per-device fees, and the SOHO edition is 100% free forever for home labs and small sites.

NEMS Linux creator Robbie Ferguson has posted what he calls "the most ambitious leap in NEMS history" on the project's Patreon. With the rapid adoption of NEMS Linux 1.8, the platform that started over ten years ago as a personal labor of love has matured into what Ferguson describes as "a formidable, enterprise-grade monitoring powerhouse." The foundation he is building right now retires the long-serving NConf configuration manager, unlocks a new distributed monitoring feature called NEMS Mesh, and is underpinned by a new NEMS API v2 that is already in the dev lab. The expected timeline is between 12 and 24 months to fully realize, test, and polish.

More Than a Dashboard: The Central Command Vision

The community has already had a first look at NEMS Central Command, and Ferguson says the feedback has been incredible. At a glance it might look like just a sleek new tactical display for your server. Under the hood, it is a complete architectural reimagining: an ultra-lightweight database backend, an advanced RESTful API, and a robust User Level Access system designed to redefine how NEMS interacts with Nagios Core. As Ferguson puts it, "It isn't just a cosmetic refresh; it's the launchpad for where NEMS is going next."

Turning the Page: Retiring NConf

For years, NConf served exceptionally well as an accessible bridge away from manually editing Nagios configuration text files. But it was designed over a decade ago around a rigid MySQL database model tailored strictly for a single, local Nagios instance. Modern monitoring demands multi-node, hybrid, and remote deployments, and NConf was never engineered to handle those architectures. In Ferguson's words, it "has officially become the single biggest bottleneck holding back what I want to build."

In its place, Ferguson is engineering a native configuration engine built directly into NEMS Central Command, unifying management, deployment, and tactical monitoring under a single, cohesive interface.

Unlocking NEMS Mesh

Retiring NConf opens the door to the feature Ferguson is most excited about: NEMS Mesh. With NEMS Mesh, you can drop lightweight NEMS nodes across all your client sites, branch offices, or cloud regions, while aggregating all reporting, alerts, and management into a single, centralized NEMS Central Command console that you host yourself, just as you currently do with NEMS Linux.

Under NConf's architecture, this was structurally impossible. Under the new NEMS Central Command Configurator, it will be native. One node in each branch office or client site, one console at HQ. The nodes report in, and the console aggregates.

Building NEMS API v2

While many across Canada were relaxing over the Thanksgiving long weekend, Ferguson spent a fair bit of his in the dev lab writing code. The backbone of the transition is NEMS API v2:

• Secure Token-Based Authentication: Clean, modern, programmatic control over your monitoring engine.
• Full Configuration Management: Direct compilation of Nagios configs, loading hosts, check commands, and services dynamically.
• Human-Readable Error Handling: Unlike NConf, which notoriously spits out cryptic, raw Nagios syntax errors when a config fails, NEMS API v2 catches problems early and translates them into plain, actionable language.

As of the post, the API can already dynamically add hosts and compile Nagios configurations cleanly. Once the API logic is sealed, Ferguson will immediately begin work on the frontend UI that will officially replace NConf.

The Road Ahead

Rebuilding the entire configuration pipeline and rolling out NEMS Mesh is a massive technical endeavor. Ferguson expects the overhaul to take between 12 and 24 months to fully realize, test, and polish, and those who support the project get early access to the new features in testing. As always, NEMS Linux remains the work of one solo developer building on evenings, weekends, and holidays. "Your support is what keeps the servers running, the lab powered, and these updates rolling out." NEMS Linux 1.8 is available now at nemslinux.com.

What to Run It On

The central console is the most important piece of a NEMS deployment, and it needs to handle a full Nagios Core stack, the Central Command UI, and the new API with room to spare. That is exactly what the ODROID-N2+ is built for.

ODROID-N2+ : from $94.95 (2GB) / $121.95 (4GB)

Amlogic S922X with quad-core Cortex-A73 at 2.2GHz plus a dual-core A53 cluster, 2GB or 4GB DDR4, Gigabit Ethernet, and an HDMI 2.1 port for 4K@60Hz output. The 4GB configuration gives you headroom for a full Nagios Core stack plus the Central Command UI and the new API. The large passive heatsink keeps it quiet, and power draw is about 2.2W idle and 5.9W under full CPU stress, so a 24/7 monitoring box costs very little to run. The HDMI 2.1 output means you can hang it next to a wall-mounted monitor and use the Central Command tactical display out of the box, exactly as the NEMS Tactical Overview is designed to be used. ODROID-N2+

The N2+ takes a 12V/2A power adapter, and a Linux Starter Kit is available if you want the board, power supply, and storage bundled. As for the lightweight mesh nodes that NEMS Mesh will eventually support, Ferguson told ameriDroid.com he is looking to get his hands on an ODROID-C5 from us to port NEMS Linux to, so that one is worth watching for a future post.