Changelog

Find and fix problems across your networks and pipelines faster. This release surfaces failures where you are already looking, collapses noisy logs into something readable, and makes pipeline runtime behavior more predictable under load.

See network and pipeline errors at a glance

Networks and their managed pipelines now make errors visible without digging. The network list shows how many pipelines have failed and how many nodes are missing carriers, and on the network page the relevant tab titles flag failed pipelines and log errors. Go straight to what needs attention instead of opening each pipeline to check.

Deduplicated pipeline logs

Pipeline logs now aggregate duplicate entries into a single line with a count. Bursts of identical messages no longer bury the events that matter, making it far easier to read what a pipeline is actually doing.

Read the API reference here.

Download logs over gRPC

New gRPC endpoints let you download the full log for the application, a pipeline run, a network, or a network instance. Pull logs into your own tooling for archival, support, or offline analysis.

Improvements

• MTU / Improved automatic component MTU discovery so components settle on the correct MTU more reliably.
• Pipelines / Improved memory management of pipeline components for more deterministic behavior when many components are running.
• Pipelines / A pipeline now shuts down mid-run if a UDP component is bound to a network interface that is not available on the OS, instead of continuing in a broken state.
• Pipelines / A pipeline's startup policy can now be set over gRPC.
• Server / The app can now be started with an HTTP server on port 3001.

Fixes

• Networks / Fixed being unable to set a network node carrier's bandwidth priority over gRPC.
• Pipelines / Fixed lifecycle handlers during pipeline shutdown incorrectly flagging the pipeline with an unexpected-failure status.
• Pipelines / Fixed pipelines not printing their log messages on fatal shutdown.
• UI / Fixed pipelines sometimes not loading in the UI.

NanoPing 10.4.2 is a pure stabilization release. The hub server and control plane are steadier under load, and the pipeline frontend behaves correctly when moving between tabs or resizing panels. A handful of underlying dependencies have also been refreshed for reliability.

NanoPing 10.4.1 speeds up template-based deployments and makes the pipeline list easier to read at a glance. Template pipelines now start in parallel, the pipeline list surfaces loading and error states for status, and log lines without a message field are no longer silently dropped.

Template Deployments

Template pipelines can now be started in parallel instead of one at a time. Deployments that fan out to many instances finish substantially faster, so rolling a fresh template into production no longer waits on a serial startup chain.

Pipeline List Status

The pipeline list now shows explicit loading and error states while fetching pipeline status, instead of leaving rows ambiguous when a fetch is in flight or has failed. Scanning a long list of instances becomes easier because you can tell at a glance whether a status is still loading, failed to load, or up to date.

Logging

Pipeline log lines that arrived without a message field were previously discarded. The full log line is now used as a fallback for the message, so nothing gets silently dropped on its way through the logging pipeline.

NanoPing 10.4.0 sharpens the tools you reach for when something goes wrong. Pipeline log timestamps render correctly again, structured JSON is back in the logging protobuf, networking handles interfaces with multiple local addresses, and a long list of deprecated components has been retired for good.

Pipeline Logs

Timestamps in the log viewer now match when events actually happened, so tracing a problem across components lines up with what you see in the pipeline. Valid JSON log lines are once again carried through the protobuf logging message data field, restoring the structured payloads that downstream tools rely on.

Pipeline Networking

Pipeline networking now supports interfaces that expose multiple local addresses, so hosts with multi-homed NICs or multiple IPs bound to the same interface work without extra configuration.

Removed Deprecated Components

A set of components marked deprecated in earlier releases has now been removed. Pipelines still using any of the following should migrate before upgrading:

• Bandwidth Constrictor
• Bandwidth Constrictor Sequencer
• ChaCha20 Decrypt
• ChaCha20 Encrypt
• Delay Fixed
• Delay Fixed Sequencer
• Delay Jitter
• Gilbert Elliot Loss
• Kodok Decoder
• Kodok Encoder
• Periodic Burst Loss
• Random Burst Loss
• Throughput Tracker
• Throughput Traffic Source
• Timed Burst Loss
• UDP
• Uniform Loss
• Uniform Loss Sequencer

NanoPing 10.3.0 brings automatic layout to pipeline diagrams. Pipelines without saved coordinates now arrange themselves into a clean, readable structure, and a new button lets you re-layout any diagram on demand.

Pipeline Auto-Layout

Open a pipeline that has no saved coordinates and the diagram now lays itself out automatically, so you see a clean structure instead of stacked nodes at the origin. For diagrams that have drifted into a tangle over time, the new "Auto-layout" button in the pipeline diagram rearranges everything in one click.

Fixes

• gRPC optionals — The gRPC bridge for network instance handling in 10.2.1 used protobuf optional fields instead of oneof. This has been reverted. If you already integrated against 10.2.1, you will need to update your code.
• gRPC Metrics — Fixed streamed pipeline metrics missing their timestamp.

NanoPing 10.2.1 focuses on making pipeline management simpler. Pipelines can now be controlled and configured from a single dashboard, including remote pipelines across multiple nodes. Uploaded configs are automatically migrated to match your NanoPing version. This release also adds a jitter buffer to the Raft component for smoother video delivery and makes log UUIDs clickable for easier navigation.

Manage all your pipelines from a single dashboard

Start and stop any pipeline, including network pipelines, directly from the pipeline list or pipeline view. Toggle a pipeline on or off right where you see it, no more navigating through multiple screens to control pipeline state. The auto-start toggle lets you configure whether a pipeline should launch automatically when its node comes online.

Create, view, edit, and delete remote pipelines from a single dashboard. Teams managing distributed deployments across multiple nodes can now handle their full pipeline configuration from one interface, removing the need to switch between nodes to manage pipelines.

Raft Jitter Buffer

The Raft component now includes a jitter buffer that stabilizes the output data stream. Components downstream, such as video decoders, can function more reliably with consistent packet timing.

UUID Links in Log Viewer

UUIDs in log output are now clickable links. Click any entity UUID to jump directly to that pipeline, pipeline run, node, or network. Run IDs are now also reflected in the URL, making it easy to share a link to a specific run.

Hub Status Indicator

A new status indicator in the dashboard footer shows your hub connection state at a glance. No need to navigate away from your current view to check connectivity.

Pipeline Migration on Upload

Upload a pipeline config and the system automatically migrates it to match your current version of NanoPing. No manual version adjustments needed.

Fixes

• KPIs — Fixed issue where adding new KPIs during a run would not display values until the pipeline was restarted
• KPIs — Added support for missing KpiEvaluatedMetric value types
• Nodes — Fixed nodes not updating on hub server when editing node settings such as name and metadata
• Nodes — Node name now automatically updates in the nodes list and node selector when changed
• Splitter component — Fixed issue with packets being duplicated with wrong annotations such as the wrong destination address