Actions
Feature #54308
closedmonitoring/prometheus: mgr/cephadm should support a data retention spec for prometheus data
Status:
Resolved
Priority:
Normal
Assignee:
Category:
cephadm/monitoring
Target version:
% Done:
0%
Source:
Tags:
backport_processed
Backport:
quincy, pacific
Description
When we deploy Prometheus server, we don't provide any ability to define the tsdb retention time - so it defaults to 15d.
This RFE would introduce a spec to the prometheus Service that would allow the storage.tsdb.retnetion.time to be defined, making it easier to adapt the data retention of the monitoring environment to meet user requirements.
with this setting defined the prometheus unit.run file would include the --storage.tsdb.retention.time parameter
Updated by Adam King over 1 year ago
- Status changed from New to In Progress
- Assignee set to Adam King
Updated by Adam King over 1 year ago
- Backport changed from quincy pacific to quincy, pacific
Updated by Adam King over 1 year ago
- Status changed from In Progress to Pending Backport
Updated by Backport Bot over 1 year ago
- Copied to Backport #57427: pacific: monitoring/prometheus: mgr/cephadm should support a data retention spec for prometheus data added
Updated by Backport Bot over 1 year ago
- Copied to Backport #57428: quincy: monitoring/prometheus: mgr/cephadm should support a data retention spec for prometheus data added
Updated by Adam King over 1 year ago
- Status changed from Pending Backport to Resolved
Actions