System features
SiUX -- web site monitoring service
HTTP control
Most users cannot see difference within web services and internet. For major part of internet users internet means web pages. Thats why SiUX implemented really deep checking of HTTP services. SiUX can check not only if the HTTP service is running but can also measure a lot of qualitative particulars. For example how fast was the server reached, how fast server answers the response, how long did it take to download the response, size of the response etc..
How SiUX does that?
Client can simply set a test in the client website. Client just sets the URL to be checked and set the check interval. Thats all. After this input SiUX starts monitoring the given source and saves the results.
Form the measured values can SiUX evaluate several essential qualitative parameters of the provided service. These essential parameters are connect time - time spent to establish connection with server, read time - time needed to read the response from server, size - size of the response from server, body size - real size of the page read from server. These information can show you how us how is the application running and if response time grows or the size of the page dither we can predict some troubles with application and can fix the troubles before total collapse.
SMTP, POP3, IMAP control
Second popular service of the internet users is email. In this direction SiUX also provides specialized functionality especially for this service. As in HTTP part also here it can do more than just check the server accessibility. It can try to log on the server and try to send or check the email. For more complex installations we can also provide tests to check the speed of email message delivery.
Server accessibility, trace monitoring
in this part of system we leave high level of application services and we reach low level IP network layer which is also SiUXs favorite one. While we monitor our services running on different server it is good to know if the server ar reachable and online. Then we can decide if the problem is based only in the application or whole server is experiencing some troubles with hardware or whatever can happen. These low-level accessibility checks are done by ICMP protocol, better known as ping service that say if and how fast is the server reachable.
Similar monitoring offers traceroute module. As ping knows only if the server is reachable, traceroute watches the route, which the information must go to get there. This information is also important as the change of this trace usually means some troubles with the connection.
Generic IP service check
Each service provided on the internet uses its server with dedicated IP address or addresses and services on this server are identified by its specific communication port which is used to communicate with that service. Due to this fact we can simply check is any service is running. This check is not deep inspection of the service like in http, but still can be really useful information to monitor.
Opened ports monitoring (port scan)
As we mentioned in the above paragraph, each service on the internet communicates on its specific port on some IP address. There are no perfect application as they are only human written and each application opened to the internet is potentional risk and in some cases can be used by some hacker to break in to the system. Thats the reason why administrators prevent such communication by firewalls and other techniques. SiUX can be used to save the current state of the opened ports and watch this state for changes because any unwanted change can mean that some awful things happens, some firewall fails or there is someone already inside the system opening a backdoor for other activity. SiUX will watch the opened ports and report any change that happens. Due to high sensitivity of these techniques we offer this service only in a bit restricted mode and we moderate usage of this service.
User defined control
As the SiUX system is highly scalable and modular we can connect any type and any kind of testing to it. If client want to monitor his system in very specific way we can develop special testing module for his system. Thats usually modules simulating browsing through the website using some searches or logging in some restricted area to assure that all the application is going fine and there are no problems.
Modules
- http (WWW)
- ping (availability server)
- smtp, pop3 a imap (email)
- traceroute (location guideway)
- portscan (location port)
Practically
Example: interval 1 min.
| time | checkpoint | action |
|---|---|---|
| 10:00:05 | sitel | 200 OK |
| 10:01:10 | dial telecom | 200 OK |
| 10:02:15 | promedia | 610 Read timeout (no send) |
| 10:03:20 | superhosting | 200 OK |
| 10:04:25 | vnet.sk | 200 OK |
| 10:05:30 | ignum | 620 Connect error |
| 10:06:35 | gts | 610 Read error (send e-mail) |
| 10:07:40 | master interne | 610 Read error (send SMS) |
| 10:08:45 | sitel | 200 OK |