| 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> |