From 944b0daff3e9d901da8ae73d78f526f55cbe653e Mon Sep 17 00:00:00 2001 From: Joey Hagedorn Date: Thu, 15 Sep 2005 06:17:45 +0000 Subject: added Why to report section. (Logical change 1.315) git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@1283 ce84e21b-d406-0410-9b95-82705330c041 --- doc/reports.xml | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-) (limited to 'doc') diff --git a/doc/reports.xml b/doc/reports.xml index 9f9a46516..76f609fb8 100644 --- a/doc/reports.xml +++ b/doc/reports.xml @@ -50,14 +50,22 @@
- Concepts -- Why to report, big picture + Concepts; Why to report - So you'll recive a report-- however you might get it--and - it'll contain any sort of info, like general net health, or specific - node broken packages, or... whatever. You choose. This will help you - correct your configuratin file, and audit things, and fix any nodes - that got all hosed. - + Reports play an important role in effectively managing systems + with BCFG. There are two primary functions they fulfill; providing + otherwise unobtainable information, and presenting additional + helpful information to allow for easier admistration. Reports + can contain information including system statistics, discrepancies + between specified and actual configuration, invalid configuration, + and auditing information among other things. + + The flexible XML configuration file allows reports to be configured + to deliver only the information that is important. Additional reports + can easily be created, providing site-specific capability to manage + at record effiency. The capability to harvest information regarding + statistics, configuration, and problems in a single location should + prove to be powerful.
@@ -172,7 +180,7 @@ - Here is a list of possible delivery mechanisms. + A list of delivery mechanisms follows: -- cgit v1.2.3-1-g7c22