Rick Stevens wrote:
There's no simple way to track "views" of a stream other than parsing the log files from the server and tracking them that way. You must look for (at least) start events, stop events, pause events, and resume events with the same session ID. You can compute the view time from those. It ain't easy. We process literally millions of log events every day. As far as bandwidth, you can use the log entries (doesn't generally cover the overhead--only the active streams), RRD/Cacti, or if you use Cisco gear, Netflow (you'll have to write programs to analyze that).
Ntop/nprobe might be good for this: http://www.ntop.org/nProbe.html -- Les Mikesell lesmikesell@xxxxxxxxx -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
