[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dante-misc
Subject:    Re: Bandwidth and Session monitoring
From:       Michael Shuldman <michaels () inet ! no>
Date:       2009-04-14 7:22:20
Message-ID: 20090414072220.GA1038 () kosmo ! inet ! no
[Download RAW message or body]

Michael Shuldman wrote,
> Markus Moeller wrote,
> > Is there a free or commercial module which allows the monitoring of 
> > number of sessions, bandwidth use per session, amount of data transferred 
> > per session ?
> 
> The amount of bytes transfered is printed out when the session ends,
> if you have specified logging of disconnect.  
> 
> E.g.:
> 
> Apr  7 21:53:12 (1239137592) sockd[8564]: pass(1): tcp/connect ]: 
> 745 -> 192.168.1.27.43131 -> 128,  128 -> 212.219.56.135.21 -> 745:
> client error: Connection reset by peer (errno = 131)
> 
> Meaning 745 bytes were sent to 192.168.1.27.43131, and 
> 192.168.1.27.43131 sent 128 bytes.
> 
> 128 bytes were sendt to 212.219.56.135.21, and 212.219.56.135.21
> send 745 bytes.
> 
> We have two modules that allow _controling_ the number of sessions,
> and the amount of bandwidth used per session, i.e. the session
> module and the bandwidth module, as described on
> "http://www.inet.no/dante/module.html".
> 
> If you by monitoring mean some statistics, based on logs or real-time
> analysis, we unfortunately do not have that currently.

One minor thing I forgot to mention is that if you send the main
sockd process a SIGINFO (or SIGUSR1 on platforms without SIGINFO),
it will print out some information about the current clients,
as well as the total number of clients handled.

-- 
  _ // 
  \X/ -- Michael Shuldman <michaels@inet.no>

[prev in list] [next in list] [prev in thread] [next in thread]