Created attachment 1349806 [details] the timeout message Description of problem: Metrics collection from OCP 3.7 using Prometheus may hit timeout while collecting metrics. a. the default timeouts are too small b. users can not set new timeout values to fit their system How reproducible: Read metrics from an OCP using Prometheus metrics and having a lot of metrics collected Steps to Reproduce: 1. Have a system with at least 10 nodes with 10 pods each and 10 containers each. 2. Try to open the ad-hoc metrics page. Actual results: a timeout message Expected results: the metrics collected from prometheus
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
submitted upstream: https://github.com/ManageIQ/manageiq/pull/16429 https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/167
Merged upstream: https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/167