Technical Overview

Architecture

The VCF Servers Insight adapter is a Go-based containerized collector that runs on a VMware Aria Operations Cloud Proxy. It communicates with Dell iDRAC / HPE iLO (Redfish) and Dell OpenManage Enterprise (OME) over HTTPS and pushes collected data to Aria Operations through the collector framework.

┌─────────────────────┐      Redfish / OME HTTPS       ┌──────────────────────┐
│  Aria Operations     │ ◄────────────────────────── │  iDRAC / iLO / OME   │
│  Cloud Proxy        │   /redfish/v1/... | /api/...   │  (server platforms)  │
│  ┌───────────────┐  │                              └──────────────────────┘
│  │ VCF Servers   │  │         HTTPS :443
│  │ Insight       │  │ ◄──────────── register.indevops.com (image pull)
│  │ Adapter       │  │
│  │ (Go container)│  │
│  └───────────────┘  │
└─────────────────────┘

Authentication

InterfaceMethod
Dell iDRACHTTP Basic authentication
Dell OMEHTTP Basic authentication
HPE iLOSession-based (X-Auth-Token via /redfish/v1/SessionService/Sessions/)

A single shared credential set (username / password) is used; per-host credentials are resolved for multiple idrac_host entries.

Management Paths

Dell iDRAC (Redfish)

Connects directly to each iDRAC, collects systems, chassis, managers, and per-system metrics:

  • CPU/memory utilization from Telemetry MetricReports (/redfish/v1/TelemetryService/MetricReports/...) — dynamic report discovery
  • CPU, memory, storage, network, BIOS, thermal, power from Redfish endpoints
  • Relationships: Adapter → Physical Server; (external) vSphere HostSystem → Physical Server

Dell OpenManage Enterprise (OME)

Connects to the OME console, fetches the device list, and for each server also connects to the blade's iDRAC (via IP from deviceManagement):

  • OME-aggregated: temperature, power, uptime, inventory (fans, PSU, OS, NIC)
  • Per-blade iDRAC Redfish: CPU/memory/storage/network/BIOS
  • Network adapters use the OME serverNetworkInterfaces (port/partition model)
  • Network switches use OME portInformation (per-port metrics)
  • Relationships: Adapter → Chassis/Server; Chassis → Server/Switch; (external) vSphere HostSystem → Physical Server

HPE iLO (Redfish)

Connects directly to each iLO with session auth:

  • CPU/memory utilization from Oem.Hpe.SystemUsage (CPUUtil, MemoryBusUtil) — Intel only (AMD/ARM do not expose telemetry)
  • Uptime from PowerOnMinutes
  • Storage, network, BIOS, thermal, power from Redfish
  • Relationships: Adapter → Physical Server; (external) vSphere HostSystem → Physical Server

Redfish API Endpoints (iDRAC / iLO)

EndpointMethodPurpose
/redfish/v1/SystemsGETList systems
/redfish/v1/ChassisGETList chassis
/redfish/v1/ManagersGETBMC/firmware info
/redfish/v1/Chassis/{id}/ThermalGETTemperature + fans
/redfish/v1/Chassis/{id}/PowerGETPower + PSUs
/redfish/v1/Systems/{id}/ProcessorsGETCPU
/redfish/v1/Systems/{id}/MemoryGETDIMM
/redfish/v1/Systems/{id}/StorageGETStorage controllers
/redfish/v1/Systems/{id}/EthernetInterfacesGETNICs
/redfish/v1/Chassis/{id}/NetworkAdaptersGETNIC model/firmware (Dell)
/redfish/v1/Systems/{id}/BaseNetworkAdaptersGETNIC model/firmware (HP)
/redfish/v1/TelemetryService/MetricReportsGETMetric reports (CPU/memory)
/redfish/v1/TelemetryService/MetricReports/{id}GETReport content
/redfish/v1/SessionService/Sessions/POST/DELETEiLO session login/logout

OME API Endpoints

EndpointMethodPurpose
/api/DeviceService/DevicesGETList devices
/api/DeviceService/Devices({Id})/TemperatureGETTemperature
/api/DeviceService/Devices({Id})/PowerGETPower
/api/DeviceService/Devices({Id})/SystemUpTimeGETUptime
/api/DeviceService/Devices({Id})/InventoryDetailsGETInventory (fans, PSU, OS, NIC, ports, FRU)

Collection Cycle

Collection is incremental and server groups are collected in parallel (errgroup, limit 5) for iDRAC and OME to keep within the collection window.

  1. Select interface — iDRAC / OME / iLO
  2. Authenticate — basic (iDRAC/OME) or session (iLO)
  3. Fetch systems/devices — systems list (Redfish) or device list (OME)
  4. Collect per server (parallel) — CPU/memory/telemetry, temperature, power, storage, network, BIOS
  5. Collect chassis — temperature, power, fans, PSUs
  6. Collect network switches (OME) — port count, active ports, per-port detail
  7. Build objects — properties and metrics per resource kind
  8. Build relationships — containment and external (vSphere)
  9. Logout / cleanup (iLO)

Non-fatal errors are logged and skipped; a partial collection is always returned.

Dashboards

The Management Pack ships three dashboards:

DashboardWidgetsPurpose
VCF Servers InsightObject List, Adapter Performance Scoreboard, Metric Picker, Metric ChartAdapter overview, collected objects, adapter CPU/memory, ad-hoc metric analysis
Physical Servers PerformanceServers Performance Scoreboard, Object Relationship, Servers ListPer-server performance metrics, health/BIOS/BMC/model columns
Physical Servers HealthHealth Heatmap, Active Alert ListHealth status overview and only active alerts

Object Model

Physical Server

  • Identifiers: name, serial
  • Groups/properties: General (manufacturer, model, uuid, power state, health, BIOS, ESXi version, CPU/memory usage), CPU, Memory, Storage Controllers, Physical Disks, Network Adapter, Chassis, Power Supply, Fan, BIOS
  • Metrics: CPU Utilization, Memory Utilization, System Uptime, Temperature, Power Consumption, link speed/status

Chassis

  • Identifiers: name, serial
  • Groups/properties: General (temperature, power, model, health), Power Supply, Fan
  • Metrics: Temperature, Power Consumption, fan speed, PSU output/input

Network Switch (LAN)

  • Identifiers: name, service_tag
  • Groups/properties: General (Port Count, Active Port Count, model, manufacturer, serial, MAC, firmware, IP), Network Port (per active/Up port: status, speed, role, MTU)
  • Metrics: Port Count, Active Port Count, Port Speed Mbps

Alert Definitions

The pack ships 34 alert definitions covering:

  • CPU utilization (warning ≥50%, critical ≥80%)
  • Memory utilization (warning ≥50%, critical ≥80%)
  • Temperature (warning ≥75°C, critical ≥85°C)
  • Fan, power supply, chassis, server, network switch, NIC, physical disk, DIMM, storage controller health states
  • BMC connection lost / server/chassis power off

Relationships

  • Containment: Adapter → Chassis/Server; Chassis → Server/Switch (OME)
  • External: vSphere HostSystem → Physical Server (match by HostSystem name)