welcome back, today and in this article (Part 1) of Microsoft Operations Management Suite (OMS) we will take a deep look about the concept of OMS, in next two parts we will discuss the technical side of implementing OMS in your environment.
one big challenge facing the IT team in any company these days is to monitoring their datacenters, this task is taking a high efforts and time from the IT team to keep their datacenters under monitoring.
Nothing is perfect … Not even your datacenter, as every thing else your datacenter need an extra efforts and cares to meet the SLA in your company, there are a lot of products such as SCOM, Nagios … etc. which help the IT team to monitor their datacenters, these products need to be implemented ( Complex Implementation) in your environment in addition to the tuning of alerts we will do after the implementation which will take high efforts and time, also in this case some times you need to monitor the monitoring products itself 🙂
Now let’s take a look about detention of OMS:
OMS is a Microsoft cloud solution which responsible for monitoring your on premise datacenters in addition to cloud ones if exist, OMS can provide the IT team with a meaningful alerts and baselines to help them to be aware about the status of their datacenters.
OMS support windows and Linux machines, it works based on agent which need to be installed on all servers with few clicks and the monitoring will start working automatically without the need of implementation complexity.
The Magic of OMS:
OMS is up to date with Microsoft baseline and this is one of the great features in it, which means if Microsoft release any new baseline check for AD, SQL, Storage … etc. it will be add to the monitoring rules automatically, so the admins don’t need to be worry about editing any alert rule or installing any management pack like in SCOM.
Also, OMS can be integrated with SCOM if you have to gain more benefits from it which we will talk more about it in next part, but keep in mind here that if you already use SCOM you can ignore the step of installing the OMS agent on the servers, in this case SCOM will be responsible to collect the required data from all servers and send it to the OMS.
OMS as any other monitoring solutions have a baselines, the alert rules will follow these baselines to generate an alerts, alerts have different status for example (High, very risk, Normal, Need and action … etc.), for now you cannot edit these baselines, in other word you cannot say ” Please OMS in next time when you generate this type of alert give a status of normal not Risk), maybe in next days Microsoft decide to allow users to do this.
OMS have many pricing plans based on your environment requirements including a free plan, you can use the free plan for a life time but with two major limitations, the first on is the daily size of transferred data, which means if you decide to use the free version of OMS your servers cannot transfer more than 500MB per day in addition to only max. of one week data retention
For more info about OMS pricing follow Microsoft site: https://www.microsoft.com/en/server-cloud/operations-management-suite/pricing.aspx
In Next part we will discuss more about the concept of OMS and the technical sides, so keep tuned 🙂
About blogger …
Ahmad Yasin in a Microsoft Cloud Engineer and the publisher of
AzureDummies blog. He also hold many certificates in office 365
and windows azure including Developing Microsoft Azure Solutions, Implementing Microsoft Azure Infrastructure Solutions
and MCSA office 365.