IBX SmartView

Facility monitoring for a colocation deployment: environmental readings, power, facility alerts, streaming and the asset hierarchy.

What it monitors#

IBX SmartView is Equinix's data center infrastructure monitoring service. It gives a customer the operating conditions of the facility around its own cages and cabinets, in near real time and as history: the air its equipment breathes, the power it draws, and the state of the electrical and mechanical systems that feed it.

A network team usually learns about a facility problem from its own equipment, after the fact: an inlet temperature alarm, a power supply that drops a feed. SmartView reports the same events from the facility side, with their cause. Through the API that data goes where the rest of the monitoring already is.

IBX SmartView data and its uses. Readings and events are read on request or pushed through a streaming subscription, and the asset hierarchy ties an infrastructure event to the cages it affects.

What it is used for#

Use	Data	Page
Watch the environment of a cage	Temperature and humidity per sensor and zone	Environment and power
Know about a power event when it happens	Power events with trigger and current values; alert configurations with thresholds	Environment and power
Follow facility incidents	System alerts on electrical and mechanical infrastructure	Environment and power
Feed an existing monitoring system	Streaming subscriptions to AWS IoT, Azure Event Hub, a webhook or a REST endpoint	Streaming and assets
Find which cages an infrastructure fault affects	Location and power hierarchy, affected assets	Streaming and assets
Plan power	Current and trending power draw	Environment and power

Clients#

IBXSmartView is the entry point, obtained with eq.ibxSmartView() or new IBXSmartView(credentials). The samples call it smartView.

Accessor	API	Covers
`environmentals()`	`dcim/v3`	Sensor readings
`powerEvents()`	`dcim/v3`	Power events and power alert configurations
`systemAlerts()`	`dcim/v3`	Facility system alerts
`streamingSubscriptions()`	`dcim/v3`	Push delivery to AWS IoT, Azure Event Hub, a webhook or a REST endpoint
`hierarchy()`, `smartViewAssets()`	v1	Location and power hierarchy, asset details, affected assets, tag points
`legacyEnvironmentals()`, `legacyPower()`	v1	The earlier environmental and power APIs

The v1 calls require the account number, and the service answers HTTP 400 without it. The asset calls also require the IBX and the asset classification. The SDK rejects a call with any of them missing before it is sent.

Use with the other APIs#

A power event can be compared with the open trouble tickets for the same IBX.
Readings can be delivered to the same sink as Fabric stream subscriptions.
The MCP tools ibx_get_environmentals and ibx_list_power_events return the two reads (MCP server).
The colocation operations walkthrough combines power events with tickets, and the observability walkthrough sends SmartView data to the same sink as Fabric metrics.