-
Bug
-
Resolution: Unresolved
-
Normal
-
rhos-18.0.15, rhos-18.0.14 FR 4
-
None
-
1
-
False
-
-
False
-
?
-
rhos-conplat-observability
-
None
-
-
Known Issue
-
Done
-
-
-
-
-
Observability Sprint 22, Observability Sprint 23, Observability Sprint 24, Observability Sprint 25, Observability Sprint 2025 EOY
-
5
-
Low
To Reproduce Steps to reproduce the behavior:
- RHOSO Telemetry rabbitmq is scraping only one rabbitmq node instead of all nodes from cluster because target is rabbitmq service
- Here is scrapeconfig ressource deployed by telemetry operator:
apiVersion: monitoring.rhobs/v1alpha1 kind: ScrapeConfig metadata: creationTimestamp: "2025-05-06T11:03:53Z" generation: 2 labels: service: metricStorage name: telemetry-rabbitmq namespace: openstack ownerReferences: - apiVersion: telemetry.openstack.org/v1beta1 blockOwnerDeletion: true controller: true kind: MetricStorage name: metric-storage uid: bac7077a-xx resourceVersion: "487284413" uid: a87a0da5-xx spec: metricRelabelings: - action: labeldrop regex: pod - action: labeldrop regex: namespace - action: labeldrop regex: job - action: labeldrop regex: publisher scheme: HTTPS scrapeInterval: 30s staticConfigs: - targets: - rabbitmq-cell1.openstack.svc:15691 - rabbitmq.openstack.svc:15691 tlsConfig: ca: secret: key: tls-ca-bundle.pem name: combined-ca-bundle cert: {}
Expected behavior
- All rabbitmq nodes needs to be scraped in order to have a complete view of rabbitmq cluster.
Device Info (please complete the following information):
-
- OpenStack Operator Version: 1.0.10
- Deployed Version: 18.0.8-20250505.2
Bug impact
- This limit the information about rabbitmq
