table of contents
- NAME
- SYNOPSIS
- DESCRIPTION
- FILE FORMAT
- TAGS RECOGNIZED BY ALL TOOLS
- GENERAL PER-HOST OPTIONS
- BBGEN DISPLAY OPTIONS
- XYMON TAGS FOR THE CRITICAL SYSTEMS OVERVIEW PAGE
- XYMON TAGS FOR THE WML (WAP) CARDS
- XYMON STATUS PROPAGATION OPTIONS
- XYMON AVAILABILITY REPORT OPTIONS
- NETWORK TEST SETTINGS
- CONNECTIVITY (PING) TEST
- SIMPLE NETWORK TESTS
- DNS SERVER TESTS
- OTHER NETWORK TESTS
- HTTP TESTS
- LDAP (DIRECTORY SERVER) TESTS
- PERFORMANCE MONITORING TESTS
- DEFAULT HOST
- SENDING SUMMARIES TO REMOTE XYMON SERVERS
- OTHER TAGS
- FILES
- SEE ALSO
other versions
- wheezy 4.3.0~beta2.dfsg-9.1
BB-HOSTS(5) | File Formats Manual | BB-HOSTS(5) |
NAME¶
bb-hosts - Main Xymon configuration fileSYNOPSIS¶
- bb-hosts
-
DESCRIPTION¶
The bb-hosts(5) file is the most important configuration file for all of the Xymon programs. This file contains the full list of all the systems monitored by Xymon, including the set of tests and other configuration items stored for each host.FILE FORMAT¶
Each line of the file defines a host. Blank lines and lines starting with a hash mark (#) are treated as comments and ignored. Long lines can be broken up by putting a backslash at the end of the line and continuing the entry on the next line.IP-address hostname # tag1 tag2 ...
TAGS RECOGNIZED BY ALL TOOLS¶
- include filename
- This tag is used to include another file into the bb-hosts
file at run-time, allowing for a large bb-hosts file to be split up into
more manageable pieces.
- dispinclude filename
- Acts like the "include" tag, but only on the
BBDISPLAY server. Can be used e.g. to put a group of hosts on multiple
subpages, without having to repeat the host definitions.
- netinclude filename
- Acts like the "include" tag, but only on the
BBNET server.
GENERAL PER-HOST OPTIONS¶
- noclear
- Controls whether stale status messages go purple or clear
when a host is down. Normally, when a host is down the client statuses
("cpu", "disk", "memory" etc) will stop
updating - this would usually make them go "purple" which can
trigger alerts. To avoid that, Xymon checks if the "conn" test
has failed, and if that is true then the other tests will go
"clear" instead of purple so you only get alerts for the
"conn" test. If you do want the stale statuses to go purple, you
can use the "noclear" tag to override this behaviour.
- prefer
- When a single host is defined multiple time in the bb-hosts
file, bbgen tries to guess which definition is the best to use for the
information used on the "info" column, or for the NOPROPRED and
other bbgen-specific settings. Host definitions that have a
"noconn" tag or an IP of 0.0.0.0 get lower priority.
BBGEN DISPLAY OPTIONS¶
These tags are processed by the bbgen(1) tool when generating the Xymon webpages or reports.- page NAME [Page-title]
- This defines a page at the level below the entry page. All
hosts following the "page" directive appear on this page, until
a new "page", "subpage" or "subparent" line
is found.
- subpage NAME [Page-title]
- This defines a subpage in the second level below the entry
page. You must have a previous "page" line to hook this subpage
to.
- subparent parentpage newpage [Page-title]
- This is used to define subpages in whatever levels you may
wish. Just like the standard "subpage" tag,
"subparent" defines a new Xymon webpage; however with
"subparent" you explicitly list which page it should go as a
subpage to. You can pick any page as the parent - pages, subpages or even
other subparent pages. So this allows you to define any tree structure of
pages that you like.
page USA United States
subpage NY New York
subparent NY manhattan Manhattan data centers
subparent manhattan wallstreet Wall Street center
USA (United States)
NY (New York)
manhattan (Manhattan data centers)
wallstreet (Wall Street center)
- group [group-title]
- group-compress [group-title]
- Defines a group of hosts, that appear together on the
webpage, with a single header-line listing all of the columns. Hosts
following the "group" line appear inside the group, until a new
"group" or page-line is found. The two group-directives are
handled identically by Xymon and bbgen, but both forms are allowed for
backwards compatibility.
- group-sorted [group-title]
- Same as the "group" line, but will sort the hosts
inside the group so they appear in strict lexicographic order.
- 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.
- title Page, group or host title text
- The "title" tag is used to put custom headings
into the pages generated by bbgen, in front of page/subpage links, groups
or hosts.
- NAME:hostname
- Overrides the default hostname used on the overview web
pages. If "hostname" contains spaces, it must be enclosed in
double quotes, e.g. NAME:"R&D Oracle Server"
- CLIENT:hostname
- Defines an alias for a host, which will be used when
identifying status messages. This is typically used to accomodate a local
client that sends in status reports with a different hostname, e.g. if you
use hostnames with domains in your Xymon configuration, but the client is
a silly Window box that does not include the hostname. Or vice versa.
Whatever the reason, this can be used to match status reports with the
hosts you define in your bb-hosts file. It causes incoming status reports
with the specified hostname to be filed using the hostname defined in
bb-hosts.
- NOCOLUMNS:column[,column]
- Used to drop certain of the status columns generated by the
Xymon client. column is one of cpu, disk,
files, memory, msgs, ports, procs. This
setting stops these columns from being updated for the host. Note: If the
columns already exist, you must use the bb(1) utility to
drop them, or they will go purple.
- COMMENT:Host comment
- Adds a small text after the hostname on the webpage. This
can be used to describe the host, without completely changing its
display-name as the NAME: tag does. If the comment includes whitespace, it
must be in double-quotes, e.g. COMMENT:"Sun webserver"
- DESCR:Hosttype:Description
- Define some informational text about the host. The
"Hosttype" is a text describing the type of this device -
"router", "switch", "hub",
"server" etc. The "Description" is an informational
text that will be shown on the "Info" column page; this can e.g.
be used to store information about the physical location of the device,
contact persons etc. If the text contain whitespace, you must enclose it
in double-quotes, e.g. DESCR:"switch:4th floor Marketing switch"
- CLASS:Classname
- Force the host to belong to a specific class. Class-names
are used when configuring log-file monitoring (they can be used as
references in client-local.cfg(5) and hobbit-clients.cfg(5)
to group logfile checks). Normally, class-names are controlled on the
client by starting the Xymon client with the "--class=Classname"
option. If you specify it in the bb-hosts file on the Xymon server, it
overrides any classname that the client reports.
- dialup
- The keyword "dialup" for a host means that it is
OK for it to be off-line - this should not trigger an alert. All network
tests will go "clear" upon failure, and any missing reports from
e.g. cpu- and disk-status will not go purple when they are not updated.
- nobb2
- Ignore this host on the BB2 page. Even if it has an active
alert, it will not be included in the BB2 page. This also removes the host
from the event-log display.
- nodisp
- Ignore this host completely when generating the Xymon
webpages. Can be useful for monitoring a host without having it show up on
the webpages, e.g. because it is not yet in production use. Or for hiding
a host that is shown only on a second pageset.
- TRENDS:[*,][![graph,...]]
- Defines the RRD graphs to include in the "trends"
column generated by bbgen. This option syntax is complex.
- COMPACT:COLUMN=COLUMN1,COLUMN2,COLUMN3[;ditto]
- Collapses a series of statuses into a single column on the
overview webpage.
XYMON TAGS FOR THE CRITICAL SYSTEMS OVERVIEW PAGE¶
NOTE: The "NK" set of tags is deprecated. They will be supported for Xymon 4.x, but will be dropped in version 5. It is recommended that you move your critical systems view to the hobbit-nkview.cgi(1) viewer, which has a separate configuration tool, hobbit-nkedit.cgi(1) with more facilities than the NK tags in bb-hosts.- NK:testname[,testname]
- Define the tests that you want included on the bbnk page.
E.g. if you have a host where you only want to see the http tests on
bbnk.html, you specify it as
12.34.56.78 www.acme.com # http://www.acme.com/ NK:http
- NKTIME=day:starttime:endtime[,day:starttime:endtime]
- This tag limits the time when an active alert is presented
on the NK webpage.
XYMON TAGS FOR THE WML (WAP) CARDS¶
If bbgen is run with the "--wml" option, it will generate a set of WAP-format output "cards" that can be viewed with a WAP-capable device, e.g. a PDA or cell-phone.- WML:[+|-]testname[,[+|-]testname]
- This tag determines which tests for this hosts are included
in the WML (WAP) page. Syntax is identical to the NK: tag.
XYMON STATUS PROPAGATION OPTIONS¶
These tags affect how a status propagates upwards from a single test to the page and higher. This can also be done with the command-line options --nopropyellow and --nopropred, but the tags apply to individual hosts, whereas the command line options are global.- NOPROPRED:[+|-]testname[,[+|-]testname]
- This tag is used to inhibit a yellow or red status from
propagating upwards - i.e. from a test status color to the (sub)page
status color, and further on to bb.html or bb2.html
- NOPROPYELLOW:[+|-]testname[,[+|-]testname]
- Similar to NOPROPRED: tag, but applies to propagating a
yellow status upwards.
- NOPROPPURPLE:[+|-]testname[,[+|-]testname]
- Similar to NOPROPRED: tag, but applies to propagating a
purple status upwards.
- NOPROPACK:[+|-]testname[,[+|-]testname]
- Similar to NOPROPRED: tag, but applies to propagating an
acknowledged status upwards.
XYMON AVAILABILITY REPORT OPTIONS¶
These options affect the way the Xymon availability reports are processed (see bb-rep.cgi(1) for details about availability reports).- REPORTTIME=day:starttime:endtime[,day:starttime:endtime]
- This tag defines the time interval where you measure uptime
of a service for reporting purposes.
REPORTTIME=W:0700:2000
- WARNPCT:percentage
- BB's reporting facility uses a computed availability
threshold to color services green (100% available), yellow (above
threshold, but less than 100%), or red (below threshold) in the reports.
NETWORK TEST SETTINGS¶
- testip
- By default, Hobbit will perform a name lookup of the
hostname to get the IP address it will use for network tests. This tag
causes Hobbit to use the IP listed in the bb-hosts file.
- NET:location
- This tag defines the host as being tested from a specific
location. If bbtest-net sees that the environment variable BBLOCATION is
set, it will only test the hosts that have a matching
"NET:location" tag in the bb-hosts file. So this tag is useful
if you have more than one BBNET system, but you still want to keep a
consolidated bb-hosts file for all your systems.
- noclear
- Some network tests depend on others. E.g. if the host does
not respond to ping, then there's a good chance that the entire host is
down and all network tests will fail. Or if the http server is down, then
any web content checks are also likely to fail. To avoid floods of alerts,
the default behaviour is for bbtest-net to change the status of these
tests that fail because of another problem to "clear" instead of
"red". The "noclear" tag disables this behaviour and
causes all failing tests to be reported with their true color.
- nosslcert
- Disables the standard check of any SSL certificates for
this host. By default, if an SSL-enabled service is tested, a second test
result is generated with information about the SSL certificate - this tag
disables the SSL certificate checks for the host.
- ssldays=WARNDAYS:ALARMDAYS
- Define the number of days before an SSL certificate
expires, in which the sslcert status shows a warning (yellow) or alarm
(red) status. These default to the values from the
"--sslwarndays" and "--sslalarmdays" options for the
bbtest-net(1) tool; the values specified in the "ssldays"
tag overrides the default.
- sslbits=MINIMUMKEYBITS
- Enable checking of the encryption strengt of the SSL
protocol offered by the server. If the server offers encryption using a
key with fewer than MINIMUMKEYBITS bits, the "sslcert" test will
go red. E.g. to check that your server only uses strong encryption (128
bits or better), use "sslbits=128".
- DOWNTIME=[columns:]day:starttime:endtime:cause[,day:starttime:endtime:cause]
- This tag can be used to ignore failed checks during
specific times of the day - e.g. if you run services that are only
monitored e.g. Mon-Fri 8am-5pm, or you always reboot a server every Monday
between 5 and 6 pm.
- SLA=day:starttime:endtime[,day:starttime:endtime]
- This tag is now deprecated. Use the DOWNTIME tag instead.
- depends=(testA:host1/test1,host2/test2),(testB:host3/test3),[...]
- This tag allows you to define dependencies betweeen tests.
If "testA" for the current host depends on "test1" for
host "host1" and test "test2" for "host2",
this can be defined with
depends=(testA:host1/test1,host2/test2)
1.2.3.4 foo # http://foo/ webmin depends=(webmin:foo/http)
- badTEST[-weekdays-starttime-endtime]:x:y:z
- Normally when a network test fails, the status changes to
red immediately. With a "badTEST:x:y:z" tag this behaviour
changes:
12.34.56.78 www.foo.com # http://www.foo.com/ badhttp:1:2:4
CONNECTIVITY (PING) TEST¶
These tags affect the behaviour of the bbtest-net connectivity test.- noping
- Disables the ping-test, but will keep the "conn"
column on the web display with a notice that it has been disabled.
- noconn
- Disables the ping-test, and does not put a "conn"
column on the web display.
- conn
- The "conn" test (which does a ping of the host)
is enabled for all hosts by default, and normally you just want to disable
it using "noconn" or "noping". However, on the rare
occasion where you may want to check that a host is NOT up, you can
specify it as an explicit test, and use the normal test modifiers, e.g.
"!conn" will be green when the host is NOT up, and red if it
does appear on the network.
- conn={best,|worst,}IP1[,IP2...]
- This adds additional IP-adresses that are pinged during the
normal "conn" test. So the normal "conn" test must be
enabled (the default) before this tag has any effect. The IP-adresses
listed here are pinged in addition to the main IP-address.
- badconn[-weekdays-starttime-endtime]:x:y:z
- This is taken directly from the "fping.sh"
connectivity- testing script, and is used by bbtest-net when it runs with
ping testing enabled (the default). See the description of the
"badTEST" tag.
- route:router1,router2,....
- This tag is taken from the "fping.sh" script, and
is used by bbtest-net when run with the "--ping" option to
enable ping testing.
- route_LOCATION:router1,router2,...
- If the BBLOCATION environment variable is defined, a tag of
"route_BBLOCATION:" is recognized by bbtest-net with the same
effect as the normal "route:" tag (see above). This allows you
to have different route: tags for each BBNET server. The actual text for
the tag then must match the value you have for the BBLOCATION setting.
E.g. with BBLOCATION=dmz, the tag becomes "route_dmz:"
- trace
- If the connectivity test fails, run a
"traceroute" and include the output from this in the status
message from the failed connectivity test. Note: For this to work, you may
have to define the TRACEROUTE environment variable, see
hobbitserver.cfg(5)
- notrace
- Similar to the "trace" option, this disables the
running of a traceroute for the host after a failed connectivity test. It
is only used if running traceroute is made the default via the --trace
option.
SIMPLE NETWORK TESTS¶
These tests perform a simple network test of a service by connecting to the port and possibly checking that a banner is shown by the server.- ftp ssh telnet smtp pop3 imap nntp rsync clamd oratns qmtp qmqp
- These tags are for testing services offering the FTP,
Secure Shell (ssh), SMTP, POP3, IMAP, NNTP, rsync, CLAM antivirus daemon
(clamd), Oracle TNS listener (oratns), qmail QMTP and QMQP protocols.
- ftps telnets smtps pop3s imaps nntps
- These tags are for testing of the SSL-tunneled versions of
the standard ftp, telnet, smtp, pop3, imap and nntp protocols. If Xymon
was configured with support for SSL, you can test these services like any
other network service - bbtest-net will setup an SSL-encrypted session
while testing the service. The server certificate is validated and
information about it sent in the "sslcert" column. Note that
smtps does not have a standard portnumber assignment, so you will need to
enter this into the bb-services file or your /etc/services file.
- bbd
- Test that a Big Brother compatible daemon is running. This
check works both for the Xymon hobbitd(8) daemon, and the original
Big Brother bbd daemon.
DNS SERVER TESTS¶
These tags are used to setup monitoring of DNS servers.- dns
- Simple DNS test. It will attempt to lookup the A record for
the hostname of the DNS server.
- dig
- This is an alias for the "dns" test. In
bbtest-net, the "dns" and "dig" tests are handled
identically, so all of the facilities for testing described for the
"dns" test are also available for the "dig" test.
- dns=hostname
- dns=TYPE:lookup[,TYPE:lookup...]
- The default DNS tests will attempt a DNS lookup of the DNS'
servers own hostname. You can specify the hostname to lookup on a DNS
server by listing it on each test.
OTHER NETWORK TESTS¶
- ntp
- Check for a running NTP (Network Time Protocol) server on
this host. This test uses the "ntpdate" utility to check for a
NTP server - you should either have ntpdate in your PATH, or set the
location of the ntpdate program in $BBHOME/etc/bbsys.local
- rpc[=rpcservice1,rpcservice2,...]
- Check for one or more available RPC services. This check is
indirect in that it only queries the RPC Portmapper on the host, not the
actual service.
HTTP TESTS¶
Simple testing of a http URL is done simply by putting the URL into the bb-hosts file. Note that this only applies to URL's that begin with "http:" or "https:".- Basic Authentication with username/password
- If the URL requires authentication in the form of a
username and password, it is most likely using the HTTP "Basic"
authentication. bbtest-net support this, and you can provide the username
and password either by embedding them in the URL e.g.
http://USERNAME:PASSWORD@www.sample.com/
- Authentication with SSL client certificates
- An SSL client certificate can be used for authentication.
To use this, the client certificate must be stored in a PEM-formatted file
together with the client certificate key, in the $BBHOME/certs/ directory.
The URL is then given as
http://CERT:FILENAME@www.sample.com/
- Forcing an HTTP or SSL version
- Some SSL sites will only allow you to connect, if you use
specific "dialects" of HTTP or SSL. Normally this is
auto-negotiated, but experience shows that this fails on some systems.
- Testing sites by IP-address
- bbtest-net ignores the "testip" tag normally used
to force a test to use the IP-address from the bb-hosts file instead of
the hostname, when it performs http and https tests.
- HTTP Testing via proxy
- bbtest-net supports the Big Brother syntax for specifying
an HTTP proxy to use when performing http tests. This syntax just joins
the proxy- and the target-URL into one, e.g.
http://webproxy.sample.com:3128/http://www.foo.com/
http://fred:Wilma1@webproxy.sample.com:3128/http://www.foo.com/
- cont[=COLUMN];URL;[expected_data_regexp|#digesttype:digest]
- This tag is used to specify a http/https check, where it is
also checked that specific content is present in the server response.
\n Newline (LF, ASCII 10 decimal)
\r Carriage return (CR, ASCII 13 decimal)
\t TAB (ASCII 8 decimal)
\\ Backslash (ASCII 92 decimal)
\XX The character with ASCII hex-value XX
- content=URL
- This syntax is deprecated. You should use the
"cont" tag instead, see above.
- post[=COLUMN];URL;form-data;[expected_data_regexp|#digesttype:digest]
- This tag can be used to test web pages, that use an input
form. Data can be posted to the form by specifying them in the form-data
field, and the result can be checked as if it was a normal content check
(see above for a description of the cont-tag and the restrictions on how
the URL must be writen).
<form action="/cgi-bin/form.cgi" method="post">
<p>Given name<input type="text" name="givenname"></p>
<p>Surname<input type="text" name="surname"></p>
<input type="submit" value="Send">
</form>
givenname=John&surname=Doe+Jr.
- nocont[=COLUMN];URL;forbidden_data_regexp
- This tag works just like "cont" tag, but reverses
the test. It is green when the "forbidden_data_regexp" is NOT
found in the response, and red when it IS found. So it can be used to
watch for data that should NOT be present in the response, e.g. a server
error message.
- nopost[=COLUMN];URL;form-data;expected_data_regexp
- This tag works just like "post" tag, but reverses
the test. It is green when the "forbidden_data_regexp" is NOT
found in the response, and red when it IS found. So it can be used to
watch for data that should NOT be present in the response, e.g. a server
error message.
- type[=COLUMN];URL;expected_content_type
- This is a variant of the content check - instead of
checking the content data, it checks the type of the data as given by the
HTTP Content-Type: header. This can used to check if a URL returns e.g. a
PDF file, regardless of what is inside the PDF file.
- soap[=COLUMN];URL;SOAPMESSAGE;[expected_data_regexp|#digesttype:digest]
- Send SOAP message over HTTP. This is identical to the
"cont" test, except that the request sent to the server uses a
Content-type of "application/soap+xml", and it also sends a
"SOAPAction" header with the URL. SOAPMESSAGE is the SOAP
message sent to the server. Since SOAP messages are usually XML documents,
you can store this in a separate file by specifying
"file:FILENAME" as the SOAPMESSAGE parameter. E.g. a test
specification of
soap=echo;http://soap.foo.bar/baz?wsdl;file:/home/foo/msg.xml;. will read the SOAP message from the file /home/foo/msg.xml and post it to the URL http://soap.foo.bar/bas?wsdl
- nosoap[=COLUMN];URL;SOAPMESSAGE;[forbidden_data_regexp|#digesttype:digest]
- This tag works just like "soap" tag, but reverses
the test. It is green when the "forbidden_data_regexp" is NOT
found in the response, and red when it IS found. So it can be used to
watch for data that should NOT be present in the response, e.g. a server
error message.
- httpstatus[=COLUMN];URL;okstatusexpr;notokstatusexpr
- This is used to explicitly test for certain HTTP
statuscodes returned when the URL is requested. The okstatusexpr
and nokokstatusexpr expressions are Perl-compatible regular
expressions, e.g. "2..|302" will match all OK codes and the
redirect (302) status code. If the URL cannot be retrived, the status is
"999".
- HIDEHTTP
- The status display for HTTP checks usually includes the
URL, and for content checks also the actual data from the webpage. If you
would like to hide these from view, then the HIDEHTTP tag will keep this
information from showing up on the status webpages.
- browser=BROWSERNAME
- By default, Xymon sends an HTTP "User-Agent"
header identifying it a "Xymon". Some websites require that you
use a specific browser, typically Internet Explorer. To cater for testing
of such sites, this tag can be used to modify the data sent in the
User-Agent header.
LDAP (DIRECTORY SERVER) TESTS¶
- ldap
- ldaps
- Simple check for an LDAP service. This check merely looks
for any service running on the ldap/ldaps service port, but does not
perform any actual LDAP transaction.
- ldap://hostport/dn[?attrs[?scope[?filter[?exts]]]]
- Check for an LDAP service by performing an LDAP request.
This tag is in the form of an LDAP URI (cf. RFC 2255). This type of LDAP
test requires that bbtest-net(1) was built with support for LDAP,
e.g. via the OpenLDAP library. The components of the LDAP URI are:
hostport is a host name with an optional ":portnumber" dn is the search base attrs is a comma separated list of attributes to request scope is one of these three strings: base one sub (default=base) filter is filter exts are recognized set of LDAP and/or API extensions.
- ldaps://hostport/dn[?attrs[?scope[?filter[?exts]]]]
- LDAP service check using LDAPv3 and STARTTLS for talking to
an LDAP server that requires TLS encryption. See bbtest-net(1) for
a discussion of the different ways of running LDAP servers with SSL/TLS,
and which of these are supported by bbtest-net.
- ldaplogin=username:password
- Define a username and password to use when binding to the
LDAP server for ldap URI tests. If not specified, bbtest-net will attempt
an anonymous bind.
- ldapyellowfail
- Used with an LDAP URL test. If the LDAP query fails during
the search of the directory, the ldap status is normally reported as
"red" (alarm). This tag reduces a search failure to a
"yellow" (warning) status.
PERFORMANCE MONITORING TESTS¶
- apache[=URL]
- If you are running an Apache webserver, adding this tag
makes bbtest-net(1) collect performance statistics from the Apache
webserver by querying the URL
http://IP.ADDRESS.OF.HOST/server-status?auto. The response is sent
as a data-report and processed by the Xymon hobbitd_rrd module into an RRD
file and an "apache" graph. If your webserver requires e.g.
authentication, or runs on a different URL for the server-status, you can
provide the full URL needed to fetch the server-status page, e.g.
apache=http://LOGIN:PASSWORD@10.0.0.1/server-status?auto for a
password protected server-status page, or
apache=http://10.0.0.1:8080/apache/server-status?auto for a server
listening on port 8080 and with a different path to the server-status
page.
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
allow from 127.0.0.1
</Location>
ExtendedStatus On
DEFAULT HOST¶
If you have certain tags that you want to apply to all hosts, you can define a host name ".default." and put the tags on that host. Note that per-host definitions will override the default ones.SENDING SUMMARIES TO REMOTE XYMON SERVERS¶
- summary ROW.COLUMN IP URL
- If you have multiple Xymon servers, the "summary"
directive lets you form a hierarchy of servers by sending the overall
status of this server to a remote Xymon server, which then displays this
in a special summary section. E.g. if your offices are spread over three
locations, you can have a Xymon server at each office. These branch-office
Xymon have a "summary" definition in their bb-hosts file that
makes them report the overall status of their branch Xymon to the central
Xymon server you maintain at the corporate headquarters.
summary Vegas.All 10.0.1.1 http://vegas.foo.com/xymon/
summary Vegas.Sales 10.0.1.1 http://vegas.foo.com/xymon/sales/
OTHER TAGS¶
- pulldata[=[IP][:port]]
- This option is recognized by the hobbitfetch(8)
utility, and causes it to poll the host for client data. The optional
IP-address and port-number can be used if the client-side
msgcache(8) daemon is listening on a non-standard IP-address or
port-number.
FILES¶
~xymon/server/etc/bb-hostsSEE ALSO¶
bbgen(1), bbtest-net(1), bbdigest(1), hobbitserver.cfg(5), xymon(7)Version 4.2.3: 4 Feb 2009 | Xymon |