-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
Currently, RHACS Central metrics related to secured clusters expose only the ClusterID label and not the human-readable cluster name.
Request: Add ClusterName as an additional label to Central and Sensor metrics that reference secured clusters, for example:
Example:
{{rox_central_sensor_connected{ClusterID="3b920717-a1ec-4a75-bc63-c9c8b5a81135",connection_state="STARTUP"} 2 }}
In this metric, only ClusterID is available. There is no ClusterName label.
In operational monitoring systems (Prometheus/Grafana), clusters are identified by name (e.g., ccp-ne-acs01b). Without the cluster name in metrics, customers must maintain an external mapping between:
ClusterID ↔ ClusterName
Expectation:
rox_central_sensor_connected{ ClusterID="3b920717-a1ec-4a75-bc63-c9c8b5a81135", ClusterName="ccp-ne-acs01b", connection_state="STARTUP" } 2
Business Requirement
- Improve observability and dashboard readability
- Simplify alerting and reporting
- Avoid maintaining external ID-to-name mapping logic
- Reduce operational complexity in large multi-cluster environments
- clones
-
RFE-8895 Improve image scan status when image is no longer present in registry
-
- Backlog
-