ovs/lib/coverage-unixctl.man

.SS "COVERAGE COMMANDS"
These commands manage \fB\*(PN\fR's ``coverage counters,'' which count
the number of times particular events occur during a daemon's runtime.
In addition to these commands, \fB\*(PN\fR automatically logs coverage
counter values, at \fBINFO\fR level, when it detects that the daemon's
main loop takes unusually long to run.
.PP
Coverage counters are useful mainly for performance analysis and
debugging.
.IP "\fBcoverage/show\fR"
Displays the values of all of the coverage counters.
coverage: Make ovs-appctl command more useful and less alarming. I've had a few complaints that ovs-vswitchd logs its coverage counters at WARN level, but this is mainly wrong: ovs-vswitchd only logs coverage counters at WARN level when the "coverage/log" command is used through ovs-appctl. This was even documented. The reason to log at such a high level was to make it fairly certain that these messages specifically requested by the admin would not be filtered out before making it to the log. But it's even better if the admin just gets the coverage counters as a reply to the ovs-appctl command. So that is what this commit does. This commit also improves the documentation of the ovs-appctl command. Signed-off-by: Ben Pfaff <blp@nicira.com> 2012-04-20 14:09:30 -07:00			`.SS "COVERAGE COMMANDS"`
			These commands manage \fB\*(PN\fR's ``coverage counters,'' which count
			`the number of times particular events occur during a daemon's runtime.`
			`In addition to these commands, \fB\*(PN\fR automatically logs coverage`
			`counter values, at \fBINFO\fR level, when it detects that the daemon's`
			`main loop takes unusually long to run.`
			`.PP`
			`Coverage counters are useful mainly for performance analysis and`
			`debugging.`
			`.IP "\fBcoverage/show\fR"`
			`Displays the values of all of the coverage counters.`