summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 2269cac)
raw | patch | inline | side by side (parent: 2269cac)
author | oetiker <oetiker@a5681a0c-68f1-0310-ab6d-d61299d08faa> | |
Fri, 20 Jul 2007 22:16:36 +0000 (22:16 +0000) | ||
committer | oetiker <oetiker@a5681a0c-68f1-0310-ab6d-d61299d08faa> | |
Fri, 20 Jul 2007 22:16:36 +0000 (22:16 +0000) |
doc/rrdcreate.pod | patch | blob | history |
diff --git a/doc/rrdcreate.pod b/doc/rrdcreate.pod
index 3689e2937aa09a158bebe6c20de60c4ca5cbfc4e..49db70ec4ca86c33c424cefb90b3ab65b03fc1c6 100644 (file)
--- a/doc/rrdcreate.pod
+++ b/doc/rrdcreate.pod
The data is also processed with the consolidation function (I<CF>) of
the archive. There are several consolidation functions that
consolidate primary data points via an aggregate function: B<AVERAGE>,
-B<MIN>, B<MAX>, B<LAST>. The format of B<RRA> line for these
+B<MIN>, B<MAX>, B<LAST>.
+
+=over
+
+=item AVERAGE
+
+the average of the data points is stored.
+
+=item MIN
+
+the smallest of the data points is stored.
+
+=item MAX
+
+the largest of the data points is stored.
+
+=item LAST
+
+the last data points is used.
+
+=back
+
+Note that data aggregation inevitably leads to loss of precision and
+information. The trick is to pick the aggregate function such that the
+I<interesting> properties of your data is kept across the aggregation
+process.
+
+
+The format of B<RRA> line for these
consolidation functions is:
B<RRA:>I<AVERAGE | MIN | MAX | LAST>B<:>I<xff>B<:>I<steps>B<:>I<rows>