System Center R2 Instance 3-Deploying scom monitoring sharepoint9-memory monitoring

In the last section we monitor the CPU load, and in this section we set the monitoring for the memory.

SharePoint monitoring ②: Memory monitoring of hardware monitoring

Alert Thresholds:

Server	DB1	DB2	APP1	APP2	SCH1	WFE1	WFE2	DB3	DC
Memory Available MBytes	1000	1000	1000	1000	1000	1000	1000	1000	1000

1. Configuring Memory Monitoring

We're still in the creation, monitor->windows Server R2 full Operating system-> performance

The default memory-aware monitor has available megabytes of memories and memory Pages Per Second

650) this.width=650; "title=" clip_image002 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/M00/6F/0A/ Wkiom1wqafvsgifdaafratlatdo415.jpg "height=" 248 "/>

Here we replace available megabytes of memory, you can use the threshold value, the replacement value is changed to 1000MB.

650) this.width=650; "title=" clip_image004 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/M00/6F/06/ Wkiol1wqa8vhltqbaahv8g3t2tq272.jpg "height=" 529 "/>

2. Test alarms

Because I this experiment environment, memory ratio is not much relationship, set effective shortly after the receipt of a large number of messages, are about memory 650) this.width=650; "title=" clip_image006 "style=" border-top:0px; border-right:0px;border-bottom:0px;border-left:0px; "border=" 0 "alt=" clip_image006 "src=" http://s3.51cto.com/ Wyfs02/m02/6f/06/wkiol1wqa83xgjxxaadvqc1z5me930.jpg "height=" 117 "/>

Enter the active alert, you can also find a large number of alerts, but how all the same look, how to simply distinguish which server is the alarm issued?

650) this.width=650; "title=" clip_image008 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image008 "src=" Http://s3.51cto.com/wyfs02/M00/6F/0A/wKiom1WQAg_AsifDAAEjda5tt_ G018.jpg "height=" 216 "/>

Right click on Personalization view

650) this.width=650; "title=" clip_image010 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/M00/6F/0A/ Wkiom1wqahksce9vaaccedozgny190.jpg "height=" 285 "/>

Tick the path and click OK to make the personalization view effective

650) this.width=650; "title=" clip_image012 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/M01/6F/0A/ Wkiom1wqahxbmi04aaea3kuqnkm454.jpg "height=" 365 "/>

In this way, you will be able to see at a glance that the server is the alarm.

650) this.width=650; "title=" clip_image014 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image014 "src=" http://s3.51cto.com/wyfs02/M02/6F/0A/ Wkiom1wqahfgtfrtaae-z8suo8k760.jpg "height=" 213 "/>

Now when all alerts are selected, right-click on the menu to close the alert.

650) this.width=650; "title=" clip_image016 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image016 "src=" http://s3.51cto.com/wyfs02/M00/6F/0A/ Wkiom1wqahmdfemcaacdxpa9kpy700.jpg "height=" 284 "/>

You can view the resolution status as closed in all alerts (this time you can change the resolution state manually)

650) this.width=650; "title=" clip_image018 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image018 "src=" http://s3.51cto.com/wyfs02/M01/6F/06/ Wkiol1wqa9zrtrr-aae-ppzafoe941.jpg "height=" 184 "/>

This way, there will be no active alert notifications until the memory recovery is idle.

3. Understanding of the Monitor's alarms

a monitor measures the health of one aspect of a managed object , each with two or three health states. At any time, the monitor will be in one and only one of its potential states. When the agent loads the monitor, the monitor is initialized to a normal state. This state is changed only when a specified condition of another state is detected.

When you create a monitor, you must specify a condition for each of its health states. When one of these conditions is met, the monitor changes to that state. Each condition must be unique so that only one condition is true at a particular time. If the monitor changes to a warning or critical state, it may generate alerts as needed. If it changes to the normal state, any previously generated alerts can be automatically resolved as needed.

An alert is generated from the monitor only if each of the following is true:

1) Configure the monitor to generate an alert.

2) The health state of the monitor has changed from a normal state to a warning or error state, depending on the possible monitor health state.

3) The same object created by the same monitor does not have an open alert.

An alert is generated from the monitor only if the health state of the monitor changes from the normal state. Even if the condition of the error condition may occur more than once, multiple alerts are not generated when the health state of the monitor is set to warning or critical. A new alert is generated only if the health state of the monitor returns to normal and the error condition recurs.

So in this lab environment, even if the available memory alert status is turned off, no new active alerts will appear because the available memory is not back to normal (greater than 1000MB). The alert appears again only if the available memory is greater than 1000MB (back to normal, resetting the monitor) and is again less than 1000MB (exceeding the threshold).

This article is from the "Iron Fist of the Invincible Speaker" blog, please be sure to keep this source http://yaojiwei.blog.51cto.com/762134/1668846

System Center R2 Instance 3-Deploying scom monitoring sharepoint9-memory monitoring