Feature requests
list Michael Nemeth
Since there a new version come soon I thought I mention a couple thing I request in the past. 1. toggle between % and size on disk graphs. right now you can change the url to do this That is: http://scorpion/hobbit-cgi/hobbitgraph.sh?host=dwvob13k&service=disk&graph_width=576&graph_height=120&first=1&count=4&disp=dwvob13k&nostale&color=red&action=menu to : http://scorpion/hobbit-cgi/hobbitgraph.sh?host=dwvob13k&service=disk1&graph_width=576&graph_height=120&first=1&count=4&disp=dwvob13k&nostale&color=red&action=menu Nice to have a button to do this. 2. Alert/show on either/or specified change in file size and/or % change. That is: DISK /home01 size=+50% size=-10G DISK /home02 size=+-50% DISK / size=+-100M Or some thing like that. How many time have you seen an FS drop to near zero because someone did a rm -Rf * !! Henrik see http://www.i-pi.com/watcher.html 3. Remove hosts/tests via the enable/disable cgi (I think that a logical place) . True you still might have to edit the bb-hosts but lots of time I decide to no longer run tests (mostly not running client any more but still want to know if its pingable). -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | _p_ Mike Nemeth | ___| |_____ email(w) user-609d3fab5b2d@xymon.invalid Work: XXX XXX-XXXX |><___________) | Home Page:http://www.geocities.com/mjnemeth/ | Work Page:http://scorpion/~nemethm/ | Work Page:http://phlccase/SWUNIX/mnemeth/ |++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
list Joe Moore
If we're throwing out feature requests... My users would love to see something that can be descibed as a "service group" of statuses... Basically, we have several groups of web servers on the page that the apache admins look at, in group-only blocks (they don't care about system messages, only their HTTP, CONT, and TRENDS). In order for them to see everything, they have to scroll around because there are a bunch of 3-column, N-row groups. But the same data could be condensed into a single screen of a bunch of N-column, 3-row groups. So what I'd like to propose is a "servicegroup"# tag in bb-hosts, that renders its content as rows of tests, and columns of hosts (as opposed to the normal rows of hosts, columns of tests) Syntax: servicegroup SERVICE1|SERVICE2|SERVICE3 [group-title] Defines a group of host-service pairs that appear on the web page. Hosts in the servicegroup are listed as a single header-line with rows for each SERVICE listed. (Optional: allow "servicegroup * group-title" to show rows for all services on any of the hosts) Another benefit for this just came to mind: 'servicegroup TRENDS "System performance trends"'... Have a page or block at the bottom of your servers-page with easy access to all of the graphs for all those systems. --Joe # I'm not tied to this name... group-service might be more syntactically consistent with the rest of the bb-hosts entries.
list Richard Leyton
I'm normally somebody who resists joining a queue... But I've a feature request that might be worth opening up to the list for comment. wrt. the log file monitoring, it's working out great for one of my clients, but the only thing missing is really the possibility of pushing some log file messages into a different service name - right now all alerts are bundled into 'msgs', that way we could separate out application log checks from system log checks, from apache error_logs, and so on. My thought re. syntax would be to add a 'SERVICE=someapp' parameter to hobbit-clients.cfg, so that the log file regexp checks go into service 'someapp' rather than the default 'msgs' where defined, as I *think* the check against pattern matches in log messages is done server side? LOG /var/opt/someapp/blah.log %FAIL* COLOR=red SERVICE=someapp As ever, muchos gratis to Henrik for being patient with us all throwing our feature requests at you in one big go :-) r.
▸
On 25/07/07, Moore, Joe <user-ee98968d771d@xymon.invalid> wrote:If we're throwing out feature requests...
My users would love to see something that can be descibed as a "service
group" of statuses...
Basically, we have several groups of web servers on the page that the
apache admins look at, in group-only blocks (they don't care about
system messages, only their HTTP, CONT, and TRENDS). In order for them
to see everything, they have to scroll around because there are a bunch
of 3-column, N-row groups. But the same data could be condensed into a
single screen of a bunch of N-column, 3-row groups.
So what I'd like to propose is a "servicegroup"# tag in bb-hosts, that
renders its content as rows of tests, and columns of hosts (as opposed
to the normal rows of hosts, columns of tests)
Syntax:
servicegroup SERVICE1|SERVICE2|SERVICE3 [group-title]
Defines a group of host-service pairs that appear on the web
page. Hosts in the servicegroup are listed as a single header-line with
rows for each SERVICE listed.
(Optional: allow "servicegroup * group-title" to show rows for all
services on any of the hosts)
Another benefit for this just came to mind: 'servicegroup TRENDS "System
performance trends"'... Have a page or block at the bottom of your
servers-page with easy access to all of the graphs for all those
systems.
--Joe
# I'm not tied to this name... group-service might be more syntactically
consistent with the rest of the bb-hosts entries.
--
Richard Leyton http://www.leyton.org
list S Aiello
▸
On Wednesday 25 July 2007 10:09, Moore, Joe wrote:
If we're throwing out feature requests... My users would love to see something that can be descibed as a "service group" of statuses... Basically, we have several groups of web servers on the page that the apache admins look at, in group-only blocks (they don't care about system messages, only their HTTP, CONT, and TRENDS). In order for them to see everything, they have to scroll around because there are a bunch of 3-column, N-row groups. But the same data could be condensed into a single screen of a bunch of N-column, 3-row groups. So what I'd like to propose is a "servicegroup"# tag in bb-hosts, that renders its content as rows of tests, and columns of hosts (as opposed to the normal rows of hosts, columns of tests) Syntax: servicegroup SERVICE1|SERVICE2|SERVICE3 [group-title] Defines a group of host-service pairs that appear on the web page. Hosts in the servicegroup are listed as a single header-line with rows for each SERVICE listed. (Optional: allow "servicegroup * group-title" to show rows for all services on any of the hosts) Another benefit for this just came to mind: 'servicegroup TRENDS "System performance trends"'... Have a page or block at the bottom of your servers-page with easy access to all of the graphs for all those systems.
Don't the group-only and group-exceot bb-host parameters already cover this ?
I am assuming you are leaving the devices on their primary page, but want a
seperate page for apache admins. on their page you would just use an bb-host
alias: 0.0.0.0 devicename # noconn. Where the bb-host entry on the primary
page would have the correct IP and all BBTAGS + the prefer BBTAG.
<snippet from man bb-hosts>
group-only COLUMN1|COLUMN2|COLUMN3 [group-title]
Same as the "group" and "group-compress" lines, but includes only the
columns explicitly listed in the group. Any columns not listed will be
ignored for these hosts.
group-except COLUMN1|COLUMN2|COLUMN3 [group-title]
Same as the "group-only" lines, but includes all columns EXCEPT those
explicitly listed in the group. Any columns listed will be ignored for these
hosts - all other columns are shown.
</snippet>
~Steve
list Trent Melcher
▸
On Wed, 2007-07-25 at 10:28 -0400, user-ce96540ed38f@xymon.invalid wrote:
On Wednesday 25 July 2007 10:09, Moore, Joe wrote:If we're throwing out feature requests... My users would love to see something that can be descibed as a "service group" of statuses... Basically, we have several groups of web servers on the page that the apache admins look at, in group-only blocks (they don't care about system messages, only their HTTP, CONT, and TRENDS). In order for them to see everything, they have to scroll around because there are a bunch of 3-column, N-row groups. But the same data could be condensed into a single screen of a bunch of N-column, 3-row groups. So what I'd like to propose is a "servicegroup"# tag in bb-hosts, that renders its content as rows of tests, and columns of hosts (as opposed to the normal rows of hosts, columns of tests) Syntax: servicegroup SERVICE1|SERVICE2|SERVICE3 [group-title] Defines a group of host-service pairs that appear on the web page. Hosts in the servicegroup are listed as a single header-line with rows for each SERVICE listed. (Optional: allow "servicegroup * group-title" to show rows for all services on any of the hosts) Another benefit for this just came to mind: 'servicegroup TRENDS "System performance trends"'... Have a page or block at the bottom of your servers-page with easy access to all of the graphs for all those systems.Don't the group-only and group-exceot bb-host parameters already cover this ? I am assuming you are leaving the devices on their primary page, but want a seperate page for apache admins. on their page you would just use an bb-host alias: 0.0.0.0 devicename # noconn. Where the bb-host entry on the primary page would have the correct IP and all BBTAGS + the prefer BBTAG.
He is already using the group-only parameter, what he want to do is flip-flop the hosts and services, He wants rows of services and columns of hosts. Trent
▸
<snippet from man bb-hosts>
group-only COLUMN1|COLUMN2|COLUMN3 [group-title]
Same as the "group" and "group-compress" lines, but includes only the
columns explicitly listed in the group. Any columns not listed will be
ignored for these hosts.
group-except COLUMN1|COLUMN2|COLUMN3 [group-title]
Same as the "group-only" lines, but includes all columns EXCEPT those
explicitly listed in the group. Any columns listed will be ignored for these
hosts - all other columns are shown.
</snippet>
~Steve
list Charles Goyard
Ok, here's another one : be able to do something like : HOST=host.my.com PROC mysqld min=1 max=2000 color=red IF:host.my.com.is_master=green (and same for PORT) As you guessed it, it's a dependency check for active/standby clusters. It would be soooooooooooooooo nice :) I also have a hard bugfix : being tolerant about CMD alignment in ps output so that "^named" matches even when pushed by a 1-3 offset. Regards, -- Charles Goyard - user-a6cdca7046e2@xymon.invalid - (+33) 1 45 38 01 31 Orange Business Services - online multimedia // ingénierie
list David Winterstein
Hi, where do I submit feature requests? David -- Compositiv GmbH Hammer Deich 30 20537 Hamburg Tel: XXX / XXX XXXX X Fax: XXX / XXX XXXX XX Geschäftsführer Matthias Krawen Amtsgericht Hamburg - HRB 122540 USt.-IdNr: DE282432834 Es gelten ausschließlich unsere AGB.