-
Bug
-
Resolution: Done
-
Normal
-
None
-
ACM 2.8.0
-
1
-
False
-
None
-
False
-
-
-
MCO Sprint 29, MCO Sprint 30
-
-
-
None
Metrics-collector failing to send logs from managed cluster to ACM Hub.
level=error caller=logger.go:55 ts=2024-09-02T08:16:06.852968737Z component=forwarder/worker msg="unable to forward results" err="Prometheus server reported unexpected error code: 502" level=error caller=logger.go:55 ts=2024-09-02T08:17:59.87454001Z component=forwarder component=metricsclient msg="error reading body" err="the incoming sample data is too long" level=debug caller=logger.go:40 ts=2024-09-02T08:18:19.963529746Z component=forwarder component=metricsclient timeseriesnumber=1654923 level=info caller=logger.go:45 ts=2024-09-02T08:18:35.903792064Z component=forwarder component=metricsclient msg="Metrics pushed successfully" level=warn caller=logger.go:50 ts=2024-09-02T08:24:07.001395707Z component=forwarder/worker msg="Failed to retrieve metrics" err="Prometheus server reported unexpected error code: 502" level=error caller=logger.go:55 ts=2024-09-02T08:24:07.024368507Z component=forwarder/worker msg="unable to forward results" err="Prometheus server reported unexpected error code: 502"
- is related to
-
ACM-14316 [Tech Preview] RFE: Make metrics-collector scalable by sharding federate calls
- Closed