Set up a new Round Robin Database (RRD). Check the rrdcreate manpage.
Store new data values into an RRD. Check the rrdupdate manpage.
Operationally equivalent to update except for output. Check the rrdupdate manpage.
Create a graph from data stored in one or several RRDs. Apart from generating graphs, data can also be extracted to stdout. Check the rrdgraph manpage.
Dump the contents of an RRD in plain ASCII. In connection with restore you can use this to move an RRD from one computer architecture to another. Check the rrddump manpage.
Restore an RRD in XML format to a binary RRD. Check the rrdrestore manpage
Get data for a certain time period from a RRD. The graph function uses fetch to retrieve its data from an RRD. Check the rrdfetch manpage.
Alter setup of an RRD. Check the rrdtune manpage.
Find the last update time of an RRD. Check the rrdlast manpage.
Get information about an RRD. Check the rrdinfo manpage.
Change the size of individual RRAs. This is dangerous! Check the rrdresize manpage.
Export data retrieved from one or several RRDs. Check the rrdxport manpage
This is a standalone tool for producing RRD graphs on the fly. Check the rrdcgi manpage.
When monitoring the state of a system, it is convenient to have the @@ -177,8 +164,7 @@ interpolated value to the log. The original value you have supplied is stored as well and is also taken into account when interpolating the next log entry.
You may log data at a 1 minute interval, but you might also be @@ -195,16 +181,13 @@ consolidated values (see rrdcreate). You can define any number of different consolidation setups within one RRD. They will all be maintained on the fly when new data is loaded into the RRD.
Data values of the same consolidation setup are stored into Round Robin Archives (RRA). This is a very efficient manner to store data for a certain amount of time, while using a known and constant amount of storage space.
-It works like this: If you want to store 1'000 values in 5 minute interval, RRDtool will allocate space for 1'000 data values and a header area. In the header it will store a pointer telling which slots @@ -215,22 +198,17 @@ manner. This automatically limits the history to the last 1'000 values single RRD, you can setup another one, for storing 750 data values at a 2 hour interval, for example, and thus keep a log for the last two months at a lower resolution.
-The use of RRAs guarantees that the RRD does not grow over time and that old data is automatically eliminated. By using the consolidation feature, you can still keep data for a very long time, while gradually reducing the resolution of the data along the time axis.
-Using different consolidation functions (CF) allows you to store exactly the type of information that actually interests you: the maximum one minute traffic on the LAN, the minimum temperature of your wine cellar, the total minutes of down time, etc.
As mentioned earlier, the RRD stores data at a constant @@ -246,8 +224,7 @@ performed to make sure that the percentage of unknown values in the data point is above a configurable level. If not, an *UNKNOWN* value will be written to the RRA.
RRDtool allows you to generate reports in numerical and @@ -256,16 +233,12 @@ graphical form based on the data stored in one or several contents of the graph can be defined freely. Check the rrdgraph manpage for more information on this.
by Jake Brutlag
-RRDtool provides the building blocks for near real-time aberrant behavior detection. These components include:
-An algorithm for predicting the value of a time series one time step @@ -312,6 +285,7 @@ particular, a FAILURES RRA logs potential failures. With these you could, for example, use a front-end application to RRDtool to initiate real-time alerts.
For a detailed description on how to set this up, see the rrdcreate manpage.
+