Trends, trends and more trends. Feature request.
list Vernon Everett
Hi all
With the addition of diskstat/iostat info (along with zonestat, mpstat, a
few other custom graphs, and the standard Xymon graphs), the trends column
is really starting to look a little full. Cluttered might even be a better
word.
It would be nice to have a diskstat column for my server with all the
diskstat info on one page, but the way it works right now, we can't have
multiple graphs on a test page, particularly when these graphs are of
different scales. (counters, percentage, kb etc)
So, if that isn't possible, how difficult would it be to add a feature to
create a "user defined trends" page.
I know I can reshape my existing trends page, but cluttered as it is, I
actually want all the graphs, and don't want tot take any out.
What would be nice is if I could define a page, let's call it diskio, and
then define that to contain all the diskstat graphs, and then take them out
of trends.
Likewise, I could do the same with mpstat and zonestat.
This will give me at least 4 "trends" columns, and like the existing trends
page, it would contain nothing but graphs.
But each trend column would be less cluttered, and contain more specific
information, making it easier to find and comprehend.
How difficult would it be for the developer types to add this as a feature?
Not sure how the underlying code looks, but from what I see, in the config,
we have
TRENDSCOLUMN="trends"
GRAPHS="heaps,of,graphs,defined,here"
Everything in $GRAPHS ends up under the trends column.
How difficult would this be?
TRENDSCOLUMN="trends, diskstat, mpstat, zonestat, network" # default plus 4
new columns.
GRAPHS="heaps,of,graphs,defined,here" # Default stuff that
appears under first item in $TRENDSCOLUMN
GRAPHS_diskstat="diskstat-reads::7,etc.etc." # Stuff that will appear
under a column labeled "diskstat"
GRAPHS_mpstat="mpstat,graphs,defined,here" # Stuff that will appear
under a column labeled "mpstat"
GRAPHS_zonestat="zone,related,graphs,defined,here" # Stuff that will appear
under a column labeled "zonestat"
GRAPHS_network="network,traffic,and,tc,stuff" # Stuff that will appear
under a column labeled "network"
As I typed that, I noticed the word "graphs" appeared in multiple
definitions. Probably be a bonus feature :-)
Regards
Vernon
list Roland Soderstrom
Vernon, just my thoughts as well.
Haven't you discovered Stef Coens way of populating trends?
instead of doing:
$BB $BBDISP "data $MACHINE.diskstat `cat datafile`"
do
$BB $BBDISP "data $MACHINE.trends `cat datafile`"
Populate the datafile like this:
echo "[iostatrd.${Disk[${disk_no}]}.rrd]" >> $datafile
echo "DS:Kb_read:DERIVE:600:0:U $KREAD" >> $datafile
Your hobbitgraph.cfg entry would in this case be "iostatrd", your rrd file would be iostatrd..rrd
then you just put the tests in GRAPHS and add the stuff in hobbitgraph.cfg
No need to do the ncv stuff.
I think this is the way all builtin functions send data to the trends page.
There is a reference thread in the archive where Stef and Henrik discusses this and Henrik coded something for 4.2.0.
Now that is explained, to go to the thread question.
Maybe its easier to make it work with several trends pages like this:
$BB $BBDISP "data $MACHINE.trends,diskio `cat datafile`"
Where diskio would be the "new" trends page.
- Roland
ps.
Vernon, agree ksh is best for shell scripts, bash is best for your shell, csh should be forbidden...
I install ksh an all my Linux boxes, just to run scripts.
Haven't you discovered Stef Coens way of populating trends?
instead of doing:
$BB $BBDISP "data $MACHINE.diskstat `cat datafile`"
do
$BB $BBDISP "data $MACHINE.trends `cat datafile`"
Populate the datafile like this:
echo "[iostatrd.${Disk[${disk_no}]}.rrd]" >> $datafile
echo "DS:Kb_read:DERIVE:600:0:U $KREAD" >> $datafile
Your hobbitgraph.cfg entry would in this case be "iostatrd", your rrd file would be iostatrd..rrd
then you just put the tests in GRAPHS and add the stuff in hobbitgraph.cfg
No need to do the ncv stuff.
I think this is the way all builtin functions send data to the trends page.
There is a reference thread in the archive where Stef and Henrik discusses this and Henrik coded something for 4.2.0.
Now that is explained, to go to the thread question.
Maybe its easier to make it work with several trends pages like this:
$BB $BBDISP "data $MACHINE.trends,diskio `cat datafile`"
Where diskio would be the "new" trends page.
- Roland
ps.
Vernon, agree ksh is best for shell scripts, bash is best for your shell, csh should be forbidden...
I install ksh an all my Linux boxes, just to run scripts.
▸
On 10/09/10 12:19 PM, Vernon Everett wrote:Hi all
With the addition of diskstat/iostat info (along with zonestat, mpstat, a few other custom graphs, and the standard Xymon graphs), the trends column is really starting to look a little full. Cluttered might even be a better word.
It would be nice to have a diskstat column for my server with all the diskstat info on one page, but the way it works right now, we can't have multiple graphs on a test page, particularly when these graphs are of different scales. (counters, percentage, kb etc)
So, if that isn't possible, how difficult would it be to add a feature to create a "user defined trends" page.
I know I can reshape my existing trends page, but cluttered as it is, I actually want all the graphs, and don't want tot take any out.
What would be nice is if I could define a page, let's call it diskio, and then define that to contain all the diskstat graphs, and then take them out of trends.
Likewise, I could do the same with mpstat and zonestat.
This will give me at least 4 "trends" columns, and like the existing trends page, it would contain nothing but graphs.
But each trend column would be less cluttered, and contain more specific information, making it easier to find and comprehend.
How difficult would it be for the developer types to add this as a feature?
Not sure how the underlying code looks, but from what I see, in the config, we have
TRENDSCOLUMN="trends"
GRAPHS="heaps,of,graphs,defined,here"
Everything in $GRAPHS ends up under the trends column.
How difficult would this be?
TRENDSCOLUMN="trends, diskstat, mpstat, zonestat, network" # default plus 4 new columns.
GRAPHS="heaps,of,graphs,defined,here" # Default stuff that appears under first item in $TRENDSCOLUMN
GRAPHS_diskstat="diskstat-reads::7,etc.etc." # Stuff that will appear under a column labeled "diskstat"
GRAPHS_mpstat="mpstat,graphs,defined,here" # Stuff that will appear under a column labeled "mpstat"
GRAPHS_zonestat="zone,related,graphs,defined,here" # Stuff that will appear under a column labeled "zonestat"
GRAPHS_network="network,traffic,and,tc,stuff" # Stuff that will appear under a column labeled "network"
As I typed that, I noticed the word "graphs" appeared in multiple definitions. Probably be a bonus feature :-)
Regards
Vernon
list Stef Coene
▸
On Friday 10 September 2010, Vernon Everett wrote:
Hi all With the addition of diskstat/iostat info (along with zonestat, mpstat, a few other custom graphs, and the standard Xymon graphs), the trends column is really starting to look a little full. Cluttered might even be a better word. It would be nice to have a diskstat column for my server with all the diskstat info on one page, but the way it works right now, we can't have multiple graphs on a test page, particularly when these graphs are of different scales. (counters, percentage, kb etc)
You can if you this is a custom test. What I do, is put some <img> and <a> links at the bottom of my custom test pages with the graphs I want: <a href=\"/hobbit-cgi/hobbitgraph.sh?host=$SVC&service=svc- mdg&nostale&color=green&action=menu\"><img src=\"/hobbit- cgi/hobbitgraph.sh?host=$SVC&service=svc- mdg&nostale&color=green&action=view&graph=hourly\" /></a> (this is from a perl script so the " is escaped) And like Roland replied, forget about ncv and use a trends message for the rrd. This is much more simple. Also, if you want to include an extra trend for a particularly host, you can use the parameter GRAPHS in bb-hosts for that host. Stef