Bug 1978091 - Cluster Utilization item Network transfer shows 'No datapoints found'
Summary: Cluster Utilization item Network transfer shows 'No datapoints found'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.9.0
Assignee: Simon Pasquier
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-01 06:38 UTC by Yadan Pei
Modified: 2021-10-18 17:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:37:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 1296 0 None open Bug 1978091: fix node_exporter recording rules for cluster network dashboards 2021-07-23 09:45:23 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:37:50 UTC

Description Yadan Pei 2021-07-01 06:38:29 UTC
Description of problem:
no metrics data returned for 'Network transfer' item in Cluster utilization card

Version-Release number of selected component (if applicable):
4.9.0-0.nightly-2021-06-30-123441

How reproducible:
Always

Steps to Reproduce:
1. cluster admin goes to Home -> Overview and check "Cluster utilization" card
2.
3.

Actual results:
1. Network transfer item shows 'Not available', the query returns "No datapoints found"


Expected results:
1. Network transfer query should return correct usage data

Additional info:

Comment 2 Robb Hamilton 2021-07-06 20:18:23 UTC
Pawel, are you aware of any changes that would have resulted in the updated queries you provided in https://github.com/openshift/console/pull/8800 to stop working?  I do not believe anything has changed on the console side that would have resulted in this new bug.

Comment 3 Robb Hamilton 2021-07-13 12:31:25 UTC
Reassigning to the monitoring team for investigation as it appears Pawel is on PTO and I need another monitoring team member to determine if there were monitoring changes that would have resulted in the updated queries Pawel provided in https://github.com/openshift/console/pull/8800 to stop working.

Comment 4 Simon Pasquier 2021-07-23 08:58:38 UTC
"instance:node_network_receive_bytes_excluding_lo:rate1m" has been renamed to "instance:node_network_receive_bytes_excluding_lo:rate5m" in https://github.com/openshift/cluster-monitoring-operator/pull/1214/files#diff-a94cb3a05102915974e53760083acd2687daeb37b792c060d2ded1912baab004 because of a change in the upstream node_exporter mixin.
We should probably improve kube-prometheus upstream to adjust the rate interval value based on the chosen scrape interval.

Comment 6 Junqi Zhao 2021-07-26 02:15:21 UTC
checked with 4.9.0-0.nightly-2021-07-25-125326, Network transfer query returns correct usage data, see the picture

Comment 14 errata-xmlrpc 2021-10-18 17:37:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:3759


Note You need to log in before you can comment on or make changes to this bug.