So there is UDP port testing with response parsing, great!
Will there ever be the same test for TCP ports ?
TCP port response parsing
Could you please write some schedule ? any schedule ? Will it be implemented in month, 3 months, half a year ?
I'm concerning still the same problem. I've got the http test which parses url and searches for the string. The test goes down. I run the url manually from IE6 on the hosmon's machine. Everything's fine. There is no proxies, no dns'es (I use IP) no network traffic (tested machine stands next to hostmon's).
So I have the reasons to believe that there has to be something with url testing. I don't know what, but I can see two options:
1. Add debug logging to hostmon. To be able to see where the problem is and be able to eliminate it or post bug report that would be more specific than these are now.
2. Add TCP port testing and forget about http, smtp dns tests and test it just like you would do i t via telnet.
I'm concerning still the same problem. I've got the http test which parses url and searches for the string. The test goes down. I run the url manually from IE6 on the hosmon's machine. Everything's fine. There is no proxies, no dns'es (I use IP) no network traffic (tested machine stands next to hostmon's).
So I have the reasons to believe that there has to be something with url testing. I don't know what, but I can see two options:
1. Add debug logging to hostmon. To be able to see where the problem is and be able to eliminate it or post bug report that would be more specific than these are now.
2. Add TCP port testing and forget about http, smtp dns tests and test it just like you would do i t via telnet.