Bug 1634303 - Filter for non-critical namespaces needs to be tighter; [criticalprefix]-.* vs [criticalprefix].*
Summary: Filter for non-critical namespaces needs to be tighter; [criticalprefix]-.* v...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.z
Assignee: Frederic Branczyk
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-29 15:49 UTC by Justin Pierce
Modified: 2019-01-10 09:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-10 09:04:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0024 0 None None None 2019-01-10 09:04:07 UTC

Description Justin Pierce 2018-09-29 15:49:44 UTC 
Description of problem:

In namespace filters like:
>>>>
alert: KubeDeploymentReplicasMismatch
expr: kube_deployment_spec_replicas{job="kube-state-metrics",namespace=~"(openshift.*|kube.*|default|logging)"}
  != kube_deployment_status_replicas_available{job="kube-state-metrics",namespace=~"(openshift.*|kube.*|default|logging)"}
for: 1h
<<<<

The existing regular expression allows in namespaces like "kubeless" which is a standard user project. 

Suggesting something like:
(openshift-.*|kube-.*|default|logging|kube|openshift)


Version-Release number of selected component (if applicable):
v3.11.16

How reproducible:
100%
Comment 1 Justin Pierce 2018-09-29 15:53:33 UTC 
Also affects other alerts like: KubePodNotReady, KubeQuotaExceeded, and others.
Comment 2 minden 2018-10-01 12:28:42 UTC 
Tracked here: https://github.com/openshift/cluster-monitoring-operator/issues/112

Thanks.
Comment 3 lserven 2018-10-01 13:06:55 UTC 
Here's a PR with the fix: https://github.com/openshift/cluster-monitoring-operator/pull/113
Comment 4 minden 2018-10-04 08:58:19 UTC 
https://github.com/openshift/cluster-monitoring-operator/pull/113 is merged. We will cherry-pick it into the release-3.11 branch so it can be released in Openshift 3.11.z.
Comment 5 Junqi Zhao 2018-10-24 07:20:57 UTC 
Issue is fixed
Version: v3.11.30-1

Please change to ON_QA
Comment 6 Junqi Zhao 2018-10-25 01:01:47 UTC 
Per Comment 5, move to VERIFIED.
Comment 8 errata-xmlrpc 2019-01-10 09:04:01 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, 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/RHBA-2019:0024
Note You need to log in before you can comment on or make changes to this bug.