I have a simple question that I hope someone can help me with.
Is it possible to monitor an IP Service without using SNMP or SSH? For some servers, I don't really care about in dept details, I just want to know if a web server is responding to port 80 or a DNS server is listening on port 53. I'm trying to acomplish something similar to Pingdom's HTTP monitoring.
I don't need any modelling for these devices as I would be happy enough to enter the IP services to monitor manually.
Any help would be appreciated
For the devices where you want simple port-sniffing, change the IpServiceMap modeler plugin to zenoss.portscan.IpServiceMap. Best to do this at a device class to automatically apply it to several devices. By default the /Server class has zenoss.snmp.IpServiceMap allocated so iIwould probably change it there.
All the rest of the configuration of actual ports to monitor is unaffected; it is just the underlying collection mechanism that changes.
If you don't need modelling then you can create command line template with check_http or check_dns plugin for http and DNS services respectively and bind it to device.
Also you can use generic check_tcp and check_udp plugins
I'm very new to Zenoss so please forigve my ignorrance.
How do I change the modeller plugins used on a per-device or per-class basis?
After I change the pluging, I'm guessing it's just a matter of disabling Ping and SNMP checks? How do I initate the port scan? Is there any way to add services without a port scan (by simple telling Zenoss to monitor port x)?
Also, regarding alex0cy's post, how do I create templates? I'm not really sure what templates are, sorry
Thanks and I'm sorry for all the questions.
I would go to INFRASTRUCTURE and then select Server in the lefthand menu. Then, there should be a DETAILS link at the top of the lefthand menu - click that. In the new window, you should be able to adjust all sorts of setting for the device class of /Server.
Click Modeler Plugins and you will find several plugins are in the assigned window, including zenoss.snmp/IpServiceMap. Click on that and move it to the unselected list. Then in that unselected/available list, find zenoss.portscan.IpServiceMap and click to move it to the selected list. Save your changes.
Whenever the zenstatus daemon runs (the daemon that does the port checking) it will now use portscan rather than SNMP. By default, zenstatus runs every 1 minute.
The services to monitor will depend on what services were available at the last modeler cycle (which typically runs every 12 hours). Whatever is et to be monitored and was detected at the modeler cycle, will then be monitored.
Try getting the Zenoss Admin Guide - it will give you a good start on these things - http://community.zenoss.org/community/documentation .
Thanks Jane for your excellent help
I'll do my homework this weekend and read that Admin guide, I promise!
Is it possible to monitor IP services with modelling the device? Somehow just manually specifying which ports to monitor?
I'm a little confused about something.
In Zenoss's default configuration for /Server (using zenoss.snmp.IpServiceMap), I have to enable firewall rules from the zenoss server to the actual service on the monitored server for Zenoss to detect that the service is up. Is this correct? Can you please explain to me the difference between portscan.IpServiceMap and snmp.IpServiceMap?
As far as I am aware portscan.IpServiceMap will do an actual port scant, while snmp.IpServiceMap, uses the SNMP table (tcp=.188.8.131.52.184.108.40.206.1, udp=.220.127.116.11.18.104.22.168.1) on the remote device to determine ip services.
Ok, so SNMP or portscan are means of discovering IP Services.
So does that mean the actual *monitoring* of the services is done by actual connections to the ports? Is there no way to monitor the running IP Services without opening all ports to the monitored server?
Note: This is a different issue from my orignal question at the top of this thread.
I'm not too sure what the actual means of monitoring is, but I'd have to assume that it does so by making a connection. The ZenTcpClient implies that its likely the code that handles that test, and it seems to do by making a connection.
I'm not sure of a way you could reliably monitor the tcp service without having the port opened.
Follow Us On Twitter »
||Latest from the Zenoss Blog »||Community||Products||Services||Customers||About Us|
Copyright © 2005-2011 Zenoss, Inc.