Extending NetBrain with NetBox and Grafana: Turning Operational Truth into Shared Insight

NetBrain as the Operational Source of Truth

NetBrain’s role is clear:
it continuously collects live data from network devices, validates behavior, detects drift, and drives automation. 

That real-time digital twin is what allows NetBrain to answer questions like: 

• What is actually happening on the network right now? 
• Is this device configured correctly? 
• Why did this change break something? 

But there are categories of information that don’t live on the wire. 

Things like: 

• Physical rack position 
• Airflow direction 
• PDU and power details 
• Facility-level metadata 

That information is typically owned by hardware or data center teams and often already maintained in tools like NetBox. 

Rather than forcing customers to rebuild that data model inside NetBrain, the integration shown at NetBrain LIVE takes a more pragmatic approach. 

Using NetBox for What It Does Best

In the demo, NetBox was used as a reference system for physical and static infrastructure data. 

Hardware teams populate NetBox the same way they always have: 

• Devices are racked 
• Metadata is entered 
• Power, airflow, and location details are documented 

A NetBrain Plugin for NetBox then pulls that information into NetBrain via the NetBox API, mapping it into NetBrain custom properties and attaching it to the corresponding devices inside NetBrain. This is a NetBrain-built plugin that utilizes the NetBox API to pull hardware installation metadata into NetBrain. 

The key point from engineering: 

NetBox remains the source of truth for hardware installation data. NetBrain becomes the source of truth for the network itself. 

No workflows change for the hardware team. No duplicate data entry is required. NetBrain simply consumes and enriches that data with live network context.

How the Integration Works (Engineer Walkthrough)

The demo showed a simple but powerful flow: 

1. NetBox holds physical device data
   Rack position, airflow, and other properties are entered by the hardware team. 
2. NetBrain utilizes the NetBox API to pull that data into NetBrain
   The data is mapped into NetBrain custom properties and populated into an ADT (Automation Data Table). 
3. The ADT table updates on a schedule
   This process is automated and human-less — no manual refresh required. 
4. Grafana consumes the data automatically
   Using a lightweight trigger and API-based access, Grafana scrapes the updated table and refreshes dashboards in real time. 

During the demo, a device initially showed no physical metadata.
Once the table was rebuilt, the data appeared instantly and the Grafana dashboard updated from red to green without a manual refresh. 

That moment captured the value clearly:
NetBox data → NetBrain context → Grafana visibility. 

Why Grafana Matters in This Architecture

Grafana plays a critical but specific role. 

Not every user needs or should have direct access to NetBrain or NetBox. 

Grafana becomes the shared visualization layer, allowing: 

• Read-only access for broader teams 
• Secure exposure of validated data 
• A single dashboard view that blends physical and network truth 

Instead of giving hundreds of users accounts in operational tools, teams can expose NetBrain-validated data through Grafana, ensuring everyone sees the same trusted information. 

As discussed in the session: 

Grafana makes the data accessible to everyone without making everyone an operator.

Complementary by Design, Not Redundant

One theme came through clearly in the engineer discussion:
this is not a competitive story — it’s an architectural one. 

NetBox excels at static infrastructure modeling.
NetBrain excels at live network intelligence and automation. 

NetBrain can model physical properties if needed but when customers already have that data in NetBox, it makes more sense to leverage it rather than rebuild it. 

The result: 

• No disruption to existing processes 
• Faster time to value 
• A unified source of truth powered by live network data 

Or as one engineer summarized: 

If you already have the data, bring it into NetBrain.
Now you have the complete picture. 

The Bigger Outcome: One Truth, Many Consumers

This integration pattern solves a real operational challenge: 

• Hardware teams keep using NetBox 
• Network teams rely on NetBrain 
• Operations and leadership consume insights through Grafana 

All backed by NetBrain as the authoritative, real-time engine. 

The value isn’t just integration, it’s confidence.
Confidence that dashboards reflect reality.
Confidence that static data is tied to live behavior.
Confidence that automation decisions are based on truth, not assumptions. 

Final Takeaway

NetBrain doesn’t ask customers to rip and replace. 

Instead, it: 

• Pulls in the data you already trust 
• Enriches it with live network intelligence 
• Exposes it cleanly to the tools your teams already use 

That’s what was demonstrated at NetBrain LIVE 2025 and that’s what modern network operations require.