Redfish listener pipeline

Configuration overview for Redfish listener pipelines and the redfishCollector component.

Tags:

A Redfish listener pipeline uses envPlugins.sensorPipeline to discover sensor metadata and a pipeline component to emit telemetry. The direct collector pattern uses redfishCollector to poll each configured baseboard management controller (BMC) and send time-series models to downstream targets.

envPlugins:
  sensorPipeline:
    maxRedfishConnections: 1
    redfishDevices:
      - endpoint: ${secrets.redfish_endpoint}
        username: ${secrets.redfish_username}
        password: ${secrets.redfish_password}
    tls:
      insecureSkipVerify: true
    manifest:
      path: /data/redfish-sensor-manifest.yaml
      forceReload: false

components:
  redfish:
    type: redfishCollector
    timeout: 30s
    samplePeriod: 5s
    targets:
      - target: aggregator
        cap: 1000
        leaky: true

Security note

Do not use tls.insecureSkipVerify: true in production. This setting disables certificate verification for Redfish connections. Use it only for local testing or lab environments with self-signed certificates. For production deployments, configure a trusted certificate authority for the BMC endpoints and leave tls.insecureSkipVerify unset or set it to false.

Important fields:

envPlugins.sensorPipeline.redfishDevices defines BMC endpoints and credentials
envPlugins.sensorPipeline.manifest.path stores the discovered sensor manifest
redfishCollector.timeout controls Redfish HTTP request timeout
redfishCollector.samplePeriod controls polling frequency
redfishCollector.targets sends *timeseries.Model values to downstream components

The Helm chart’s default Redfish listener entry uses Redfish discovery with a UDP listener pipeline. Use redfishCollector when the listener itself should poll Redfish telemetry.