Changelog

This page tracks what’s new in GridNMS — both the platform (the web app you work in) and the collector software that runs at your sites.

Collector releases

This section lists what changed in each release of the GridNMS collector — the software that runs at your sites and feeds data back to GridNMS.

You don’t have to do anything to get these updates: new collector software is delivered automatically over the collector’s existing connection. When an update is ready, your collector shows an Update available note (with a short summary of what changed) on the Collectors page, where you can apply it immediately or let it roll out on your chosen schedule. See Updates for how delivery works.

Collector app for macOS & Windows

The desktop collector app has its own version, separate from the collector software it runs:

• v0.1.3 — the macOS app now stays awake in the background, so a sleeping display no longer drops the collector’s connection. Collector logs also rotate instead of being cleared when the app restarts, so the log tail from before a restart is preserved for troubleshooting.
• v0.1.2 — in-app reset: wipe a collector’s identity and re-enroll it with a new join token without reinstalling.
• A macOS installer for Intel Macs is now available alongside the Apple Silicon build on the portal Downloads page.

v0.59 – v0.61

These releases carry the collector side of the device identity and configuration-backup improvements described under Platform releases below:

• Devices report their make, model, software version, and DNS name so GridNMS can identify them automatically.
• A daily system scan keeps each device’s interfaces and identity details up to date, including forward and reverse DNS cross-checks.
• Configuration backups automatically pick the right backup command for each device, honoring per-class and per-device overrides.

v0.56 – v0.58

• SNMP traps carrying binary and text payloads are now decoded correctly.
• Service checks (TCP, UDP, and ping) run natively inside the collector — no external tooling required.
• Forwarded syslog messages now carry the full structured record, not just the message text, so more fields are searchable.

v0.50 – v0.55

• Devices whose SSH login only supports interactive prompts (common on appliances) can now be polled — these previously failed even with correct credentials.
• Per-device SSH credential overrides now reach the collector; previously only class-level credentials applied.
• Fixed DNS service checks and HTTPS checks on non-standard ports.
• Internal cleanup and dependency updates for stability and security.

v0.44 – v0.49

• API-based monitoring. The collector can poll cloud-managed platforms (starting with Cisco Meraki) over HTTPS. The same safety rule as network polling applies: the collector may only reach the API endpoints you configure.
• Run a single data collector on demand from a device’s detail page, instead of re-running the whole pack.
• Logs and telemetry now carry real device and interface names, so search results and charts are easier to read.
• On-demand collection failures are reported clearly instead of failing silently.
• Faster, more reliable telemetry delivery.

v0.42 – v0.43

• Device configuration backup. The collector runs your device’s backup command on schedule and ships the output back for versioned storage and change tracking — see Configuration backups.
• Internal reliability improvements.

v0.41

• Scheduled port scans now use their own probe profile, separate from network discovery, so each can be tuned independently.

v0.40

• Collectors now surface release notes directly in the app when a new version is available, so you can see what changed before applying an update.
• Stability and reliability improvements to log and metric forwarding.

Platform releases

New capabilities in the GridNMS web app, most recent first. Because GridNMS Cloud and the collector software update themselves, these arrive automatically; self-hosted instances pick them up on their next update.

Built-in detections

• Ready-made telemetry detections. GridNMS now ships a library of built-in, vendor-neutral detections — CPU and memory utilization, temperature, UPS battery, interface errors and discards, latency degradation, and unexpected device reboots. They work the same way on every supported vendor, arrive disabled by default (no day-one alert storm), and you enable just the ones you want under Admin → Detections. Each threshold detection clears itself when the reading recovers.
• Detections update themselves. New built-in detections are delivered automatically as they’re released — like the vendor and service-name reference data, with version tracking. Your own edits, enable/disable choices, and deletions are always preserved.

Cases & events

• Cases are the alert surface. Related events are grouped into a single case, and the case — not the individual event — is what notifies you. Case detail now includes a timeline viewer for the case’s member events (expandable rows with a field summary) and a panel explaining why the case was created. See Cases.
• Case rules with priority. Write your own grouping rules for how events roll up into cases. When more than one rule could match, the highest-priority rule wins — one case, no duplicates.
• A permanent event record. Events are now immutable, append-only records of what happened — they’re never edited or overwritten. Investigation status (open, closed, ownership) lives on the case instead. The events list shows which case each event belongs to, with a Hide case-managed events toggle to focus on what isn’t already being handled.
• Clearer events list. Events show the detection that produced them, how many log lines matched, and a richer description — with a one-click view matching logs link to jump from an event to the underlying logs.
• Notifications link straight to the source. Email and webhook notifications now deep-link to the exact event or case they’re about.

Devices & configuration

• Device configuration backup & diff. GridNMS backs up device configurations on a schedule, keeps a version history, detects real changes (ignoring volatile lines like timestamps), and shows side-by-side diffs. Each device gets a Config tab with versions, changes, the full config, and download. See Configuration backups.
• Automatic device identity. Make, model, software version, and DNS name are detected automatically and shown (and editable) on the device overview. A daily system scan keeps interfaces and identity details current.
• API-based monitoring — Cisco Meraki. Monitor cloud-managed devices through the vendor’s API, alongside your SNMP and SSH devices. Manage API credentials under Configure → API Credentials and attach an API target per device or per device class.
• Interface thresholds. Set traffic and utilization thresholds directly on an interface. Breaches raise events through the same detection pipeline as everything else, and recovery is recorded when the value comes back down.

Collector management

• Load-balancing profiles with a standby option. Choose how devices are assigned across the collectors at a site — including a dedicated backup collector that stays idle and only takes over when the primary collector goes offline.
• Updates respect your settings. Collector updates are only applied automatically when auto-update is on; otherwise you get an Update available notice and apply it on your own schedule.

Backup & restore

• Full configuration export & import. Export your entire GridNMS configuration (devices, credentials, monitoring, users and roles, notifications, detections, dashboards) as a single password-protected, encrypted file. Import previews every difference — row by row, field by field, classified New / Changed / Unchanged — and applies only what you tick.

API & automation

• API tokens. Create personal access tokens under Profile → API Tokens to script against GridNMS. Tokens act with your user’s permissions, and a published API reference documents the endpoints.

Reference data

• Data feeds. Curated reference datasets — device vendor identification and well-known service names — now update automatically over the collector’s existing connection, with per-dataset status, version history, and the ability to refresh or roll back to a specific version (Admin → Service Management → Data Feeds).
• Local overrides. Override any reference entry with your own value under System Config → Reference Data — your overrides survive dataset updates.

Quality of life

• About dialogs everywhere. Every GridNMS screen can tell you exactly which version you’re running, with a copy-to-clipboard summary for support requests.
• Consistent device search. Anywhere the app asks you to pick a device, you get the same fast, searchable device picker.

Self-hosted

• Update notice with one-click apply. Self-hosted administrators see an in-app banner when a new server release is available and can apply it with a single confirmed click — the update health-checks itself and rolls back automatically if something goes wrong. See Updates.

Reliability & alerting

• Durable collector offline alerting. GridNMS now reliably alerts you when a collector goes offline and clears the alert when it reconnects, so a site that drops off is never missed — even across GridNMS restarts.
• Maintenance windows. Schedule planned downtime for devices or sites so expected outages don’t generate noise. Notifications are suppressed for the window, and upcoming maintenance is shown on the dashboard and in reports.

Access control

• Site-aware roles and permissions. Roles can now be scoped down to individual sites, so a user can be given access to only the sites they’re responsible for. Every view, list, and action respects each user’s authorized sites, and you can switch your active site on the fly.

Monitoring & devices

• Vendor monitoring packs. Ready-to-use monitoring packs for Cisco (IOS-XE and Nexus), Juniper, Fortinet, Aruba, APC/UPS, Arista, HPE/Aruba, QNAP, and generic SNMP hosts — so common gear is monitored correctly out of the box.
• MIB browser. Browse the MIBs behind your monitoring packs directly in the app, grouped by the pack that provides them.
• Clearer service and topology views. Discovered services are now labelled with their well-known names (for example ssh (22/tcp)), and duplicate service entries are de-duplicated for a cleaner picture.
• Smarter metric collection. Polling intervals are tuned per data point so fast-changing counters stay responsive without over-collecting slower metrics.

Logs, detections & cases

• Log management and search. Collect syslog and SNMP traps from your devices, search across all of them, and drill into the fields that matter with a live fields sidebar.
• Detections and cases. Turn log and telemetry patterns into detections that raise events, and automatically group related events into cases so a storm of alerts becomes one actionable item.
• Configurable retention. Choose how long to keep logs — by age or by a fixed storage size — so your history stays predictable.

Security

• Mandatory multi-factor authentication. Sign-in is protected with passkey-first login, an authenticator-app fallback, and recovery codes, with policy controls for your organization.
• Hardened collector connections. Per-site IP allowlisting and one-time diagnostic access tokens give you tighter control over what each collector can reach.

Account & deployment

• Self-serve signup and customer portal. Sign up, manage your subscription, and handle billing from a self-service portal.
• Faster, more reliable cloud. GridNMS Cloud now runs on upgraded infrastructure for better performance and responsiveness.