At the moment, all data is retained infinitely. This change allows users
to specify a default_retention_hours (defaults to 0 meaning unlimited
retention) in the influxdb section of monasca persister configuration so
that new projects are automatically assigned this retention policy when
the given hour is greater than 0 to preserve original behaviour.
At present, all time series are accumulated in the same database in
InfluxDB. Separate database per tenant would make queries faster for
tenants. It would also allow administrators to define retention policy
This changeset adds a migration tool and a guide to allow users to
migrate existing data to a database per tenant.
It was found in some installations that python-cachetools needed
to be present on the system. This can happen if the installation
was configured for the Java mon-persister but the recreate-metric-id
tool is written in Python. Added a bullet item to describe this
dependency and the quick workaround of installing the
It was discovered that the example paths included in the README.rst
used monasca-persister rather than monasca_persister.
Also added a footnote with two error messages that occur when the
contact_points is not specified correctly.
In some rare cases it is possible for a row in Cassandra for
metrics to have no value for metric_id or created_at, though
they may still have updated_at and the other required columns.
This tool is for recreating the metric_id from the other required
An additional 'persister-check-missing-metric-id.py' tool is
provided which can be run to see if there are missing metric-id
values that need to be recreated.
Please see the README.rst for usage directions.
(cherry picked from commit 09af9bff91)