Day 13 - Connection Monitor
This application allows you to monitor 3 types of connections - ICMP (ping), socket connection, and HTTP. It has a fairly intuitive interface, and I invite you to try it!.
Upon launching, like many of my apps, it'll disappear into the systray. Options are available there for adding connections to monitor, and changing the retry rate.Each connection also independently has a failure allowance. If it exceeds this failure allowance it will balloon onto your desktop, warning you of it's failure. Hopefully this application can help some web or system admins out the without the budget for expensive monitoring tools.
Download the app here
Download the source here
Cheers!
posted by Unknown @ 12:17 AM
5 comments
5 Comments:
Hello Dana,
Great work so far - I'm staggered by your productivity!
One small request - could you post a screenshot (or two) of each app so I can get more of an idea of what it does without downloading it and firing up vs.net? A picture speaks a thousand words, etc etc. I know you post screenshots now and again, but one for each app would be great.
Keep it up!
Hi Dana,
AnAppADay is a really nice idea tht you have put forward and the applications are pretty good.
Good going! Keep up the good work.
One request: I'm making an application in which the Client(s) will be sending (and receiving replies) in pretty large numbers every minute to the application running on the server and I'm unsure as to how to go about it. Large Numbers = ~50-500 messages every couple of seconds. Return messages would be required for around 10% of all messages sent.
Should I monitor a port on the server and send in return messages to the client as and when requested or should I go the WebServices way. Which would you advice? Any url I could read to understand more about the connectivity options offered by .Net 2?
Thankyou :)
Thanks a lot for this app, i was waiting for it, and it seems to works pretty nice.
damned usefull!
What a great little app - which brings up an idea for a similar app.... But one with a real purpose...
Wake On Lan capability has been around for awhile now - and there is two ways of implementing it - either as just a listen for network traffic or to listen for a specific 'magic packet'. The problem with the former is that the computer wakes unneccessarily to renew ip addresses / pings / etc etc. Magic packets will just wake the computer as needed.
However not all applications support magic packets - ie. Microsoft Media Centre can not support magic packets and relys upon sending pings out to wake up other servers on your network to find and use your video / photo / mp3 files....
So why not have something like this app sitting in the tray - monitoring for a ping and then broadcasting a magic packet to wake up that server - would need a config file to list say 3-6 ip addresses to send the magic packet to....
Just trying to save the environment in keeping things off when not needed....
I cant make this work. Tells me to reinstall my .net framework.
Post a Comment
<< Home