Creating Alerts and Reports

<< Click to Display Table of Contents >>

Navigation:  Introduction >

Creating Alerts and Reports

In the WinScry Client Console you can create 3 different types of Alerts. Select 1 of the 3 types of WinScry Alerts below:



System Status Report. This is a special type of alert that isn't driven by any type of "condition" occurring and instead generates a "Status Report" email automatically periodically (configured by you)


Conditional Alerts. Conditional alerts are triggered when "Alert Conditions" configured by you are met. You can create as many conditional alerts on a system as you like.


File API Alerts. The File API Alert is another special type of alert which allows ANY program to interface with WinScry. If you have a process which creates reports or alert data you can write those items to a file folder and WinScry will deliver them to you as an email attachment. You can create as many File API Alerts on a system as you like.


Creating Effective, Meaningful Alerts


Creating effective alerts always requires a certain amount of creativity. This discussion will mainly focus on Conditional Alerts, with some brief discussion of the System Status Report and File API Alerts. Typically the whole point of creating an alert is to notify you (the alert email recipient[s]) that something is amiss at a monitor installation. This means that you want to do your best to insure that your WinScry software only generate an Alert email when a) something is genuinely wrong and b) someone is in a position to respond.


The types of alerts you create at any WinScry Monitor Installation will be determined by several key factors:


How many installations will you be monitoring in total? Using the System Status Report as an example, it's a great tool to get a status report from your installations daily IF you are only monitoring a few installations. If you have a WinScry subscription for dozens or hundreds of monitors and they will all be delivering to the same email recipient(s), is it practical to receive dozens or hundreds of status report emails every day? If this is the case consider using the On Demand option in your system status report.

Is the process being supported (and the alerts that prompt support) a 24/7 operation? Let's say for the sake of argument that you are using WinScry to monitor a telephone call center operation on a clients' server and you will be monitoring files and folders, database queries, etc with Conditional Alerts. If the call center is only open from 8 AM to 5 PM, then is it to your benefit to have WinScry generate email alerts in the middle of the night when there's no one at the client site to actually assist? For example, if your alerts are configured to generate an alert email AND to send followup emails every 2 hours and an alert is Triggered at 5:30 PM (after everyone at the client has left), the WinScry software might generate 9 or 10 email alerts before the client office opens at 8 AM the next morning. If you're only monitoring 1 or 2 clients this might not be bad, but if you're monitoring 200 clients and this happens on half of them, that could be 1000 alert emails generated in the overnight. Remember that the first rule when setting up any remote system monitor is Don't SPAM Yourself. Use Hibernation Settings to intelligently limit the ability of the WinScry Client to generate email alerts.

As an extension of the previous item. Is YOUR support a 24/7 operation? The same argument applies here, even if the client operation runs 24/7, IF your support operation only works from 8 AM to 5 PM then is it to your benefit to have alert emails delivered when the email recipient(s) configured in the Management Console for that installation are not available to respond to them? Here again use Hibernation Settings to make sure you don't get email alerts when they aren't needed.