Data Feeds

GridNMS ships with a handful of reference datasets and built-in rule packs — things like the vendor list used to identify devices by their hardware address, or the library of built-in detections for common device-health problems. These are curated centrally and delivered to your instance automatically through your platform connection. Data Feeds is where you see the state of each one and choose which version your organization is running.

Open it from Configure → Service Management → Data Feeds.

What’s in the list

Each row is one feed:

Column	What it tells you
Feed	The feed’s name and a short description of what it covers. If you’ve added any local overrides for it, a link shows how many.
Status	Whether your organization is caught up, or a newer version is available (see below).
Installed	The version your organization is currently running, its row count, and when it was applied.
Latest	The newest version the platform has published.
Actions	Pick a specific version and activate it, or revert to the previous one.

The feeds

Feed	What it does for you
MAC Vendors (IEEE OUI)	Identifies a device’s hardware vendor from the first part of its MAC address.
Well-known Ports	Labels the services your devices expose by port number — for example, showing “HTTPS” instead of just “443”.
Built-in Telemetry Detections	A vendor-agnostic set of detections for common device-health problems — high CPU, low memory, temperature, UPS state, unexpected reboots. New rules arrive turned off, and if you’ve customized or deleted a built-in rule, that choice is preserved — an update never overwrites it.
OCSF Extraction & Classification Rules	The built-in rules that recognize incoming log formats and pull structured fields out of them (see The Log Data Model and Field Extraction). New versions add support for identifying more log formats automatically, with no product update needed.

Status meanings

• Up to date — your organization is running the newest version the platform has published.
• Update available — a newer version has been published. You aren’t moved onto it automatically; activate it yourself when you’re ready (see below).
• Never imported — this feed hasn’t been applied to your organization yet.
• Platform unreachable — this instance has no platform connection configured, so feed status can’t be checked. This is expected on some self-hosted installations; see Choosing a Deployment.

Activating or reverting a version

New versions arrive on your instance automatically as the platform publishes them, but nothing is applied to your organization until you choose to. For each feed:

• Pick a version from the dropdown next to it and click Load to activate that version for your organization. This choice is per-organization — if other organizations share this instance, they’re unaffected.
• Click Revert to go back to the most recent version older than the one currently active. It’s disabled if there’s no earlier version available to revert to.

Only the versions this instance has already downloaded from the platform show up in the dropdown — there’s no manual “check for updates” action, since new versions arrive on their own through the platform connection.

Where to go next

• Reference Data — add your own overrides on top of the MAC Vendors and Well-known Ports feeds.
• Detections — see and manage the detections these feeds deliver, including the Built-in Telemetry Detections pack.
• The Log Data Model and Field Extraction — how incoming logs are recognized and broken into fields.
• Service Management — live health of the background services that keep monitoring running.