Event, Alerts, Perf Data Flow in OpsMgr 2007
2012-08-09 17:04
537 查看
相信刚开始接触SCOM的同学对于整个数据流不是很了解,导致在排错的时候遇到了很多困难。这里我找了一张很好的数据流图片供大家参考:
Data Type Flow:
Events/Perf/State data is sent from OpsMgr 2007 agents to their primary Management Server which then write to the Operational database and data warehouse simultaneously.
Heartbeats are sent to the Root Management Server from the management servers in the environment. If an OpsMgr 2007 agent goes down for some reason and therefore does not report to its primary or secondary management servers the root management server will change the state of the agent from healthy to unavailable. Only these state changes are registered in the Operational Database, otherwise heartbeats data is not written in the Operational Database.
Alert/Discovery Agents send alert and discovery data to their primary management servers which then write directly to the Operational Database and the SDK service on the root management server then pulls the data from the Operational Database and displays in your console. The sync module on the root management server then reflects the alerts and discovery data changes into the data warehouse.
http://blogs.technet.com/b/momteam/archive/2007/10/30/event-alerts-perf-data-flow-in-opsmgr-2007.aspx
Data Type Flow:
Events/Perf/State data is sent from OpsMgr 2007 agents to their primary Management Server which then write to the Operational database and data warehouse simultaneously.
Heartbeats are sent to the Root Management Server from the management servers in the environment. If an OpsMgr 2007 agent goes down for some reason and therefore does not report to its primary or secondary management servers the root management server will change the state of the agent from healthy to unavailable. Only these state changes are registered in the Operational Database, otherwise heartbeats data is not written in the Operational Database.
Alert/Discovery Agents send alert and discovery data to their primary management servers which then write directly to the Operational Database and the SDK service on the root management server then pulls the data from the Operational Database and displays in your console. The sync module on the root management server then reflects the alerts and discovery data changes into the data warehouse.
http://blogs.technet.com/b/momteam/archive/2007/10/30/event-alerts-perf-data-flow-in-opsmgr-2007.aspx
相关文章推荐
- ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2
- [DirectShow] 012 - Overview of Data Flow in DirectShow
- ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2
- The supplied data appears to be in the Office 2007+ XML
- SharePoint 2007运行 Edit In DataSheet 时在IE 6下页面卡死的分析和处理方法
- 翻译 Extjs in action中的Event flow in the DOM
- [转]How to handle Failed Rows in a Data Flow
- ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 77, even
- Data Flow in the Filter Graph
- How to backup and restore data and e-mail account settings in Outlook 2007
- Spring - Spring Data REST - Prevent The Methods in Event Handlers Be Triggered Twice
- Sharepoint 2007 用代码聚合所有子网站文章 (populating data sources in code)
- SharePoint 2007运行 Edit In DataSheet 时在IE 6下页面卡死的分析和处理方法
- Passing data between event loops in multithreaded apps
- Graphical Data Flow Modeling in SAP BW 7.3(避免传输丢失)
- visual event recognition in videos by learning from web data
- ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 234781854, event_type: 2
- ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2
- ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2
- why request event is fired before data event in http modlues of node.js.