Monitor Everything with Monitis – And do it easily with PowerShell – Part 1

Monitis is an amazing cloud monitoring SaaS platform.  It lets you monitor everything.  And we do mean everything.    Monitis has an amazing set of built in monitors that let you monitor every major web protocol, and Monitis has a structure to allow you to upload a custom monitor to keep track of anything.

PowerShell is a task-based automation platform built right into the Windows operating system.  PowerShell lets you perform tasks simple and easily, using logically named commands, like Get-command, Get-Help, or Send-MailMessage.

Monitis has partnered with the PowerShell experts at Start-Automating to make monitoring anything and everything easy in Montiis a piece of cake in PowerShell.  Monitis now has a rich PowerShell module to manage its incredible monitoring system.

You can download open source Monitis PowersShell Modules here, or run it online, at

Let’s start really simple.   Go ahead and download the module.  When you’ve got it, extract it to:

My Documents\WindowsPowerShell\Modules\Monitis

Now go ahead and launch Powershell ISE.  If you’re on Windows 7, it will be built right in.  If you’re on Server 2K8R2, you will have to enable the feature.   If you’re on an older operating system, you might need to download the Windows Management Framework, which includes PowerShell V2.

If you’ve never run PowerShell before, you’ll probably want to change the execution policy.  The execution policy is a nifty feature of PowerShell that helps protect people who don’t use PowerShell from accidentally running scripts they don’t trust.  You can turn it off at any time, but it’s on by default when Powershell is installed.

Since you downloaded your module from the internet, you will need to use the Execution Policy bypass.  If you want to always have it this way, run PowerShell.exe as an admin and then run: Set-ExecutionPolicy Bypass –Force.  If you only want to trust things for this article, just run PowerShell ISE as a regular user, and start by typing:

Set-ExecutionPolicy –Scope Process Bypass –Force

Great, now the execution policy has been changed, and you can run whatever you’d like.  Let’s import the Monitis Module:


Let’s use a simple PowerShell pipeline to find every command in the module:


Let’s go ahead and add a simple external monitor to make sure a site is working.

Add-MonitisExternalMonitor -Name "MyWebSite" -Tag WebMonitors -MonitorType http -Url -ApiKey 20ECHRRRMK88L31KH6OMDU0BNR -SecretKey 26CQ6QUIRF571P1BHU3CV37MR0

In the Monitis dashboard, go to monitors, External, and a screen will pop up showing you all of the external monitors that you’ve added with the API, and let you add them to the dashboard:

That’s it!

Monitis is now monitoring from multiple locations around the world, keeping track of how long it takes to respond.