[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [hobbit] printer monitoring v. static bb-hosts

Oops... there should be a <cr> at the end of each detail line...

Rich Smrcina wrote:
If you're sending a status message to the Hobbit server, it might look something like this:

status cupshost1.cups yellow date time CUPS queues not OK<cr>
Queues on cupshost1<cr>
queue   run   acc   njob<cr>
------------------------<cr>
laser1  &green &green &green
laser2 ...

This status will then appear on cupshost1 as a yellow cups icon. The information on the first line after the time appears in larger bolder type on the cups page. The data after the first <cr> appears underneath, centered, in smaller type. You may have to play with the formatting, but that's how I send the data to Hobbit from the clients that I've written.

Obviously, design it how you like, but this format is pretty typical of clients and contributed tests. I like to try to design my test results to appeal to the larger audience, but still be functional for me.

Chapman Flack wrote:
Rich Smrcina wrote:
Since CUPS (as a print server) would run on one or multiple hosts, why not just one column, CUPS? Then when the icon is clicked, the various queue statuses for that host listed on the page. 

So if I understand what you're suggesting, it's something like:

     CUPS hosts:
  host      conn     cups
-------------------------
cupshost1    grn      yel
                       `-clik!-.
                     -> Queues on cupshost1
                    queue     run    acc   njob
                    ---------------------------
                    laser1    grn    grn   grn
                    laser2    grn    grn   grn
                    laser3    grn    grn   yel
                    laser4    grn    grn   grn

I guess my question is more about how to produce the 'queues on
cupshost1' page. A quick'n'dirty way would be to just have the
icon on the 'cups hosts' page link directly to the CUPS server's
own printers/ url. That would basically work and provide the
information, but not in a condensed Hobbit-like form. Another way
would be to create the page tag and group tag in bb-hosts in the
usual way and redundantly declare all the queue names in it, which
is what I was looking for a way to avoid. I suppose another way
would be for the ext script to generate the corresponding html
itself as the message it sends with bb for cupshost1 ... but even
if that can work it sounds like a brittle approach with a lot of
duplicated effort.

Or did you have another approach in mind that I've overlooked?

Thanks,
-Chap


To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk




--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service:  360-715-2467
rich.smrcina at vmassist.com

Catch the WAVV!  http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007