https://www.infra-repository.org/oiar-2013/index.php?action=history&feed=atom&title=PAT.Facilities_Monitoring 2026-05-06T13:48:18Z Revision history for this page on the wiki MediaWiki 1.40.0 https://www.infra-repository.org/oiar-2013/index.php?title=PAT.Facilities_Monitoring&diff=542&oldid=prev 2012-11-11T23:22:21Z

<p>start</p> <p><b>New page</b></p><div>{{Maturity|3}}<br /> {{Pageheaderbox4PatternType<br /> |PATname=Facilities Monitoring<br /> |summary=Comprises a set of facilities to enable centralized and intelligent monitoring of automated systems, either or both for system health care and security purposes<br /> |version=0.3<br /> |owner=S.A.D. Jumelet<br /> |sector=Infrastructure Sector Operations<br /> }}<br /> This Pattern Type serves as the definition for the majority of all solutions that IT Operations and or Security Maintenance use to monitor the IT infrastructure.<br /> {{PAgraphic<br /> |graphic=PAT.Facilities Monitoring.png<br /> |source=Pattern Facilities Monitoring.vsd<br /> |size=450px<br /> |title=Facilities Monitoring pattern<br /> }}<br /> {{Pattern Type Composition}}<br /> {{Pattern Type Composition Row<br /> |facility=BT.Alerting<br /> |choice=may<br /> |reason=This facility handles warning messages and/or signals that are triggered by the processing of logging and reporting data.<br /> }}<br /> {{Pattern Type Composition Row<br /> |facility=BT.Process Engine<br /> |choice=must<br /> |reason=The Process Engine facility is the heart of automated monitoring solutions. It processes logging and reporting data. Depending on its implementation, it may normalize, correlate and/or analyze logging data. Based pre-defined rules and/or automated analysis, it generates monitoring data and alerts.<br /> }}<br /> {{Pattern Type Composition Row<br /> |facility=BT.Logging<br /> |choice=must<br /> |reason=A logging facility provides a (central) place where system messages are collected. Logging data is used as input to the Process Engine.<br /> }}<br /> {{Pattern Type Composition Row<br /> |facility=BT.Reporting<br /> |choice=may<br /> |reason=This facility carries out reporting regarding system activities. Reporting data is used as input to the Process Engine.<br /> }}<br /> {{Pattern Type Composition Row<br /> |facility=BT.Control Interface<br /> |choice=may<br /> |reason=The Control Interface facility provides management access to monitoring solutions. It should at least offer a programming interface to operators.<br /> }}<br /> {{Pattern Type Composition Row<br /> |facility=BT.Configuration Retrieval<br /> |choice=may<br /> |reason=In some cases, facilities are being monitored by comparing actual configurations and stored configurations. By using the Configuration Retrieval facility, actual configurations are being collected. This function is used in conjunction with Configuration Register facilities, where stored configurations reside.<br /> }}<br /> {{Pattern Type Composition Row<br /> |facility=BT.Configuration Register<br /> |choice=may<br /> |reason=In some cases, facilities are being monitored by comparing actual configurations and stored configurations. Configuration Register facilities are used to lookup stored configurations, in order to compare them with configurations that are collected using a Configuration Retrieval facility.<br /> }}<br /> {{Pattern Type Composition Row<br /> |facility=BT.Scheduling<br /> |choice=may<br /> |reason=This function, if present, can trigger periodic or scheduled configuration retrievals.<br /> }}<br /> {{Table Ending}}<br /> {{Pattern Type Neighbors}}<br /> {{Pattern_Type_Adjacent_PAT_Row<br /> |pattern=PAT.Authentication+Authorization<br /> |choice=must<br /> |reason=Configuration of the Process Engine of a monitoring solution should be restricted to authorized operators and it should be possible to trace back changes to operators that issued those. Therefore, it should be possible to validate the permissions and identities of operators that manage this facility.<br /> }}<br /> {{Table Ending}}<br /> {{PATfooter}}</div>

Jan Schoonderbeek