ANormal "Green" color. All continuous ping detections (the number can be assigned by users , default : 3)received normal responses ,and package- lost rate (if needed to check ) is below limits(which can also be set) . BUnknown state "Yellow" color . If a ping detection does not receive normal response in standard time and the former state of the line is normal . When continuous ping detections do not receive normal responses , and the number exceed set number (default : 3 ), then the state will change into "Break ? CHigh package- lost rate "Red- Yellow " color .
Several ping detections do not receive normal responses in standard time . Thepackage- lost rate can be checked if necessary ,when package- lost rate exceeds standard(which can be set ),the color changes into Red- Yellow . DBreak / Down "Red" color . When all continuous ping detections do not receive normal responses in standardtime .
Simple Server Monitor Home Simple Server Monitor INCREASES UPTIME by instantly alerting you to server problems. FIX server issues before they become costly disasters! Simple Server Monitor is an affordable, powerful, and user. Test your ping. CA App Synthetic Monitor, the reliable web site monitoring service for server performance measurement. Free and paid remote web site and server monitoring. IPv6 now supported, give it a shot!
Break or Down" state .
Ping Monitor - Code. Project. Introduction.
This is yet another Ping Monitor utility written in VB. NET on . NET Framework 2.
It fulfills the need of steadily monitoring through a "PING" the status (the aliveness) of some PCs and servers on a network, keeping a history of each state transition (ON to OFF and viceversa) and visually highlighting the last status of each machine. This application is far from being a complete and sophisticated tool. I wrote it for a colleague who needed a starting point for a more advanced and customized tool implementation. One service, one database, one IUIn order to continuously monitor some machine, we need to have a monitoring EXE continuously runnning.
So, I decided to implement the "monitor engine" as a Windows Service application (taking advantage of unattended execution, automatic restart in case of power failure, and so on). This Ping. Monitor.
DNSstuff offers DNS tools, Network tools, Email tools, DNS reporting and IP information gathering. Explore monitoring products and free DNS tools at DNSstuff. Quick Ping Monitor 3.2.0 A enterprise graphic ip monitor tool. It is able to monitor thousands of IP equipments simultaneously and send message and mail when states of some equipments change, it could. IPHost Network Monitor offers admins server monitoring tool to test availability and performance of LAN and WAN servers, websites, appliances, URLs, and more. Ping Test website, server & network speed. Instant pingtest tool sends ICMP packets to the host measuring response time & errors from around the world. Yet another Ping Monitor utility written in VB.NET on.NET Framework 2.0; Author: Alberto Venditti; Updated:; Section: Internet / Network; Chapter: General Programming; Updated. Be notified via email, SMS, Skype, Hangout when your website is down. Monitor http availability, ping, port access, trace route, domain black list, db query results and snmp agent from many world regions.
Service simply has to: read from some configuration storage (such as a database table) the list of machines to be monitored (along with the monitoring frequency); execute the actual monitoring sending a "PING" to each machine configured as to be monitored; log the outcome of each "PING" somewhere. Other than a Windows Service for the monitoring and a database as a storage, we obviously need also a user interface (UI) to interact with the configuration and the log; that's why I created a simple Windows Form application (named Ping. Monitor) to accomplish these tasks: showing the last PING status of the monitored machines and editing the Ping. Monitor. Service configuration. I decided to use a SQL Server 2.
Quick Ping Monitor is a powerful graphic ip monitor tool. It is able to monitor the states of thousands of IP equipments simultaneously and send message when states of some equipments change! it could also adopt necessary.
The following are the two table schemas, expressed in T- SQL code, with some explanations. The configuration table. CREATE TABLE Host. List (. ID int IDENTITY(1,1) NOT NULL. Host nvarchar(5. 0) NULL. Is. Host char(1) NULL. Show. In. Monitor char(1) NULL.
Do. Ping char(1) NULL. Ping. Freq int NULL. IDparent int NULL. CONSTRAINT PK_Host. List PRIMARY KEY CLUSTERED (ID ASC). WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON PRIMARY. The Host. List table will contain the list of the machines to be monitored.
For each machine, it stores: the machine name with a unique ID (Host and ID fields), the frenquency of monitoring (Ping. Freq field, expressed in seconds), a flag indicating if the monitoring is currently activated (Do. Ping field) and a flag indicating if the specific machine has to be shown in the UI (Show. In. Monitor field). Being able to list a hierarchycal tree enables you to organize the machines to be monitored in groups and subgroups, the Host. List table supports the concept of parent- child node relationships (via the IDparent field) and the concept of "folder" tree nodes, that are intermediate nodes not corresponding to an host but simply being the parent of other nodes (for them, the Is.
Host flag is not set to "yes"). The user interface provided by the Ping. Monitor application allows you to visually edit the tree while directly modifying the underlying Host. List table (please, notice that the deletion of nodes and the addition of children nodes is allowed through the context menu on the tree).
The log table. CREATE TABLE Ping. Log (. Host varchar(5. NOT NULL. Status varchar(5) NOT NULL. Recording. Date datetime NOT NULL. CONSTRAINT [PK_Ping.
Log] PRIMARY KEY CLUSTERED (Host ASC, Status ASC. Recording. Date ASC). WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON PRIMARY. The Ping. Log table will contain an entry for each detected state transition (ON to OFF or viceversa) for each monitored machine during a monitored period of time. The Host field contains the name of the monitored machine, the Recording. Date field contains a timestamp of the recorded entry and the Status field simply contains the value "ON" or "OFF" (respectively indicating a successful and an unsuccessful "PING").
Some notes about the service. The Ping. Monitor. Service has been implemented on the standard Windows Service application template of Visual Studio 2.
Being a standard . NET Windows Service, it has to be installed through the installutil.
When started, the service reads its CONFIG file in order to retrieve: the connection string to the configuration database (see Conn. Str app. Setting) the configuration reloading frequency (see Reload.
Config. Frequency app. Setting): it indicates the number of seconds before reloading all the configuration parameters (this enables the service to adapt its behavior based on new settings in the Host. List table eventually modified by the user through the Ping. Monitor UI). To determine if it's time to "PING" a machine, the service simply looks at the total number of seconds passed after midnight and checks if this number is a multiple of the specific Ping. Freq for that host (notice that only status transitions are stored, not each status detection). If Current. Second Mod.
CInt(dr("Ping. Freq")) = 0. Then. Dim Is. Alive As. Boolean = Host. Is. Alive(dr("Host")). Dim Last. Status As. String = Host. Last. Status(dr("Host")).
If Last. Status = ""Or. Else _. (Last. Status = "ON"And. Not Is. Alive) Or. Else _. (Last. Status = "OFF"And Is.
Alive) Then. Store. Status. Transition(dr("Host"), Is. Alive). End. If. End. If. Notice that the polling interval in the Main.
Task() is currently set to 9. If the host list is very very big, the execution of the Try. Ping() method could be long enough to make the service miss some "PING" to some hosts (so please carefully configure the hosts list and the specific Ping. Freqs). The "PING" itself is done, in a very simple way, through the System. Net. Network. Information.
Ping class: Private. Function Host. Is. Alive(By. Val Host As. String) As. Boolean. Dim ping. Sender As.
New Ping. Dim reply As Ping. Reply. reply = ping. Sender. Send(Host). If reply. Status = IPStatus. Success Then. Return. True. Else. Return.
False. End. If. Catch ex As Exception. Return. False. End. Try. End. Function.
Some notes about the UIThe UI application is very simple; it consists of two forms: the monitoring form and the configuration form. The application needs a CONFIG file where the connection string to the support database is specified (see Conn.
Str app. Setting). The monitoring form is just a Data.
Grid. View populated by a query on the Ping. Log table; the query is designed to show only the last entry for each host having Show. In. Monitor='Y'. The refresh frequency for the Data. Grid. View can be specified in the Reload. Frequency app. Setting of the application configuration file. Entries with an "OFF" status are highlighted by simply implementing the Cell. Formatting() event handler: Private.
Sub dg. Monitor_Cell. Formatting(..). Handles dg. Monitor. Cell. Formatting.
Dim v As. Object = dg. Monitor. Rows(e. Row. Index). Cells("Status"). Value. If v Is. Not.
Nothing. And. Also v. To. String() = "OFF"Then. For. Each i As Data. Grid. View. Cell In dg. Monitor. Rows(e. Row.
Index). Cells. i. Style. Back. Color = Color. Orange. Next. End. If. End. Sub. The configuration form contains a treeview with a detail panel, shown when a host node is selected (see the first picture in the article). No special remarks needed on this. Just notice that the update of the underlying Host.
List table is done immediately after modifying values on the UI controls, through updates on the corresponding Data. Table suddenly written down by the Data. Adapter. Conclusions. As stated in the Introduction, this application is to be considered as a starting point for a more advanced and customized tool implementation. Its basic idea and implementation are intentionally very simple, hoping it can be useful for you in building something more complex. Downloads. Content of the downloadable ZIP (now available also in a C# version) for this article: the DBTables. Creation. sql file - contains the T- SQL scripts for creating support database tables on Microsoft SQL Server 2.
Ping. Monitor. Service folder - contains the Visual Studio 2. Ping. Monitor folder - contains the Visual Studio 2. UI Win. Form application. Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.