X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=doc%2Frrdcached.pod;h=4d079a9ced6a866b6a368d0e9e9e6a77ed8e5c23;hb=3c3effad5f54f8c73260068e3ec32c56684243bb;hp=fd565239845be1bca72f1e6636022ff451f20ffa;hpb=273a1b83ea752d385159b02977e5157a9fe09aa1;p=rrdtool.git diff --git a/doc/rrdcached.pod b/doc/rrdcached.pod index fd56523..4d079a9 100644 --- a/doc/rrdcached.pod +++ b/doc/rrdcached.pod @@ -409,6 +409,10 @@ Adds more data to a filename. This is B operation the daemon was designed for, so describing the mechanism again is unnecessary. Read L above for a detailed explanation. +Note that rrdcached only accepts absolute timestamps in the update values. +Updates strings like "N:1:2:3" are automatically converted to absolute +time by the RRD client library before sending to rrdcached. + =item B I This command is written to the journal after a file is successfully @@ -434,8 +438,8 @@ message itself. The first user command after B is command number one. client: BATCH server: 0 Go ahead. End with dot '.' on its own line. - client: UPDATE x.rrd N:1:2:3 <--- command #1 - client: UPDATE y.rrd N:3:4:5 <--- command #2 + client: UPDATE x.rrd 1223661439:1:2:3 <--- command #1 + client: UPDATE y.rrd 1223661440:3:4:5 <--- command #2 client: and so on... client: . server: 2 Errors @@ -469,10 +473,11 @@ daemon was started. =item B I<(unsigned 64bit integer)> -Total number of "data sets" written to disk since the daemon was started. A -data set is one or more values passed to the B command. For example: -C is one data set with two values. The term "data set" is used to -prevent confusion whether individual values or groups of values are counted. +Total number of "data sets" written to disk since the daemon was +started. A data set is one or more values passed to the B +command. For example: C<1223661439:123:456> is one data set with two +values. The term "data set" is used to prevent confusion whether +individual values or groups of values are counted. =item B I<(unsigned 64bit integer)>