Hi Folks,
I'm going to write some pollers to fit my needs, but I have a very general question: I saw that most of the original interface types define all their values in one interface. The advantage is obviously all values in one hand, the disadvantage is that values which are not considered interesting are also polled. How about the idea of a more or less general interface type (e.g. temperature, humidity, whatever) and a smart discovery procedure, which delivers all the info necessary for polling? The discovery would have to deliver a generic variable with the oid to test. I tried this approach and it worked quite good - for a very finite number of interfaces in my test scenario. The advantage would be less rrd-variables and less polling, but more interfaces, which would take more time for poller.php to execute. Which drawbacks are worse from your point of view, valued community? kind regards Markus ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ jffnms-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jffnms-users
