Back to bug 2112800
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Lijo Stephen Thomas | 2022-08-01 07:39:37 UTC | CC | lithomas | |
| Red Hat One Jira (issues.redhat.com) | 2022-08-01 07:40:23 UTC | Link ID | Red Hat Issue Tracker RHCEPH-4975 | |
| Michaela Lang | 2022-08-01 07:59:40 UTC | Comment | 0 | updated |
| Geo Jose | 2022-08-02 03:09:35 UTC | CC | gjose | |
| Matthias Muench | 2022-08-02 11:32:37 UTC | CC | mmuench | |
| Adam King | 2022-08-08 14:53:00 UTC | Target Release | 6.1 | 6.0 |
| Veera Raghava Reddy | 2022-08-17 05:00:21 UTC | CC | vereddy | |
| Scott Ostapovicz | 2022-09-14 13:23:19 UTC | CC | sostapov | |
| Target Release | 6.0 | 6.1 | ||
| Adam King | 2022-09-16 21:59:42 UTC | Status | NEW | POST |
| Target Release | 6.1 | 6.0 | ||
| errata-xmlrpc | 2022-09-17 02:59:10 UTC | Fixed In Version | ceph-17.2.3-35.el9cp | |
| Status | POST | MODIFIED | ||
| CC | tserlin | |||
| Status | MODIFIED | ON_QA | ||
| Masauso Lungu | 2022-09-19 13:26:02 UTC | CC | adking, mlungu | |
| Flags | needinfo?(adking) | |||
| Masauso Lungu | 2022-09-19 13:26:51 UTC | Docs Contact | asriram | mlungu |
| Masauso Lungu | 2022-09-21 17:31:43 UTC | Flags | needinfo?(adking) | |
| Adam King | 2022-09-21 19:49:24 UTC | Doc Text | Feature: Users can now set the prometheus tdsb retention size and time in the prometheus spec. The format for doing so is service_type: prometheus placement: count: 1 spec: retention_time: "1y" retention_size: "1GB" Reason: to allow users to customize these settings through cephadm so they are persistently applied. This should make it easier for users to specify how much and for how long they would like their prometheus instance to retain data. Result: Users can now specify tdsb retention time and size easily through the spec. | |
| Flags | needinfo?(adking) needinfo?(adking) | |||
| Doc Type | If docs needed, set a value | Enhancement | ||
| Masauso Lungu | 2022-09-27 11:31:23 UTC | Flags | needinfo?(adking) | |
| Doc Text | Feature: Users can now set the prometheus tdsb retention size and time in the prometheus spec. The format for doing so is service_type: prometheus placement: count: 1 spec: retention_time: "1y" retention_size: "1GB" Reason: to allow users to customize these settings through cephadm so they are persistently applied. This should make it easier for users to specify how much and for how long they would like their prometheus instance to retain data. Result: Users can now specify tdsb retention time and size easily through the spec. | .Users can now easily set the Prometheus TSDB retention size and time in the Prometheus specification Previously, users could not modify the default 15d retention period and disk consumption from Prometheus. With this release, users can customize these settings through `cephadm` so that they are persistently applied, thereby making it easier for users to specify how much and for how long they would like their Prometheus instances to return data. The format for achieving this is as follows: .Example ---- service_type: prometheus placement: count: 1 spec: retention_time: "1y" retention_size: "1GB" ---- |
||
| Masauso Lungu | 2022-09-27 18:36:14 UTC | Blocks | 2126050 | |
| Adam King | 2022-09-27 20:25:39 UTC | Flags | needinfo?(adking) | |
| Vivek Das | 2022-11-03 05:32:40 UTC | CC | vdas | |
| QA Contact | mgowri | vdas | ||
| Pranav Prakash | 2022-12-15 07:53:01 UTC | CC | prprakas | |
| Milind | 2022-12-22 09:27:12 UTC | Flags | needinfo?(adking) | |
| CC | milverma | |||
| Adam King | 2022-12-22 16:32:08 UTC | Flags | needinfo?(adking) | |
| Red Hat Bugzilla | 2022-12-31 19:26:03 UTC | CC | prprakas | |
| Red Hat Bugzilla | 2023-01-01 05:37:23 UTC | CC | adking | |
| Assignee | adking | nobody | ||
| Red Hat Bugzilla | 2023-01-01 05:39:48 UTC | CC | tserlin | |
| Red Hat Bugzilla | 2023-01-01 08:43:07 UTC | CC | sostapov | |
| Red Hat Bugzilla | 2023-01-01 08:46:17 UTC | QA Contact | vdas | |
| CC | vdas | |||
| Red Hat Bugzilla | 2023-01-01 08:47:39 UTC | CC | vereddy | |
| Vivek Das | 2023-01-02 13:36:22 UTC | CC | vdas | |
| QA Contact | vdas | |||
| Alasdair Kergon | 2023-01-04 04:33:20 UTC | Assignee | nobody | adking |
| Alasdair Kergon | 2023-01-04 04:38:28 UTC | CC | adking | |
| Alasdair Kergon | 2023-01-04 05:33:04 UTC | CC | prprakas | |
| Alasdair Kergon | 2023-01-04 05:43:50 UTC | CC | sostapov | |
| Alasdair Kergon | 2023-01-04 06:59:12 UTC | CC | vereddy | |
| Sayalee | 2023-01-09 04:52:56 UTC | QA Contact | vdas | saraut |
| CC | saraut | |||
| Michaela Lang | 2023-01-09 06:58:57 UTC | Flags | needinfo?(adking) | |
| Adam King | 2023-01-09 14:17:30 UTC | Flags | needinfo?(adking) | |
| Sayalee | 2023-01-18 09:58:46 UTC | Status | ON_QA | VERIFIED |
| Lijo Stephen Thomas | 2023-03-14 02:13:49 UTC | Link ID | Red Hat Knowledge Base (Solution) 6969242 | |
| errata-xmlrpc | 2023-03-20 18:38:11 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-03-20 18:57:13 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-03-20 18:57:13 UTC | |||
| errata-xmlrpc | 2023-03-20 18:57:56 UTC | Link ID | Red Hat Product Errata RHBA-2023:1360 | |
| Raimund Sacherer | 2023-05-02 12:43:47 UTC | Blocks | 2192594 |
Back to bug 2112800