Network Application Monitoring
Hi,
I am currently looking at the beta product running under Debian 4.0(side note, I had a problem getting it up and running - support was brilliant).
I have a requirement for some monitoring to be able to do more than just do TCP port polling.
Included are:
SMTP polling
IMAP polling
DNS (udp)
Our current solution allows me to configure not only TCP port polling, but, TCP conversation polling (while in most case tcp port tests are sufficient there are scenarios when more detailed tests are required).
I see URL monitoring is a feature, will a more generic ability to do TCP conversations be made available e.g:
receive "220.*"
send "ehlo domain.com"
receive "250.*"
send "mail from: <sender@domain>"
...and on it goes until a final...
receive "250.*"
Thus allowing deeper inspecting of services that require it. If memory serves correctly (and it often doesn't) I remember reading somewhere that TCL can be embedded into java quite nicely...or was it python and java. An embedded interpreter would mean admins could get quite advanced in their testing of services.
As for UDP testing, there does not seem to be a mechanism to specify if a port is UDP or TCP based. So I am somewhat assuming that UDP port testing, and more detailed DNS checker is a request that has not yet been made.
While I am thinking of things. I would not want to spawn a perl application to test an SMTP or IMAP server, I am sure there are times when being able to write a quick script to do some advanced status tests would be required.
Looking over the available options, I am also noticing 2 things that would be useful for larger sites. One being Notification groups so that adding a common group of people to be notified can be done in one click. The other would be being able to specifiy default notification profiles in the device templates.
Are any of these features on the cards for 7.0?
The product looks really promising apart from the list of items above, unfortunately being able to do a little more than just tcp port testing is a requirement in my environment.
Cheers,
Stewart
I am currently looking at the beta product running under Debian 4.0(side note, I had a problem getting it up and running - support was brilliant).
I have a requirement for some monitoring to be able to do more than just do TCP port polling.
Included are:
SMTP polling
IMAP polling
DNS (udp)
Our current solution allows me to configure not only TCP port polling, but, TCP conversation polling (while in most case tcp port tests are sufficient there are scenarios when more detailed tests are required).
I see URL monitoring is a feature, will a more generic ability to do TCP conversations be made available e.g:
receive "220.*"
send "ehlo domain.com"
receive "250.*"
send "mail from: <sender@domain>"
...and on it goes until a final...
receive "250.*"
Thus allowing deeper inspecting of services that require it. If memory serves correctly (and it often doesn't) I remember reading somewhere that TCL can be embedded into java quite nicely...or was it python and java. An embedded interpreter would mean admins could get quite advanced in their testing of services.
As for UDP testing, there does not seem to be a mechanism to specify if a port is UDP or TCP based. So I am somewhat assuming that UDP port testing, and more detailed DNS checker is a request that has not yet been made.
While I am thinking of things. I would not want to spawn a perl application to test an SMTP or IMAP server, I am sure there are times when being able to write a quick script to do some advanced status tests would be required.
Looking over the available options, I am also noticing 2 things that would be useful for larger sites. One being Notification groups so that adding a common group of people to be notified can be done in one click. The other would be being able to specifiy default notification profiles in the device templates.
Are any of these features on the cards for 7.0?
The product looks really promising apart from the list of items above, unfortunately being able to do a little more than just tcp port testing is a requirement in my environment.
Cheers,
Stewart