[hobbit] CLIENT vs. NAME
Gary Baluha
gumby3203 at gmail.com
Tue Apr 29 20:44:59 CEST 2008
In our Hobbit configuration, we have hosts using every possible combination
of CLIENT, NAME, neither, and both.
In short, here is how it works:
(In the bb-hosts file)
IP HOSTNAME # CLIENT=HOSTNAME_ALIAS NAME=DISPLAY_NAME
* Without CLIENT or NAME, the machine displays as HOSTNAME on the Hobbit
webpage, and in monitor alerts. All "bb" commands, alert rules, and monitor
rules (hobbit-clients.cfg) should refer to the machine as HOSTNAME
* With CLIENT, the machine displays as HOSTNAME on the Hobbit webpage and in
monitors alerts as above. All rules should also refer to the machine as
HOSTNAME. CLIENT is primarily to get rid of Ghost Client alerts. (In your
case, this is what you would use)
* NAME only affects what the machine shows up as on the Hobbit webpage.
Looking at my Hobbit notifications log file, the alerts sent out still use
HOSTNAME as the name.
* With both CLIENT and NAME, both rules apply.
For your final question, no, as long as HOSTNAME doesn't change (which is
what Hobbit uses for the name internally), the old saved data won't be
lost. If you want to change HOSTNAME, you should use the "rename" command
for the "bb" program (how to use this is listed in the man pages).
On Mon, Apr 28, 2008 at 7:08 PM, Eric Jacobs <
eric.jacobs at thomastechsolutions.com> wrote:
> Long time ago, servers were set up with "wrong" name. To correct hobbit
> display "NAME" variable was used in bb-hosts file for these servers. But I
> notice that email alerts are sent out with "wrong" name. If I used correct
> name in entry and used "CLIENT" variable to list name that would be seen
> by
> Hobbit server, would email alerts go out with correct name? And, if I make
> that change now, does that screw up any of the old saved data?
>
>
>
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe at hswn.dk
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20080429/f55ddbc2/attachment.html>
More information about the Xymon
mailing list