Wolfgang Powisch (privat) wrote: >When using STACKs, the order of the AREA definitions is mandatory. >But the order of this definition forces the legend-items also to be in >this order. I would need some solution to change the order/position of >the legend-items ... is this possible. > >For better understanding, what I need in detail, in a fancy ascii-graph: > > >======================================================= >^ out_c >| out_b <-- stacked >| out_a >|-------------------------------- <--HRULE (zero-line) >| in_a >| in_b <-- stacked (negative values) >| in_c >|_____________________________________________> > # in_a # out_a > # in_b # out_b > # in_c # out_c >======================================================= > > >so the stack-order is: > in_a,in_b,in_c,out_a,out_b,out_c >but the legend order should be: > in_a,out_a,in_b,out_b,in_c,out_c
Simple, do all the legends as part of the out stack. I do graphs exactly like this at work and effectively do something like this : for var in a b c CDEF ... (calculate out value for $var) CDEF ... (calculate in value for $var) done for var in a b c area out_$var ... gprint in_$var out_$var done for var in a b c area in_$var ... done You could actually combine the first two loops, but I felt it made things more understandable to keep them separate. As it happens, there's been a similar thread over on teh Shorewall lists, you might find http://article.gmane.org/gmane.comp.security.shorewall/15218/match=packet+counting+auditing+per+ip gives you some ideas. _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
