{"id":1474,"date":"2013-12-14T18:49:55","date_gmt":"2013-12-14T16:49:55","guid":{"rendered":"https:\/\/alax.info\/blog\/?p=1474"},"modified":"2013-12-14T18:57:00","modified_gmt":"2013-12-14T16:57:00","slug":"connectivitywatchdog-inaccessible-tcp-based-service-notification-via-email","status":"publish","type":"post","link":"https:\/\/alax.info\/blog\/1474","title":{"rendered":"ConnectivityWatchdog: Inaccessible TCP based Service Notification via Email"},"content":{"rendered":"
\n

This is dual “yet another…” and utility clearance series. Once again an attempt to easily automate network availability check for a service.<\/p>\n

The application is doing periodic TCP connectivity check and sends an email to notify on inaccessible service. If you got systems running at 2+ sites, they can be set up to check one another and inform timely on network issues.<\/p>\n

\"ConnectivityWatchdog<\/p>\n

Configuration is provided through\u00c2\u00a0ConnectivityWatchdog.ini<\/code>\u00c2\u00a0file to be put into the directory of the binary. Sample file is as follows:<\/p>\n

[General]\r\n\r\n[Host]\r\n$(SomeUniqueIdentifer)=$(FriendlyName), tcp, $(TcpHostOrIpAddress), $(TcpPort)\r\n$(SomeUniqueIdentifer)=$(FriendlyName), tcp, $(TcpHostOrIpAddress), $(TcpPort)\r\n\r\n[Probe.TCP]\r\nConnection Time=45 ; Timeout for TCP connection attempt, seconds\r\nSuccess Idleness Time=60 ; Next attempt in case of successful connection, seconds\r\nFailure Idleness Time=10 ; Next attempt in case of failed connection, seconds\r\nNotification Failure Count=3, 33, 333 ; Numbers of failure attempts which trigger email notification \r\n\r\n[Notification]\r\nDelay=450 ; Delay in notification in order to combine messages into single email, seconds \r\n\r\n[Notification.SMTP]\r\nHost=smtp.gmail.com\r\nSender=$(UserName)@gmail.com\r\nTo=$(UserName)@gmail.com\r\nTLS=1\r\nAuthentication Methods=login\r\nAuthentication Name=$(UserName)@gmail.com\r\nAuthentication Password=$(Password)\r\n<\/code><\/pre>\n
Once the application notices TCP connectivity issues, it updates UI status and as configured (see “Notification Failure Count” value above) it will trigger a notification email:<\/p>\n
The following are the updates on $(Host) system:\r\n\r\n * Remote host $(FriendlyName) connection SUCCEEDED after 8 failures [2013-12-12 02:15:06 - 4 minutes ago]\r\n * Remote host $(FriendlyName) connection FAILED 3 times in a row (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond - 0x8007274c) [2013-12-12 02:12:21 - 7 minutes ago]\r\n\r\n--\r\n  System: $(Host)\r\n  Time: 2013-12-12 02:19:51\r\n  Agent: Alax.Info ConnectivityWatchdog Application\/1.0.0.58\r\n<\/code><\/pre>\n
All $(…) values above are placeholders.<\/p>\n
The application has a convenient option to enable automatic startup with user logon.<\/p>\n
\"ConnectivityWatchdog<\/p>\n
Download links<\/h3>\n