How i can generate report which will tell me that my SCOM environment is out of capacity or still can take load

Hi All,

is it possible to automate a report which will tell that SCOM or any other Microsoft product is over capacity or still not over utilized. By considering the number of CPU memory and the type of storage attached to machine and amount of transaction happening from agent or User connectivity with application. So the management can take quick decision to increase the capacity or look in to deep level where exactly its having problem that its not giving the exact performance.

Thanks,

Onkar Um

May 30th, 2015 3:57am

Hi Omkar,

This can be identified by the alerts trigered by your MS or your MS is throwing alerts for your MS Server its self.

So you will need to have a close look on the operations console or subscribe the alerts via email.

Also based on your alerting latency. Are your alerts appearing on time when the event / issue occurs on your agents ? Lets say one of the service stopped and within a max of 1 min you get an alert for it. So if your alerting is fine then i would consider a Healthy MS

If there is latency like 5 hrs old alert appearing now then there is performance issues and you will need to look at it.

For resource utilization you can use / create performance based alert targeting to MS for Memory an CPU Utilization.

Also below is the capacity chart for SCOM As well.

Hoping you used the Seizer tool for the same.

Ill post the sheet later as i am not getting that link here.

Free Windows Admin Tool Kit Click here and download it now
May 31st, 2015 5:17pm

Below is the capacity chart

Operations Manager supports the following number of monitored items.

Monitored item

Recommended limit

Simultaneous Operations consoles

50

Agent-monitored computers reporting to a management server

3,000

Agent-monitored computers reporting to a gateway server

2,000

Agentless Exception Monitored (AEM)-computers per dedicated management server

25,000

Agentless Exception Monitored (AEM)-computers per management group

100,000

Collective client monitored computers per management server

2,500

Management servers per agent for multihoming

4

Agentless-managed computers per management server

10

Agentless-managed computers per management group

60

Agent-managed and UNIX or Linux computers per management group

6,000 (with 50 open consoles); 15,000 (with 25 open consoles)

UNIX or Linux computers per dedicated management server

500

UNIX or Linux computers monitored per dedicated gateway server

100

Network devices managed by a resource pool with three or more management servers

1,000

Network devices managed by two resource pools

2,000

Agents for Application Performance Monitoring (APM)

700

Applications for Application Performance Monitoring (APM)

400

URLs monitored per dedicated management server

3000

URLs monitored per dedicated management group

12,000

URLs monitored per agent

50

June 9th, 2015 3:39am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics