Performance Me of events or alerts processed in a specified time interval can be printed in TL1 Devices server logs using this configuration Miscellaneous Events Alarms Event Performance Configuration Enable Event Performance calculation Time Period EventCount count Log Now Apply Cancel Performance Metrics Apply Choosing Apply button will apply the performance configuration details to Server. LogNow Log Now can be selected if the performance details are needed immediately. Cancel Cancel option can be made use of to revert to the previously applied changes Done. Figure 12.35 Configuring performance metrics. 12.13 Conclusion Fault management is largely a matter of alarm and alert management. Indeed, some vendors use the term "alarm management" rather than "fault management" in their OSS modules. The fact that network devices generate alarms when they are in a fault state allows OSS for fault management to focus on the abstraction, rather than being involved in the job of examining devices and checking whether they are in a fault state. This functionality will become more advanced as devices are increasingly able to repair themselves or be aware of what type of corrective action to take if they are in a fault state. It will be increasingly rare for a human to be required to process a fault alert. Fault management is also largely a matter of information management. An OSS vendor is not too concerned about how to go about fixing an NE. Rather, they merely create a hub to where information on faults is sent and from where instruc- tions on how to fix the fault are sent out. The OSS then allows the service provider to 12 Fault Management implement their own fault correction procedures according to their particular busi- ness and the needs of the network infrastructure that they have in place. Increasing intelligence in NEs will lead to some faults bypassing the OSS altogether. For example, a device that is in a fault state might know to contact a field engineer directly for repairs and only inform the central OSS if the