Blog Summary for week of October 10

1. Monitor Everything with Monitis – And do it easily with PowerShell – Part 5
If you’ve read the previous posts in this series, you know how easy it is to set up monitors in Monitis using Powershell, without any downloads. This article shows some two powerful parameters of the Add-MonitisExternalMonitor command and how to use them in MS Excel to create all your web monitors in Powershell. The two important parameters of the Add -MonitisExternalMonitor command are ExpectedContentPattern – A regular expression you expect to find in the results, and RequiredResponseTime – the maximum amount of time it should take to get a response. In Excel, you can create a table with the columns Url, MonitorType, OperationType, Postdata, ExpectedContentPattern, RequiredResponseTime. Then simply fill in row by row the details of your monitors. Once you have them ready, you can save it as a CSV file and use the command Connect-Monitis -ApiKey $apiKey -SecretKey $secretKey
Import-Csv .\MyWebTest.csv | Add-MonitisExternalMonitor to create the monitors in Monitis. Yet another way to do a lot with just a few simple steps.

2. Virtualization in Q&A
Virtualization is a hot topic of conversation today in IT. If you’re an IT administrator or manager, you’ve no doubt considered using it in your environment. Many infrastructures are making the switch from physical to virtual servers for efficiency and flexibility. This article is a list of questions that most IT administrators have about virtualization along with answers. One of the interesting things explained is the difference between Type 1 and Type 2 hypervisors. A hypervisor is a Virtual Machine Manager. Type 1 runs on hardware itself, and Type 2 runs on an OS, like Oracle’s VirtualBox for example. The article dives into some advantages of virtualization and gives some valuable tips on choosing between vendors. A must read for anyone in IT thinking about implementing a virtualized environment.

3. Monitor Everything with Monitis – And do it easily with PowerShell – Part 6
In the last few articles, we’ve been walking through how to easy it is to use external monitors in Monitis when you use the Monitis PowerShell module. External monitors are just the beginning. The real power of Monitis comes from being able to upload your own custom monitor. Most monitoring systems require you to download an agent every time you want to monitor an application, but if you’re ISO 27001 compliant, this has to go through security review. With Monitis custom monitors, you don’t need agents! Just create scripts and use our REST API. The post illustrates how to connect to Monitis with PowerShell and create a custom monitor with the command Add-MonitisCustomMonitor. The next post will show how to feed data into the new monitors you’ve created.

4. SharePoint Performance Monitoring
Have you implemented SharePoint in your network? If so, then you’ve added new requirements to your performance monitoring needs. This article is about the basic monitoring needed if you have Sharepoint running in your network. You’ll need to monitor metrics related to CPU, Memory, and Disk. For CPU, for example you’ll need to track Queue Length, utilization, and Interrupts to understand how much strain Sharepoint is causing on your hardware. Most of these monitors are available using the Internal Agent in Monitis. The next post will talk about how to use custom monitors for metrics specific to Sharepoint.

5. Monitor Everything with Monitis – And do it easily with PowerShell – Part 7
This article shows how to create a custom hardware inventory in Monitis with PowerShell, and update it in the same script. This is a pretty powerful thing. Imagine keeping track of detailed information about your hardware in the cloud without downloading anything. This involves three commands: Add-MonitisCustomMonitor,
Get-MonitisCustomMonitor, and Update-MonitisCustomMonitor. These commands allow you to monitor absolutely anything with Monitis. You will have a script that you to monitor anything in Monitis. You’ll have a script that you can run on any Windows box, because Powershell is installed by default on every Windows machine from Win7/Server2k8R2 onward. One of the powerful things you can do with Powershell is collect hardware information from WMI. For example, the command Get-WmiObject Win32_ComputerSystem gets the make and model of the PC. Now the post shows how to use this in a custom monitor with the command $computerSystem = Get-WmiObject Win32_ComputerSystem. This command saves the make and model information as a variable which we can call later without having to keep calling WMI. The post shows further scripts that feed more hardware related information to Monitis. The next post shows how to monitor Windows installations using custom monitors.