Project

General

Profile

action #66019

Configure downsampling and a retention policy for InfluxDB

Added by mkittler over 1 year ago. Updated about 1 year ago.

Status:
Workable
Priority:
Low
Assignee:
-
Target version:
Start date:
2020-04-23
Due date:
% Done:

0%

Estimated time:

Description

Motivation

When working on #64574 I've noticed that we don't have a retention policy and the default policy seems to be storing the data forever. That's likely something we want to adjust in the long term.

Acceptance criteria

  • AC1: Downsampling and retention is enabled with at least some sensible settings on the influxdb on monitor.qa.suse.de

Suggestion

History

#1 Updated by okurz over 1 year ago

  • Priority changed from Normal to Low

#2 Updated by okurz about 1 year ago

  • Target version set to Ready

#3 Updated by okurz about 1 year ago

  • Tags set to monitor, influxdb, infrastructure, administration, osd
  • Subject changed from Configure a retention policy for InfluxDB to Configure downsampling and a retention policy for InfluxDB
  • Description updated (diff)
  • Status changed from New to Workable

#4 Updated by okurz about 1 year ago

found https://towardsdatascience.com/influxdb-data-retention-f026496d708f which is describing a bit of an overview. I have not really understood if we need to define something in a config file or set in the database itself, if we need to run some additional process on a regular base or if that is handled within influxdb as well.

#5 Updated by okurz about 1 year ago

  • Target version changed from Ready to future
$ ssh monitor.qa df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda2        77G   27G   50G  35% /
/dev/vdb1       300G   87G  212G  30% /var/lib/influxdb

I think we have enough headroom for now. Removing from backlog again due to backlog capacity constraints.

Also available in: Atom PDF