X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=doc%2Frrdgraph_graph.html;h=efee2d85dd78836efe49755723b25bda5fe4f60e;hb=HEAD;hp=b0d7bef1f752772de00536c07ae7d1b605efc7c5;hpb=51c3d3fb997c22e1ee828470413f1e84989e1f6c;p=pkg-rrdtool.git diff --git a/doc/rrdgraph_graph.html b/doc/rrdgraph_graph.html index b0d7bef..efee2d8 100644 --- a/doc/rrdgraph_graph.html +++ b/doc/rrdgraph_graph.html @@ -37,8 +37,8 @@
  • COMMENT:text
  • VRULE:time#color[:legend][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]
  • HRULE:value#color[:legend][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]
  • -
  • LINE[width]:value[#color][:[legend][:STACK]][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]
  • -
  • AREA:value[#color][:[legend][:STACK]]
  • +
  • LINE[width]:value[#color][:[legend][:STACK][:skipscale]][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]
  • +
  • AREA:value[#color][:[legend][:STACK][:skipscale]]
  • TICK:vname#rrggbb[aa][:fraction[:legend]]
  • SHIFT:vname:offset
  • TEXTALIGN:{left|right|justified|center}
  • @@ -78,8 +78,8 @@

    COMMENT:text

    VRULE:time#color[:legend][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]

    HRULE:value#color[:legend][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]

    -

    LINE[width]:value[#color][:[legend][:STACK]][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]

    -

    AREA:value[#color][:[legend][:STACK]]

    +

    LINE[width]:value[#color][:[legend][:STACK][:skipscale][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]

    +

    AREA:value[#color][:[legend][:STACK][:skipscale]]

    TICK:vname#rrggbb[aa][:fraction[:legend]]

    SHIFT:vname:offset

    TEXTALIGN:{left|right|justified|center}

    @@ -142,7 +142,7 @@ will all use the same magnitude unit except for zero 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 +: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.

    @@ -217,7 +217,7 @@ such cases %p will return an empty string.

    %S
    -

    The seconds since the epoch (1.1.1970) (libc dependant non standard!)

    +

    The seconds since the epoch (1.1.1970) (libc dependent non standard!)

    %U
    @@ -315,7 +315,7 @@ will have no effect on the scale of the graph. If a HRULE is outside the graphing area it will just not be visible.

    -

    LINE[width]:value[#color][:[legend][:STACK]][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]

    +

    LINE[width]:value[#color][:[legend][:STACK][:skipscale]][:dashes[=on_s[,off_s[,on_s,off_s]...]][:dash-offset=offset]]

    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 @@ -324,6 +324,10 @@ the legend section if specified. The value can be generated by 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.

    +

    Normally the graphing function makes sure that the entire LINE or AREA +is visible in the chart. The scaling of the chart will be modified +accordingly if necessary. Any LINE or AREA can be excluded from this +process by adding the option skipscale.

    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 @@ -332,10 +336,10 @@ provides the length of alternate on_s and off_s portions of th 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.

    +you want to use STACK, use the "LINEx:<value>::STACK" form.

    -

    AREA:value[#color][:[legend][:STACK]]

    +

    AREA:value[#color][:[legend][:STACK][:skipscale]]

    See LINE, however the area between the x-axis and the line will be filled.

    @@ -402,7 +406,7 @@ specified.

    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.

    +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 @@ -412,8 +416,18 @@ in connection with %s to suppress empty unit strings.

    GPRINT:a:MAX:%lf%s\g

    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 +

    If you want to have left and right aligned legends on the same line use COMMENT:\u +to go one line back like this:

    +
    + COMMENT:left\l
    + COMMENT:\u
    + COMMENT:right\r
    +

    There is also a 'nop' control for situations where you want a string to +actually end in a backslash character sequence \.

    +
    + COMMENT:OS\2\.
    +

    When using a proportional font in your graph, the tab +characters or the sequence \t will 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. @@ -496,7 +510,7 @@ Pango uses the xml span tags for inline formatting instructions

    strikethrough_color
    -

    The color of strikethrough lines; an RGB color specification such as '#00FF00' or a color name such as 'red'

    +

    The color of crossed out lines; an RGB color specification such as '#00FF00' or a color name such as 'red'

    fallback
    @@ -544,7 +558,7 @@ Pango uses the xml span tags for inline formatting instructions
    s
    -

    Strikethrough

    +

    Strike through

    sub