 in the logging con- figuration file are: create the default logs directory direct log messages to configout and configerr files distinguish the file to which output messages are sent from the file to which error messages are sent set to "3" the default logging level for the various modules of the product. We give some of the more important logging parameters to indicate the extent to which logging can be customised. It is only possible to report upon information that is logged which puts logging and its customization near the centre of network man- agement. For example, the dependence of reporting on logging means that any data that are relevant to SLA management must be logged for future reference. Indeed, it is arguable that any data that are materially relevant to network performance - and so which might impact upon customer experience - should be logged for potential future reporting, in order that the carrier can correlate such things as negative customer experiences with network events. Thus, customizability of logging is important in limiting or enabling the ability of a carrier to monitor the standard of their services. Logging parameters are as follows: Filename: Name of the file in which the log messages are to be written. MaxLines: Limits the number of lines in the log files to a desired value. When there are additional lines to be written, a new file is created, for example, configerr.txt, configerr1.txt, or configerr2.txt. MaxLinesCached: Limits the number of times the log messages are written in the specified text file. The default value for the parameter "MaxlinesCached" is 0 in the logging parameters configuration file, which means that messages are not 43 In the second phase of the WINMAN project (to develop an integrated management system for IP-over- DWDM networks), implementing scheduling for periodic automated provisioning was a priority for just such as an application as informing fans of the scoring of football goals in real-time. 11 Configuration Management cached at all but are immediate