| 1 |
< |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
| 2 |
< |
|
| 3 |
< |
<!-- |
| 4 |
< |
index.shtml |
| 5 |
< |
Created by pjm2 25/05/2001 |
| 6 |
< |
Last edited 25/05/2001 |
| 7 |
< |
--> |
| 8 |
< |
|
| 9 |
< |
<html> |
| 10 |
< |
|
| 11 |
< |
<head> |
| 12 |
< |
<title>i-scream screenshots / overview</title> |
| 13 |
< |
<meta name="description" content="The i-scream central monitoring system runs distributed on Unix, Linux and Windows NT/2000 servers."> |
| 14 |
< |
<meta name="keywords" content="i-scream, screenshots, distributed, central, monitoring, system, project, unix, linux, nt, 2000, server, alert, email, winhost, ihost, conient"> |
| 15 |
< |
<meta name="generator" content="Microsoft FrontPage 4.0"> |
| 16 |
< |
</head> |
| 17 |
< |
|
| 18 |
< |
<basefont face="arial, sans-serif" size="2"> |
| 19 |
< |
<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066"> |
| 20 |
< |
|
| 21 |
< |
<table border="0" cellpadding="2" cellspacing="2"> |
| 22 |
< |
<tr> |
| 23 |
< |
<td valign="top"> |
| 24 |
< |
<!--#include virtual="../left.inc" --> |
| 25 |
< |
</td> |
| 26 |
< |
<td valign="top"> |
| 27 |
< |
<!--#include virtual="../title.inc" --> |
| 28 |
< |
<font size="2"> |
| 29 |
< |
|
| 30 |
< |
|
| 31 |
< |
|
| 32 |
< |
|
| 33 |
< |
<div align="center"> |
| 34 |
< |
<center> |
| 35 |
< |
<table border="0" cellspacing="10" width="500" cellpadding="0"> |
| 36 |
< |
<tr> |
| 37 |
< |
<td valign="top" colspan="2"> |
| 38 |
< |
<h1 align="center"><font face="Arial" color="#000066">i-scream |
| 39 |
< |
screenshots</font></h1> |
| 40 |
< |
<h3 align="center"><font face="Arial" color="#000066">(or the 5 minute |
| 41 |
< |
tour)</font></h3> |
| 42 |
< |
</center> |
| 43 |
< |
<p><font size="2" face="Arial">This page provides a sequence of |
| 44 |
< |
screenshots to help you to gain a better understanding of the i-scream |
| 45 |
< |
distributed central monitoring system and how it may be applied in |
| 46 |
< |
networked environments. Click on the thumbnails to view the full |
| 47 |
< |
size screenshots.</font></p> |
| 48 |
< |
<p> </td> |
| 49 |
< |
</tr> |
| 50 |
< |
<center> |
| 51 |
< |
<tr> |
| 52 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/reports-main.gif"><img border="0" src="screenshots/thumbnail-reports-main.gif" alt="click to enlarge!" width="100" height="77"></a></font> |
| 53 |
< |
<p> </td> |
| 54 |
< |
<td valign="top"><font color="#000066"><font face="Arial"><b>Reports Centre</b></font><b><font face="Arial"> |
| 55 |
< |
(Web)</font></b></font><font size="2" face="Arial"><br> |
| 56 |
< |
The i-scream reports centre provides a central access point to all |
| 57 |
< |
web-based reports that are provided by the i-scream system. Reports |
| 58 |
< |
are available to display information about the current status of an |
| 59 |
< |
individual machine and any alerts pertaining to either an individual |
| 60 |
< |
machine, or a summary of alerts for all machines. Historical |
| 61 |
< |
information about monitored machines may also be accessed from this point.</font> |
| 62 |
< |
<p> </td> |
| 63 |
< |
</tr> |
| 64 |
< |
<tr> |
| 65 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/reports-raptor-latest-misc.gif"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" alt="click to enlarge!" width="100" height="104"></a></font> |
| 66 |
< |
<p> </td> |
| 67 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Latest Information |
| 68 |
< |
(Web)</font></b><font size="2" face="Arial"><br> |
| 69 |
< |
Here we are viewing the latest information provided by a host. Bars |
| 70 |
< |
are used to represent values such as disk space and free memory as this |
| 71 |
< |
makes it easier to spot casual problems. The small graph icons link |
| 72 |
< |
to historical reports of each field for the previous day. The choice |
| 73 |
< |
of fields to display on this page is stored in a separate configuration |
| 74 |
< |
file.</font> |
| 75 |
< |
<p> </td> |
| 76 |
< |
</tr> |
| 77 |
< |
<tr> |
| 78 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/conient-main.gif"><img border="0" src="screenshots/thumbnail-conient-main.gif" alt="click to enlarge!" width="100" height="110"></a></font> |
| 79 |
< |
<p> </td> |
| 80 |
< |
<td valign="top"><b><font face="Arial"><font color="#000066">Conient (Multiplatform |
| 81 |
< |
real-time client)</font><br> |
| 82 |
< |
</font></b><font size="2" face="Arial">Conient is a real-time client that |
| 83 |
< |
can hook into an i-scream server to allow the user to view host |
| 84 |
< |
information as it passes through the server. The client displays |
| 85 |
< |
information provided by the hosts as well as the results of service checks |
| 86 |
< |
performed by the server on each host (eg FTP, Telnet, etc). Conient |
| 87 |
< |
is written in Java and can thus be run on most operating systems.</font> |
| 88 |
< |
<p> </td> |
| 89 |
< |
</tr> |
| 90 |
< |
<tr> |
| 91 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/conient-platform-info.gif"><img border="0" src="screenshots/thumbnail-conient-platform-info.gif" alt="click to enlarge!" width="100" height="59"></a></font> |
| 92 |
< |
<p> </td> |
| 93 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Conient (Viewing |
| 94 |
< |
extra data)</font></b><font size="2" face="Arial"><br> |
| 95 |
< |
Less important host information may be viewed in a seperate window to |
| 96 |
< |
avoid clutter in Conient's display. Details of the protocol for |
| 97 |
< |
host-to-server communications are freely available to developers. |
| 98 |
< |
The protocol itself is extensible and client programs such as Conient |
| 99 |
< |
display even unrecognised data from modified host programs.</font> |
| 100 |
< |
<p> </td> |
| 101 |
< |
</tr> |
| 102 |
< |
<tr> |
| 103 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/conient-config.gif"><img border="0" src="screenshots/thumbnail-conient-config.gif" alt="click to enlarge!" width="100" height="48"></a></font> |
| 104 |
< |
<p> </td> |
| 105 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Conient |
| 106 |
< |
(Configuration)</font></b><font size="2" face="Arial"><br> |
| 107 |
< |
Conient is fully configurable from within the program itself. |
| 108 |
< |
Multiple configurations may be saved. Conient can also be configured |
| 109 |
< |
to connect to a server through a firewall via an SSH tunnel or suchlike.</font> |
| 110 |
< |
<p> </td> |
| 111 |
< |
</tr> |
| 112 |
< |
<tr> |
| 113 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/ihost-main.gif"><img border="0" src="screenshots/thumbnail-ihost-main.gif" alt="click to enlarge!" width="100" height="51"></a></font> |
| 114 |
< |
<p> </td> |
| 115 |
< |
<td valign="top"><b><font face="Arial" color="#000066">ihost (Unix/Linux |
| 116 |
< |
host)</font></b><font size="2" face="Arial"><br> |
| 117 |
< |
The ihost is currently the main Unix/Linux/FreeBSD host application for |
| 118 |
< |
i-scream. ihost is centrally configured by the server it connects to |
| 119 |
< |
and periodically sends information about the machine on which it is |
| 120 |
< |
running. The ihost is written in Perl, so can be easily altered to |
| 121 |
< |
send extra information to your i-scream server.</font> |
| 122 |
< |
<p> </td> |
| 123 |
< |
</tr> |
| 124 |
< |
<tr> |
| 125 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/winhost-main.gif"><img border="0" src="screenshots/thumbnail-winhost-main.gif" alt="click to enlarge!" width="100" height="62"></a></font> |
| 126 |
< |
<p> </td> |
| 127 |
< |
<td valign="top"><b><font face="Arial" color="#000066">WinHost (Windows |
| 128 |
< |
host)</font></b><font size="2" face="Arial"><br> |
| 129 |
< |
The WinHost is similar in concept to the ihost, however, this one runs on |
| 130 |
< |
Windows NT/2000 servers. Again, the configuration is dynamically |
| 131 |
< |
obtained from the server. The WinHost is typically only present in |
| 132 |
< |
the Windows system tray. Double clicking on the system tray icon |
| 133 |
< |
will bring up a small window that allows data to be viewed and to force |
| 134 |
< |
reconfiguration with the server.</font> |
| 135 |
< |
<p> </td> |
| 136 |
< |
</tr> |
| 137 |
< |
<tr> |
| 138 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/alerter-email.gif"><img border="0" src="screenshots/thumbnail-alerter-email.gif" alt="click to enlarge!" width="100" height="74"></a></font> |
| 139 |
< |
<p> </td> |
| 140 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Alerts (Email)</font></b><font size="2" face="Arial"><br> |
| 141 |
< |
The i-scream server includes many alerting mechanisms. Simple email |
| 142 |
< |
alerts may be sent out if desired. Alert levels and frequencies may |
| 143 |
< |
be configured for the server. This screenshot shows the format of a |
| 144 |
< |
typical alert; the contents of which are of course configurable.</font> |
| 145 |
< |
<p> </td> |
| 146 |
< |
</tr> |
| 147 |
< |
<tr> |
| 148 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/alerter-irc.gif"><img border="0" src="screenshots/thumbnail-alerter-irc.gif" alt="click to enlarge!" width="100" height="95"></a></font> |
| 149 |
< |
<p> </td> |
| 150 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Alerts (IRC bot)</font></b><font size="2" face="Arial"><br> |
| 151 |
< |
Another i-scream alerter comes in the form of an interactive IRC bot. |
| 152 |
< |
This may reside in an IRC (Internet relay chat) channel and broadcasts |
| 153 |
< |
alerts if told to do so. This screenshot shows a typical interaction |
| 154 |
< |
with a user in the "Bersirc" IRC client.</font> |
| 155 |
< |
<p> </td> |
| 156 |
< |
</tr> |
| 157 |
< |
<tr> |
| 158 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/reports-alerts-all.gif"><img border="0" src="screenshots/thumbnail-reports-alerts-all.gif" alt="click to enlarge!" width="100" height="96"></a></font> |
| 159 |
< |
<p> </td> |
| 160 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Alerts (Web page)</font></b><font size="2" face="Arial"><br> |
| 161 |
< |
Individual alerts and a summary of all alerts raised by the i-scream |
| 162 |
< |
server may be viewed on the alerts web pages. These show the |
| 163 |
< |
different levels of alerts in configurable colours and provides specific |
| 164 |
< |
details about the alerts being raised for each machine.</font> |
| 165 |
< |
<p> </td> |
| 166 |
< |
</tr> |
| 167 |
< |
<tr> |
| 168 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/reports-public-autoscroll.gif"><img border="0" src="screenshots/thumbnail-reports-public-autoscroll.gif" alt="click to enlarge!" width="100" height="78"></a></font> |
| 169 |
< |
<p> </td> |
| 170 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Alerts (Public |
| 171 |
< |
helpdesk display)</font><font size="2" face="Arial"><br> |
| 172 |
< |
</font></b><font size="2" face="Arial">The reports centre also provides a |
| 173 |
< |
page that may be useful in configuring non-interactive public displays of |
| 174 |
< |
alerts. These displays automatically refresh the page periodically |
| 175 |
< |
and supported web browsers may also automatically scroll the page to allow |
| 176 |
< |
a large font to be employed for easier reading from a distance.</font> |
| 177 |
< |
<p> </td> |
| 178 |
< |
</tr> |
| 179 |
< |
<tr> |
| 180 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/conient-queues.gif"><img border="0" src="screenshots/thumbnail-conient-queues.gif" alt="click to enlarge!" width="100" height="159"></a></font> |
| 181 |
< |
<p> </td> |
| 182 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Conient (Server queue |
| 183 |
< |
monitoring)</font><font size="2" face="Arial"><br> |
| 184 |
< |
</font></b><font size="2" face="Arial">The Conient client may also be used |
| 185 |
< |
to monitor information about the i-scream server itself. Here we are |
| 186 |
< |
viewing the status of the internal queues within the server. This |
| 187 |
< |
shows that the server is performing healthily and that there are no |
| 188 |
< |
bottlenecks. </font></td> |
| 189 |
< |
</tr> |
| 190 |
< |
<tr> |
| 191 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/reports-raptor-load15.gif"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" alt="click to enlarge!" width="100" height="107"></a></font> |
| 192 |
< |
<p> </td> |
| 193 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Historical reports |
| 194 |
< |
(Web)</font><font size="2" face="Arial"><br> |
| 195 |
< |
</font></b><font size="2" face="Arial">Historical information is collated |
| 196 |
< |
by the i-scream server into (typically) a MySQL database. A separate |
| 197 |
< |
program is used to produce the historical web reports These may be browsed |
| 198 |
< |
via this web-based interface (see screenshot). The reports to be |
| 199 |
< |
generated for each machine and the size of the page are of course |
| 200 |
< |
configurable.</font> |
| 201 |
< |
<p> </td> |
| 202 |
< |
</tr> |
| 203 |
< |
<tr> |
| 204 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/reports-raptor-users.gif"><img border="0" src="screenshots/thumbnail-reports-raptor-users.gif" alt="click to enlarge!" width="100" height="96"></a></font> |
| 205 |
< |
<p> </td> |
| 206 |
< |
<td valign="top"><b><font face="Arial" color="#000066">Historical reports |
| 207 |
< |
(Metadata)</font><font size="2" face="Arial"><br> |
| 208 |
< |
</font></b><font size="2" face="Arial">The historical report generation |
| 209 |
< |
also produces a number of other files that may be useful for third party |
| 210 |
< |
analysis tools. The chart itself is written as a GIF image, as well |
| 211 |
< |
as a small file suitable for including on PHP pages that specifies the |
| 212 |
< |
minimum and maximum values during the 24 hour period. A file |
| 213 |
< |
containing the raw plot data is also produced to enable the use of third |
| 214 |
< |
party on-the-fly plotting tools.</font> |
| 215 |
< |
<p> </td> |
| 216 |
< |
</tr> |
| 217 |
< |
<tr> |
| 218 |
< |
<td valign="top" width="100"><font size="2" face="Arial"><a href="screenshots/server-main.gif"><img border="0" src="screenshots/thumbnail-server-main.gif" alt="click to enlarge!" width="100" height="100"></a></font> |
| 219 |
< |
<p> </td> |
| 220 |
< |
<td valign="top"><b><font face="Arial" color="#000066">The i-scream server</font><font size="2" face="Arial"><br> |
| 221 |
< |
</font></b><font size="2" face="Arial">The server is distributed and may |
| 222 |
< |
therefore have multiple points of data entry and run on more than one |
| 223 |
< |
machine. This helps to reduce the amount of host traffic over large |
| 224 |
< |
networks and reduces potential bottlenecks. The server is written in |
| 225 |
< |
Java to allow it to run on most operating systems. This exciting |
| 226 |
< |
screenshot shows the i-scream server running ;-)</font> |
| 227 |
< |
<p> </td> |
| 228 |
< |
</tr> |
| 229 |
< |
</table> |
| 230 |
< |
</center> |
| 231 |
< |
</div> |
| 232 |
< |
|
| 233 |
< |
|
| 234 |
< |
|
| 235 |
< |
<!--#include virtual="../bottom.inc" --> |
| 236 |
< |
</td> |
| 237 |
< |
</tr> |
| 238 |
< |
</table> |
| 239 |
< |
|
| 240 |
< |
</body> |
| 1 |
> |
<!--#include virtual="/doctype.inc" --> |
| 2 |
> |
<head> |
| 3 |
> |
<title> |
| 4 |
> |
CMS Screen Shots |
| 5 |
> |
</title><!--#include virtual="/style.inc" --> |
| 6 |
> |
</head> |
| 7 |
> |
<body> |
| 8 |
> |
<div id="container"> |
| 9 |
> |
<div id="main"> |
| 10 |
> |
<!--#include virtual="/header.inc" --> |
| 11 |
> |
<div id="contents"> |
| 12 |
> |
<h1 class="top"> |
| 13 |
> |
CMS Screen Shots |
| 14 |
> |
</h1> |
| 15 |
> |
<h2> |
| 16 |
> |
i-scream screenshots |
| 17 |
> |
</h2> |
| 18 |
> |
<p> |
| 19 |
> |
This page provides a sequence of screenshots to help you to |
| 20 |
> |
gain a better understanding of the i-scream distributed |
| 21 |
> |
central monitoring system and how it may be applied in |
| 22 |
> |
networked environments. Click on the thumbnails to |
| 23 |
> |
view the full size screenshots. |
| 24 |
> |
</p> |
| 25 |
> |
<p> |
| 26 |
> |
<b>Reports Centre (Web)</b><br /> |
| 27 |
> |
The i-scream reports centre provides a central access point |
| 28 |
> |
to all web-based reports that are provided by the i-scream |
| 29 |
> |
system. Reports are available to display information |
| 30 |
> |
about the current status of an individual machine and any |
| 31 |
> |
alerts pertaining to either an individual machine, or a |
| 32 |
> |
summary of alerts for all machines. Historical |
| 33 |
> |
information about monitored machines may also be accessed |
| 34 |
> |
from this point. |
| 35 |
> |
</p> |
| 36 |
> |
<p> |
| 37 |
> |
<a href="reports-main.gif"> |
| 38 |
> |
<img src="thumbnail-reports-main.gif" alt="click to enlarge!" width="100" height="77" /> |
| 39 |
> |
</a> |
| 40 |
> |
</p> |
| 41 |
> |
<p> |
| 42 |
> |
<b>Latest Information (Web)</b><br /> |
| 43 |
> |
Here we are viewing the latest information provided by a |
| 44 |
> |
host. Bars are used to represent values such as disk |
| 45 |
> |
space and free memory as this makes it easier to spot casual |
| 46 |
> |
problems. The small graph icons link to historical |
| 47 |
> |
reports of each field for the previous day. The choice |
| 48 |
> |
of fields to display on this page is stored in a separate |
| 49 |
> |
configuration file. |
| 50 |
> |
</p> |
| 51 |
> |
<p> |
| 52 |
> |
<a href="reports-raptor-latest-misc.gif"> |
| 53 |
> |
<img src="thumbnail-reports-raptor-latest-misc.gif" alt="click to enlarge!" width="100" height="104" /> |
| 54 |
> |
</a> |
| 55 |
> |
</p> |
| 56 |
> |
<p> |
| 57 |
> |
<b>Conient (Multiplatform real-time client)</b><br /> |
| 58 |
> |
Conient is a real-time client |
| 59 |
> |
that can hook into an i-scream server to allow the user to |
| 60 |
> |
view host information as it passes through the server. |
| 61 |
> |
The client displays information provided by the hosts as well |
| 62 |
> |
as the results of service checks performed by the server on |
| 63 |
> |
each host (eg FTP, Telnet, etc). Conient is written in |
| 64 |
> |
Java and can thus be run on most operating systems. |
| 65 |
> |
</p> |
| 66 |
> |
<p> |
| 67 |
> |
<a href="conient-main.gif"> |
| 68 |
> |
<img src="thumbnail-conient-main.gif" alt="click to enlarge!" width="100" height="110" /> |
| 69 |
> |
</a> |
| 70 |
> |
</p> |
| 71 |
> |
<p> |
| 72 |
> |
<b>Conient (Viewing extra data)</b><br /> |
| 73 |
> |
Less important host information may be viewed in a seperate |
| 74 |
> |
window to avoid clutter in Conient's display. Details |
| 75 |
> |
of the protocol for host-to-server communications are freely |
| 76 |
> |
available to developers. The protocol itself is |
| 77 |
> |
extensible and client programs such as Conient display even |
| 78 |
> |
unrecognised data from modified host programs. |
| 79 |
> |
</p> |
| 80 |
> |
<p> |
| 81 |
> |
<a href="conient-platform-info.gif"> |
| 82 |
> |
<img src="thumbnail-conient-platform-info.gif" alt="click to enlarge!" width="100" height="59" /> |
| 83 |
> |
</a> |
| 84 |
> |
</p> |
| 85 |
> |
<p> |
| 86 |
> |
<b>Conient (Configuration)</b><br /> |
| 87 |
> |
Conient is fully configurable from within the program |
| 88 |
> |
itself. Multiple configurations may be saved. |
| 89 |
> |
Conient can also be configured to connect to a server through |
| 90 |
> |
a firewall via an SSH tunnel or suchlike. |
| 91 |
> |
</p> |
| 92 |
> |
<p> |
| 93 |
> |
<a href="conient-config.gif"> |
| 94 |
> |
<img src="thumbnail-conient-config.gif" alt="click to enlarge!" width="100" height="48" /> |
| 95 |
> |
</a> |
| 96 |
> |
</p> |
| 97 |
> |
<p> |
| 98 |
> |
<b>ihost (Unix/Linux host)</b><br /> |
| 99 |
> |
The ihost is currently the main Unix/Linux/FreeBSD host |
| 100 |
> |
application for i-scream. ihost is centrally configured |
| 101 |
> |
by the server it connects to and periodically sends |
| 102 |
> |
information about the machine on which it is running. |
| 103 |
> |
The ihost is written in Perl, so can be easily altered to |
| 104 |
> |
send extra information to your i-scream server. |
| 105 |
> |
</p> |
| 106 |
> |
<p> |
| 107 |
> |
<a href="ihost-main.gif"> |
| 108 |
> |
<img src="thumbnail-ihost-main.gif" alt="click to enlarge!" width="100" height="51" /> |
| 109 |
> |
</a> |
| 110 |
> |
</p> |
| 111 |
> |
<p> |
| 112 |
> |
<b>WinHost (Windows host)</b><br /> |
| 113 |
> |
The WinHost is similar in concept to the ihost, however, this |
| 114 |
> |
one runs on Windows NT/2000 servers. Again, the |
| 115 |
> |
configuration is dynamically obtained from the server. |
| 116 |
> |
The WinHost is typically only present in the Windows system |
| 117 |
> |
tray. Double clicking on the system tray icon will |
| 118 |
> |
bring up a small window that allows data to be viewed and to |
| 119 |
> |
force reconfiguration with the server. |
| 120 |
> |
</p> |
| 121 |
> |
<p> |
| 122 |
> |
<a href="winhost-main.gif"> |
| 123 |
> |
<img src="thumbnail-winhost-main.gif" alt="click to enlarge!" width="100" height="62" /> |
| 124 |
> |
</a> |
| 125 |
> |
</p> |
| 126 |
> |
<p> |
| 127 |
> |
<b>Alerts (Email)</b><br /> |
| 128 |
> |
The i-scream server includes many alerting mechanisms. |
| 129 |
> |
Simple email alerts may be sent out if desired. Alert |
| 130 |
> |
levels and frequencies may be configured for the |
| 131 |
> |
server. This screenshot shows the format of a typical |
| 132 |
> |
alert; the contents of which are of course configurable. |
| 133 |
> |
</p> |
| 134 |
> |
<p> |
| 135 |
> |
<a href="alerter-email.gif"> |
| 136 |
> |
<img src="thumbnail-alerter-email.gif" alt="click to enlarge!" width="100" height="74" /> |
| 137 |
> |
</a> |
| 138 |
> |
</p> |
| 139 |
> |
<p> |
| 140 |
> |
<b>Alerts (IRC bot)</b><br /> |
| 141 |
> |
Another i-scream alerter comes in the form of an interactive |
| 142 |
> |
IRC bot. This may reside in an IRC (Internet relay |
| 143 |
> |
chat) channel and broadcasts alerts if told to do so. |
| 144 |
> |
This screenshot shows a typical interaction with a user in |
| 145 |
> |
the "Bersirc" IRC client. |
| 146 |
> |
</p> |
| 147 |
> |
<p> |
| 148 |
> |
<a href="alerter-irc.gif"> |
| 149 |
> |
<img src="thumbnail-alerter-irc.gif" alt="click to enlarge!" width="100" height="95" /> |
| 150 |
> |
</a> |
| 151 |
> |
</p> |
| 152 |
> |
<p> |
| 153 |
> |
<b>Alerts (Web page)</b><br /> |
| 154 |
> |
Individual alerts and a summary of all alerts raised by the |
| 155 |
> |
i-scream server may be viewed on the alerts web pages. |
| 156 |
> |
These show the different levels of alerts in configurable |
| 157 |
> |
colours and provides specific details about the alerts being |
| 158 |
> |
raised for each machine. |
| 159 |
> |
</p> |
| 160 |
> |
<p> |
| 161 |
> |
<a href="reports-alerts-all.gif"> |
| 162 |
> |
<img src="thumbnail-reports-alerts-all.gif" alt="click to enlarge!" width="100" height="96" /> |
| 163 |
> |
</a> |
| 164 |
> |
</p> |
| 165 |
> |
<p> |
| 166 |
> |
<b>Alerts (Public helpdesk display)</b><br /> |
| 167 |
> |
The reports centre also |
| 168 |
> |
provides a page that may be useful in configuring |
| 169 |
> |
non-interactive public displays of alerts. These |
| 170 |
> |
displays automatically refresh the page periodically and |
| 171 |
> |
supported web browsers may also automatically scroll the page |
| 172 |
> |
to allow a large font to be employed for easier reading from |
| 173 |
> |
a distance. |
| 174 |
> |
</p> |
| 175 |
> |
<p> |
| 176 |
> |
<a href="reports-public-autoscroll.gif"> |
| 177 |
> |
<img src="thumbnail-reports-public-autoscroll.gif" alt="click to enlarge!" width="100" height="78" /> |
| 178 |
> |
</a> |
| 179 |
> |
</p> |
| 180 |
> |
<p> |
| 181 |
> |
<b>Conient (Server queue monitoring)</b><br /> |
| 182 |
> |
The Conient client may also be used to |
| 183 |
> |
monitor information about the i-scream server itself. |
| 184 |
> |
Here we are viewing the status of the internal queues within |
| 185 |
> |
the server. This shows that the server is performing |
| 186 |
> |
healthily and that there are no bottlenecks. |
| 187 |
> |
</p> |
| 188 |
> |
<p> |
| 189 |
> |
<a href="conient-queues.gif"> |
| 190 |
> |
<img src="thumbnail-conient-queues.gif" alt="click to enlarge!" width="100" height="159" /> |
| 191 |
> |
</a> |
| 192 |
> |
</p> |
| 193 |
> |
<p> |
| 194 |
> |
<b>Historical reports (Web)</b><br /> |
| 195 |
> |
Historical information is collated by the |
| 196 |
> |
i-scream server into (typically) a MySQL database. A |
| 197 |
> |
separate program is used to produce the historical web |
| 198 |
> |
reports These may be browsed via this web-based interface |
| 199 |
> |
(see screenshot). The reports to be generated for each |
| 200 |
> |
machine and the size of the page are of course configurable. |
| 201 |
> |
</p> |
| 202 |
> |
<p> |
| 203 |
> |
<a href="reports-raptor-load15.gif"> |
| 204 |
> |
<img src="thumbnail-reports-raptor-load15.gif" alt="click to enlarge!" width="100" height="107" /> |
| 205 |
> |
</a> |
| 206 |
> |
</p> |
| 207 |
> |
<p> |
| 208 |
> |
<b>Historical reports (Metadata)</b><br /> |
| 209 |
> |
The historical report generation also |
| 210 |
> |
produces a number of other files that may be useful for third |
| 211 |
> |
party analysis tools. The chart itself is written as a |
| 212 |
> |
GIF image, as well as a small file suitable for including on |
| 213 |
> |
PHP pages that specifies the minimum and maximum values |
| 214 |
> |
during the 24 hour period. A file containing the raw |
| 215 |
> |
plot data is also produced to enable the use of third party |
| 216 |
> |
on-the-fly plotting tools. |
| 217 |
> |
</p> |
| 218 |
> |
<p> |
| 219 |
> |
<a href="reports-raptor-users.gif"> |
| 220 |
> |
<img src="thumbnail-reports-raptor-users.gif" alt="click to enlarge!" width="100" height="96" /> |
| 221 |
> |
</a> |
| 222 |
> |
</p> |
| 223 |
> |
<p> |
| 224 |
> |
<b>The i-scream server</b><br /> |
| 225 |
> |
The server is distributed and may therefore have multiple |
| 226 |
> |
points of data entry and run on more than one machine. |
| 227 |
> |
This helps to reduce the amount of host traffic over large |
| 228 |
> |
networks and reduces potential bottlenecks. The server |
| 229 |
> |
is written in Java to allow it to run on most operating |
| 230 |
> |
systems. This exciting screenshot shows the i-scream |
| 231 |
> |
server running ;-) |
| 232 |
> |
</p> |
| 233 |
> |
<p> |
| 234 |
> |
<a href="server-main.gif"> |
| 235 |
> |
<img src="thumbnail-server-main.gif" alt="click to enlarge!" width="100" height="100" /> |
| 236 |
> |
</a> |
| 237 |
> |
</p> |
| 238 |
> |
</div> |
| 239 |
> |
<!--#include virtual="/footer.inc" --> |
| 240 |
> |
</div> |
| 241 |
> |
<!--#include virtual="/menu.inc" --> |
| 242 |
> |
</div> |
| 243 |
> |
</body> |
| 244 |
|
</html> |
