Bug 1913443 - Rename filename of prometheus recording file to match its content
Summary: Rename filename of prometheus recording file to match its content
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.7.0
Assignee: Hui Kang
QA Contact: Qiaoling Tang
URL:
Whiteboard: logging-exploration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-06 19:07 UTC by Hui Kang
Modified: 2021-02-24 11:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 11:22:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 598 0 None open Bug 1913443: Rename prometheus filename for recording rules 2021-01-06 19:45:40 UTC
Red Hat Product Errata RHBA-2021:0652 0 None None None 2021-02-24 11:22:56 UTC

Description Hui Kang 2021-01-06 19:07:38 UTC 
Description of problem:

According to the prometheus website, the filename should be something like recording_rules to match its content and differentiate from the alert rule.

https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/

How reproducible:

NA
Steps to Reproduce:

1.
Comment 2 Qiaoling Tang 2021-01-07 07:12:40 UTC 
Tested with ose-elasticsearch-operator-v4.7.0-202101070128.p0, the file is renamed to `prometheus_recording_rules.yml`

sh-4.4$ ls /etc/elasticsearch-operator/files/
dashboards  prometheus_alerts.yml  prometheus_recording_rules.yml
Comment 5 errata-xmlrpc 2021-02-24 11:22:33 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 (Errata Advisory for Openshift Logging 5.0.0), 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-2021:0652
Note You need to log in before you can comment on or make changes to this bug.