From LNMP to Ephemres: What Changed Between v3.0 and v3.3.5
LNMP is now Ephemres. What changed from v3.0 to v3.3.5: NetFlow and IPFIX telemetry, a near zero-dependency Python core, and dashboards that stopped guessing.
5 labs in this category.
LNMP is now Ephemres. What changed from v3.0 to v3.3.5: NetFlow and IPFIX telemetry, a near zero-dependency Python core, and dashboards that stopped guessing.
How production scaling and improved Python architectural practices led to LNMP v3.0: deterministic 32s/28s sweeper concurrency, typed SQLAlchemy 2.0 repositories, Server-Sent Events, dual PostgreSQL/Redis storage, and multi-protocol synthetics.
How production multi-user deployments led to LNMP v2.0: implementing a 4-phase Sugiyama topology engine, TimescaleDB compression, top-of-minute write semaphores, and solving in-memory authentication deadlocks.
How we upgraded the Lightweight Network Monitoring Platform with TimescaleDB continuous aggregates, pure-Python FHRP inspection, Differential RCA, and an in-memory DAG topology engine.
Network visibility isn’t just a nice-to-have; it’s essential for keeping operations running smoothly