Task · SKT-0168.04

Verify solace_prometheus_exporter metric names and add a Solace broker construct

Description

The demo includes two Solace PubSub+ Cloud brokers carrying near-real-time master-data propagation. The community solace_prometheus_exporter is a public source of emitted names. Source names and labels from its code or docs at a pinned release (queue depth/spool usage, flows, rx/tx rates, discards, client connections), write signals/solace.md, then add a construct. If names cannot be confirmed at a pinned version, add a cantfind PENDING and stop rather than emitting.

Acceptance Criteria

Definition of Done

Implementation Plan

Independently review inherited identity repair, compose root wiring and source catalogue, and gate before landing.

Implementation Notes

2026-10-23: stretch for the demo (broker leg of the response path); do only after SKT-0168.02.

Landed 0b4ec1a, pushed integrated 93a7f34 after guarded source-target repair review, dsreview and zero-finding composed CodeRabbit. Upstream v1.21.0 tag and 32 cached blobs authenticated. Real selected dump matches 80 sourced families; independent GlobalSystemInfo target and health dispatch, collision/fanout and zero-consumer protections retained. Exact composed remote just check and generation passed. Values remain documented synthetic assumptions, not a live broker capture.

Final Summary

Added independently declarable substrate-scoped Solace broker telemetry with pinned source names, labels, types and scrape-target gating. No unsupported family or native OTLP claim.

View the source file on GitHub