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]...] N|timestamp:value[:value...] at-timestamp@value[:value...]
11 [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 argu‐
25 ments of the current and previous call to update, the list may
26 have no entries or a large number of entries.
27 filename
29 The name of the RRD you want to update.
30 --template|-t ds-name[:ds-name]...
32 By default, the update function expects its data input in the
33 order the data sources are defined in the RRD, excluding any
34 COMPUTE data sources (i.e. if the third data source DST is COM‐
35 PUTE, the third input value will be mapped to the fourth data
36 source in the RRD and so on). This is not very error resistant,
37 as you might be sending the wrong data into an RRD.
38 The template switch allows you to specify which data sources
40 you are going to update and in which order. If the data sources
41 specified in the template are not available in the RRD file,
42 the update process will abort with an error message.
43 While it appears possible with the template switch to update
45 data sources asynchronously, RRDtool implicitly assigns non-
46 COMPUTE data sources missing from the template the *UNKNOWN*
47 value.
48 Do not specify a value for a COMPUTE DST in the update func‐
50 tion. If this is done accidentally (and this can only be done
51 using the template switch), RRDtool will ignore the value spec‐
52 ified for the COMPUTE DST.
53 N|timestamp:value[:value...]
55 The data used for updating the RRD was acquired at a certain
56 time. This time can either be defined in seconds since
57 1970-01-01 or by using the letter 'N', in which case the update
58 time is set to be the current time. Negative time values are
59 subtracted from the current time. An AT_STYLE TIME SPECIFICA‐
60 TION (see the rrdfetch documentation) may also be used by
61 delimiting the end of the time specification with the '@' char‐
62 acter instead of a ':'. Getting the timing right to the second
63 is especially important when you are working with data-sources
64 of type COUNTER, DERIVE or ABSOLUTE.
65 The remaining elements of the argument are DS updates. The
67 order of this list is the same as the order the data sources
68 were defined in the RRA. If there is no data for a certain
69 data-source, the letter U (e.g., N:0.1:U:1) can be specified.
70 The format of the value acquired from the data source is depen‐
72 dent on the data source type chosen. Normally it will be
73 numeric, but the data acquisition modules may impose their very
74 own parsing of this parameter as long as the colon (:) remains
75 the data source value separator.
76
78 "rrdtool update demo1.rrd N:3.44:3.15:U:23"
79 Update the database file demo1.rrd with 3 known and one *UNKNOWN*
81 value. Use the current time as the update time.
82 "rrdtool update demo2.rrd 887457267:U 887457521:22 887457903:2.7"
84 Update the database file demo2.rrd which expects data from a single
86 data-source, three times. First with an *UNKNOWN* value then with two
87 regular readings. The update interval seems to be around 300 seconds.
88
90 Tobias Oetiker <tobi@oetiker.ch>
911.2.27 2008-02-17 RRDUPDATE(1)