K Jonathan Harker 730b938ec3 Reduce graphite's stats retention policy ... In order to make more efficient use of disk space, let's change the default retention policy. Being able to react to changes with a 10-seccond precision less likely to be usefule as the data gets older, and our historic data does not give much insight beyond a 1-hour precision. This change does not effect already created metrics, changing that would require a manual run of whisper-resize.py on the data directories. This only effects new metrics. Old retention: 10-second precision for 6 hours 60-second precision for 7 days 10-minute precision for 5 years New retention 10-second precision for 8 hours 60-second precision for 7 days 1-hour precision for 1 year 1-day precision for 5 years Change-Id: I08d73d092fc73c271e9092f551f38f395e006ca4		2014-09-03 16:42:57 -07:00
..
admin.ini	Add graphite.	2012-12-02 20:28:38 +00:00
carbon.conf.erb	Work acound carbon issue #55.	2013-01-02 19:05:59 +00:00
config.js.erb	Add graphite.	2012-12-02 20:28:38 +00:00
graphite.vhost.erb	Correct graphite paths.	2012-12-18 21:44:04 +00:00
graphite.wsgi.erb	Add graphite.	2012-12-02 20:28:38 +00:00
local_settings.py.erb	Have graphite use the One True Timezone.	2014-03-10 17:24:07 -07:00
storage-aggregation.conf.erb	Set xfilesfactor to 0 for stats_counts.	2012-12-29 15:41:37 +00:00
storage-schemas.conf.erb	Reduce graphite's stats retention policy	2014-09-03 16:42:57 -07:00