Bug 1511341

Summary: Metrics collection from Prometheus may hit timeout
Product: Red Hat CloudForms Management Engine Reporter: Yaacov Zamir <yzamir>
Component: C&U Capacity and UtilizationAssignee: Red Hat CloudForms Documentation <cloudforms-docs>
Status: CLOSED CURRENTRELEASE QA Contact: Einat Pacifici <epacific>
Severity: medium Docs Contact:
Priority: high    
Version: unspecifiedCC: jhardy, lavenel, obarenbo, yzamir
Target Milestone: GAKeywords: TestOnly
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.10.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1513116 (view as bug list) Environment:
Last Closed: 2018-06-21 20:42:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1513116    
Attachments:
Description Flags
the timeout message none

Description Yaacov Zamir 2017-11-09 07:54:27 UTC
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

Comment 2 Dave Johnson 2017-11-09 08:03:01 UTC
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.

Comment 4 Dave Johnson 2017-11-09 09:44:26 UTC
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.

Comment 6 Yaacov Zamir 2017-11-13 12:39:19 UTC
Merged upstream:
https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/167