Depending on the context, either the value component or the time component of a VDEF is printed using format. It is an error to specify a vname generated by a DEF or CDEF.
Any text in format is printed literally with one exception: The percent character introduces a formatter string. This string can be:
For printing values:
If you PRINT a VDEF value, you can also print the time associated with it by appending the string :strftime to the format. Note that rrdtool uses the strftime function of your OSs C library. This means that the conversion specifier may vary. Check the manual page if you are uncertain. The following is a list of conversion specifiers usually supported across the board.
Deprecated. Use the new form of this command in new scripts. The first form of this command is to be used with CDEF vnames.
This is the same as "PRINT", but printed inside the graph.
Deprecated. Use the new form of this command in new scripts. This is the same as "PRINT", but printed inside the graph.
Text is printed literally in the legend section of the graph. Note that in RRDtool 1.2 you have to escape colons in COMMENT text in the same way you have to escape them in *PRINT commands by writing '\:'.
Draw a vertical line at time. Its color is composed from three hexadecimal numbers specifying the rgb color components (00 is off, FF is maximum) red, green and blue followed by an optional alpha. Optionally, a legend box and string is printed in the legend section. time may be a number or a variable from a VDEF. It is an error to use vnames from DEF or CDEF here. Dashed lines can be drawn using the dashes modifier. See LINE for more details.
Draw a horizontal line at value. HRULE acts much like LINE except that will have no effect on the scale of the graph. If a HRULE is outside the graphing area it will just not be visible.
Draw a line of the specified width onto the graph. width can be a floating point number. If the color is not specified, the drawing is done 'invisibly'. This is useful when stacking something else on top of this line. Also optional is the legend box and string which will be printed in the legend section if specified. The value can be generated by DEF, VDEF, and CDEF. If the optional STACK modifier is used, this line is stacked on top of the previous element which can be a LINE or an AREA.
The dashes modifier enables dashed line style. Without any further options a symmetric dashed line with a segment length of 5 pixels will be drawn. The dash pattern can be changed if the dashes= parameter is followed by either one value or an even number (1, 2, 4, 6, ...) of positive values. Each value provides the length of alternate on_s and off_s portions of the stroke. The dash-offset parameter specifies an offset into the pattern at which the stroke begins.
When you do not specify a color, you cannot specify a legend. Should you want to use STACK, use the ``LINEx:<value>::STACK'' form.
See LINE, however the area between the x-axis and the line will be filled.
Plot a tick mark (a vertical line) for each value of vname that is non-zero and not *UNKNOWN*. The fraction argument specifies the length of the tick mark as a fraction of the y-axis; the default value is 0.1 (10% of the axis). Note that the color specification is not optional. The TICK marks normally start at the lower edge of the graphing area. If the fraction is negative they start at the upper border of the graphing area.
Using this command RRDtool will graph the following elements with the specified offset. For instance, you can specify an offset of ( 7*24*60*60 = ) 604'800 seconds to ``look back'' one week. Make sure to tell the viewer of your graph you did this ... As with the other graphing elements, you can specify a number or a variable here.
Labels are placed below the graph. When they overflow to the left, they wrap to the next line. By default, lines are justified left and right. The TEXTALIGN function lets you change this default. This is a command and not an option, so that you can change the default several times in your argument list.
Deprecated. Use the STACK modifiers on the other commands instead!
Some notes on stacking
When stacking, an element is not placed above the X-axis but rather on top of the previous element. There must be something to stack upon.
You can use an invisible LINE or AREA to stacked upon.
An unknown value makes the entire stack unknown from that moment on. You don't know where to begin (the unknown value) and therefore do not know where to end.
If you want to make sure you will be displaying a certain variable, make sure never to stack upon the unknown value. Use a CDEF instruction with IF and UN to do so.
Valid markers are: \j for justified, \l for left aligned, \r for right aligned, and \c for centered. In the next section there is an example showing how to use centered formatting.
\n is a valid alias for \l since incomplete parsing in earlier versions of rrdtool lead to this behavior and a number of people has been using it.
Normally there are two space characters inserted between every two items printed into the graph. The space following a string can be suppressed by putting a \g at the end of the string. The \g also ignores any space inside the string if it is at the very end of the string. This can be used in connection with %s to suppress empty unit strings.
A special case is COMMENT:\s which inserts some additional vertical space before placing the next row of legends.
If you are using the proportional font in your graph, you can use tab characters or the sequence \t to line-up legend elements. Note that the tabs inserted are relative to the start of the current legend element!
Since RRDtool 1.3 is using Pango for rending text, you can use Pango markup. Pango uses the xml span tags for inline formatting instructions.:
A simple example of a marked-up string might be:
<span foreground="blue" size="x-large">Blue text</span> is <i>cool</i>!
The complete list of attributes for the span tag (taken from the pango documentation):
To save you some typing, there are also some shortcuts:
Make sure to read rrdgraph_examples for tips&tricks.
This manual page by Alex van den Bogaerdt <firstname.lastname@example.org> with corrections and/or additions by several people