Hi Joe, That's right, monitoring periodically queries switches for statistics and exposes that info. The interface is probably not going to chance any time soon. It has been used and tested to some extent, and has been proven ok for what it used so far. It exposes information like table_stats, port_stats, aggregate_stats I'm not aware of scripts that demonstrate its usage, but the GUI interacts with monitoring to display some switch statistics etc. So if you wanted to delve into the code there you could find an example of how to use the API. (It's probably more complicated than you need since, 'messenger' is used between the GUI and monitoring for their communication. You probably don't care about interfacing with an external program like that)
On Tue, Jan 17, 2012 at 5:58 PM, Joe Stringer <joestrin...@google.com>wrote: > Hi all, > > I'm currently writing an SNMP subagent to interface with NOX to fetch > openflow statistics from NOX. To this end, I was thinking of fetching > the statistics via JSON messages. I noticed that netapps/monitoring in > the destiny branch caches stats about connected datapaths, and it > looks like it could be useful for my project. > > What is the current status of the monitoring component in the destiny > branch? > - Is the interface likely to change much? > - What information does it expose? > - Are there any scripts like src/scripts/nox-console.py that have > examples of how to structure messages to get certain types of replies? > > Cheers, > Joe > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
