This project is read-only.

PolyMon RC3 Screenshots

Monitoring and Reporting

PolyMon Dashboard: Main PolyMon monitoring dashboard, Tile View

PolyMon Dashboard: Main PolyMon monitoring dashboard, List View

PolyMon All Monitors: This view provides different views of all monitors defined in PolyMon and their current status. Unlike the Dashboard which allows any grouping of any monitors (including displaying the same monitor in multiple groups), this view is essentially just a list of all monitors and contains three views: Icon, Tile and Details.

PolyMon Alerts: Lists any current alerts (failures and warnings).

Historical Analysis: Summary of various counter data and status data for a specified Monitor

Historical Analysis: Daily aggregated data for specified Monitor

Historical Analysis: Data corresponding to the charts displayed on the Daily historical report. Data views can be generated for any of the Daily, Weekly, MOnthly and Custom reports.

Historical Analysis: Weekly aggregated data for specified Monitor

Historical Analysis: Monthly aggregated data for specified Monitor

Historical Analysis: Custom aggregated data for specified monitor. Data can be viewed at the raw level (each individual monitoring point, or aggregated over any span of time specified in minutes, hours, days)

Event History Report: This report is used to view all events (filtered by status) that occurred during a specified time period.

System Health Report: This report is used to see the % Uptime for all monitors (and optionally Lifetime % Uptime) during a specified time period.

Monitor Setup

Monitor Editor: All Monitor definitions are maintained via the Monitor Editor screen.

Monitor Editor: Settings tab that displays the plug-in Monitor Editors and is used to specify monitor type specific information such as threshold values, what to monitor, etc.

Monitor Editor: Notification Template tab used to specify what information the email notifications will contain. Standard merge fields include Monitor Name, Type, Status, Date, etc.

Monitor Editor: Notification Rules tab used to specify how notifications are generated. Notifications can be generated based on failures, warnings, consecutive failures/warnings, etc.

Monitor Editor: Operators tab used to specify which operators are associated with Monitor (and hence who will receive notifications based on notification rules)

Monitor Editor: Retention Schedule tab is used to specify how long historical data will be retained for the monitor. Data is stored at the raw (individual event) level, as well as at multiple aggregation levels (daily, weekly, monthly). This retention schedule specifies how much data to retain for each of these aggregation levels.

PolyMon Settings

General Settings - System: SMTP settings, etc.

General Settings - Retention Scheme: Default retention scheme used to determine how long to keep counter and status data, at the raw data level and at daily, weekly and monthly aggregate levels.

General Settings - User Settings: User specific settings such as Audio Alerts, etc.

Operators: Used to define operators, unavailable times (times when they will not receive notifications), email address, etc.

Monitor Types: Polymon uses a plug-in type architecture for all monitors and their corresponding editors. New monitor types are registered here. A generic XML editor is provided in case the new Monitor does not have it's own editor plug-in.


PolyMon Executive: The PolyMon Executive is a windows service that handles monitoring and notifications. It can be started/stopped either in the Windows Services applet or directly from PolyMon Manager through this screen.

Last edited Mar 15, 2007 at 12:37 PM by fbaptiste, version 2


No comments yet.