hobbitd_filestore is a worker module for hobbitd, and as such it is normally
run via the
program. It receives hobbitd messages from a hobbitd channel via stdin, and
stores these in the filesystem in a manner that is compatible with the
Big Brother daemon, bbd.
This program can be started multiple times, if you want to store
messages for more than one channel.
Incoming messages are "status" messages, they will be stored in the
$BBLOGS/ directory. If you are using
throughout your Xymon server, you will not need to run this
module to save status messages, unless you have a third-party
add-on that reads the status-logs directly.
This module is NOT needed to get trend graphs, you should run the
Incoming messages are "data" messages, they will be stored in the
$BBDATA directory. This module is not needed, unless you have a
third-party module that processes the data-files. This module is
NOT needed to get trend graphs, you should run the
Incoming messages are "notes" messages, they will be stored in the
$BBNOTES directory. This modules is only needed if you want to
allow people to remotely update the notes-files available on the
Incoming messages are enable/disable messages, they will update
files in the $BBDISABLED directory. This is only needed if you have
third-party add-ons that use these files.
Overrides the default output directory.
Used together with "--status". Tells hobbitd_filestore to also save
an HTML version of the status-log. Should not be used unless you
must run with "BBLOGSTATUS=static".
The directory where HTML-versions of the status logs are stored.
Set the filename extension for generated HTML files. By default, HTML
files are saved with a ".html" extension.
This causes hobbitd_filestore to generate HTML status pages with links to
service graphs that are split up into multiple images, with at most 5 graphs
per image. If not specified, only the "disk" status is split up this way.
Save status messages only for the listed set of tests. This can be useful
if you have an external script that needs to parse some of the status logs,
but you do not want to save all status logs.
Enable debugging output.
This module does not rely on any configuration files.