Tartarus client report
Client side
Every DICE system runs
/usr/lib/tartarus/bin/clientreport
at boot time and periodically (currently twice a day) thereafter. This harvests a variety of information on the system and submits it to the Tartarus system over GSSAPI authenticated HTTP. The information is harvested by individual modules - eg DMI, Disk, LCFG, Network.
Additional modules, written in Perl, are simple to produce (see Tartarus-clientreport in the DICE SVN repository). A module must provide a
probe()
which returns a hash of values. It is mandatory that this hash includes the following keys :-
-
_errors
- indicating success, or otherwise, of the probe. Value 0 for success, 1 for failure
-
_version
- indicating the schema version of the returned hash. This would prove useful should you changed the format of your returned data.
Note that if a system's managed_type is set to anything other than 'dice', any entry for that system in the
client_report
table is wiped.
Server side
The client reports are submitted to the
/cgi-bin/krbsecured/submitjson
script in the Tartarus web root (
/usr/lib/tartarus/web
). This updates the relevant row in the
client_report
table.
--
AlastairScobie - 20 Sep 2019