Blog Summary for Week of September 26

1: HTTP Extraction with Monitis
Say you want to monitor some metric, such as the temperature in your neighborhood, or a stock price, or your number of twitter subscribers. How would you go about doing that? This post shows how to extract content from an http webpage and monitor it using Monitis. M3 – Monitis Monitor Manager is utilized to manage adding monitors to Monitis via API. In the example shown, a temperature is recorded from using a JSON extraction script and fed to Monitis. There is also an attribute for loading HTTP statistics like latency, page size and HTTP code. A graph is shown plotting the temperature in Wanaka, New Zealand.

2: Monitor Everything with Monitis – And do it easily with PowerShell – Part 3
The last article in this series showed some of the commands related to external monitoring in Monitis and Powershell. This article focuses on one of those commands: Get- MonitisMonitorResult. Get-MonitisMonitorResult gives you results from any type of Monitor. You use it by piping in the monitors you want. For instance, this will show todays results from the current monitor:
Get-MonitisExternalMonitor | Select-Object -First 1 | Get-MonitisMonitorResult
You can use the –Last parameter to get results for the last 3 days:Get-MonitisExternalMonitor |
Select-Object -First 1 |
Get-MonitisMonitorResult -Last (New-TimeSpan -Days 3)
This post shows several other ways to use the Get-MonitisMonitorResult command.

3: Notification rules are a bit simpler now
This post explains a recent change made to Monitis notification rules. Prior to this change, users had to select monitoring locations when setting notification rules. For example, if a user selected US West and Spain, any failure in those two locations would cause an alert to be sent. This caused some confusion when users started changing their monitoring locations without remembering to edit the corresponding rules. So Monitis has simplified this a bit by removing the need to select locations. Now, a user only has to select the minimum number of failing locations required to send an alert.