1RRDUPDATE(1) rrdtool RRDUPDATE(1)
2
6 rrdupdate - Store a new set of values into the RRD
7
9 rrdtool {update | updatev} filename [--template|-t ds-name[:ds-
10 name]...] [--daemon|-d address] [--] N|timestamp:value[:value...] at-
11 timestamp@value[:value...] [timestamp:value[:value...] ...]
12
14 The update function feeds new data values into an RRD. The data is time
15 aligned (interpolated) according to the properties of the RRD to which
16 the data is written.
17 updatev This alternate version of update takes the same arguments and
19 performs the same function. The v stands for verbose, which
20 describes the output returned. updatev returns a list of any
21 and all consolidated data points (CDPs) written to disk as a
22 result of the invocation of update. The values are indexed by
23 timestamp (time_t), RRA (consolidation function and PDPs per
24 CDP), and data source (name). Note that depending on the
25 arguments of the current and previous call to update, the list
26 may have no entries or a large number of entries.
27 Since updatev requires direct disk access, the --daemon option
29 cannot be used with this command.
30 filename
32 The name of the RRD you want to update.
33 --template|-t ds-name[:ds-name]...
35 By default, the update function expects its data input in the
36 order the data sources are defined in the RRD, excluding any
37 COMPUTE data sources (i.e. if the third data source DST is
38 COMPUTE, the third input value will be mapped to the fourth
39 data source in the RRD and so on). This is not very error
40 resistant, as you might be sending the wrong data into an RRD.
41 The template switch allows you to specify which data sources
43 you are going to update and in which order. If the data sources
44 specified in the template are not available in the RRD file,
45 the update process will abort with an error message.
46 While it appears possible with the template switch to update
48 data sources asynchronously, RRDtool implicitly assigns non-
49 COMPUTE data sources missing from the template the *UNKNOWN*
50 value.
51 Do not specify a value for a COMPUTE DST in the update
53 function. If this is done accidentally (and this can only be
54 done using the template switch), RRDtool will ignore the value
55 specified for the COMPUTE DST.
56 --daemon|-d address
58 If given, RRDTool will try to connect to the caching daemon
59 rrdcached at address and will fail if the connection cannot be
60 established. If the connection is successfully established the
61 values will be sent to the daemon instead of accessing the
62 files directly.
63 For a list of accepted formats, see the -l option in the
65 rrdcached manual.
66 N|timestamp:value[:value...]
68 The data used for updating the RRD was acquired at a certain
69 time. This time can either be defined in seconds since
70 1970-01-01 or by using the letter 'N', in which case the update
71 time is set to be the current time. Negative time values are
72 subtracted from the current time. An AT_STYLE TIME
73 SPECIFICATION (see the rrdfetch documentation) may also be used
74 by delimiting the end of the time specification with the '@'
75 character instead of a ':'. Getting the timing right to the
76 second is especially important when you are working with data-
77 sources of type COUNTER, DERIVE or ABSOLUTE.
78 When using negative time values, options and data have to be
80 separated by two dashes (--), else the time value would be
81 parsed as an option. See below for an example.
82 When using negative time values, options and data have to be
84 separated by two dashes (--), else the time value would be
85 parsed as an option. See below for an example.
86 The remaining elements of the argument are DS updates. The
88 order of this list is the same as the order the data sources
89 were defined in the RRA. If there is no data for a certain
90 data-source, the letter U (e.g., N:0.1:U:1) can be specified.
91 The format of the value acquired from the data source is
93 dependent on the data source type chosen. Normally it will be
94 numeric, but the data acquisition modules may impose their very
95 own parsing of this parameter as long as the colon (:) remains
96 the data source value separator.
97
99 The following environment variables may be used to change the behavior
100 of "rrdtool update":
101 RRDCACHED_ADDRESS
103 If this environment variable is set it will have the same effect as
104 specifying the "--daemon" option on the command line. If both are
105 present, the command line argument takes precedence.
106
108 · "rrdtool update demo1.rrd N:3.44:3.15:U:23"
109 Update the database file demo1.rrd with 3 known and one *UNKNOWN*
111 value. Use the current time as the update time.
112 · "rrdtool update demo2.rrd 887457267:U 887457521:22 887457903:2.7"
114 Update the database file demo2.rrd which expects data from a single
116 data-source, three times. First with an *UNKNOWN* value then with
117 two regular readings. The update interval seems to be around 300
118 seconds.
119 · "rrdtool update demo3.rrd -- -5:21 N:42"
121 Update the database file demo3.rrd two times, using five seconds in
123 the past and the current time as the update times.
124 · "rrdtool update --cache /var/lib/rrd/demo3.rrd N:42"
126 Update the file "/var/lib/rrd/demo3.rrd" with a single data source,
128 using the current time. If the caching daemon cannot be reached, do
129 not fall back to direct file access.
130 · "rrdtool update --daemon unix:/tmp/rrdd.sock demo4.rrd N:23"
132 Use the UNIX domain socket "/tmp/rrdd.sock" to contact the caching
134 daemon. If the caching daemon is not available, update the file
135 "demo4.rrd" directly. WARNING: Since a relative path is specified,
136 the following disturbing effect may occur: If the daemon is
137 available, the file relative to the working directory of the daemon
138 is used. If the daemon is not available, the file relative to the
139 current working directory of the invoking process is used. This
140 may update two different files depending on whether the daemon
141 could be reached or not. Don't do relative paths, kids!
142
144 Tobias Oetiker <tobi@oetiker.ch>, Florian Forster
145 <octo at verplant.org>
1461.4.8 2013-05-23 RRDUPDATE(1)