Every organization has a few monitoring requirements that are very specific and sometimes unique. It might be a custom application written a long time ago and the original coders are long gone. Or it might be a legacy relational database whose vendor disappeared ages ago but your company still relies on it for important operations.

For these cases and others you can easily extend FrameFlow using simple scripts written in PowerShell, VBScript, PerlScript or JavaScript.

The following PowerShell script shows a simple example that checks the last line of a text log file and then generates alerts based on what it finds.

$server = "knothole";

$path = "\\$server\c$\Temp\InputFile.txt"

$lines = (Get-Content $path)[-1 .. -1]

if ($lines[0] -eq "Error")
{
    Write-Host "Failure($server)=The log file for '$server' indicates an error condition"
}
else
{
   Write-Host "Success($server)=No errors detected in the log file for '$server'."
}

Your scripts can perform practically any kind of check and then they either print "Success(ServerName)=Success message text" or they print "Failure(ServerName)=Error message text".

FrameFlow also lets you specify tokens in your scripts which are replaced with values from your monitoring configuration. For example if you assign your script to five network devices you can use the token %%devicename%% and it will be substituted for the device name for each of the five checks.

The previous example shows how to use scripts to implement custom monitoring actions but FrameFlow also lets you run scripts after the event monitor completes. The scripts can perform custom actions such as writing to a ticketing system or even taking corrective actions such as restarting a service, clearing out a log file or relaunching an app.