[darkice] Re: user Statistics & logging
- From: GO DJ HaKa <gangstified@xxxxxxxxx>
- To: darkice@xxxxxxxxxxxxx
- Date: Sun, 22 Jan 2012 09:43:51 -0600
I've had my host setup awstats. The only problem unlike Paolo Patruno, my
awstats shows unknown for a few things (Connect to site from , browser,
operating system, & file type are all unknown. file type shows m3u but 98%
is unknown WHICH may be because they listen from http://tunein.com/)
tunein is a site that logs radio stations (mine showed up automatically
then i added the correct info. prob pulled the station list from
icecast/shoutcast directory)
they have an app available on android phones (and prob iphone) to allow
easy listening which makes our job easier (having to have a station site &
either flash/mmp/ffp whatever type player )
@Niels I will give cacti a shot I love the way it does the timed graphs.
For a cacti setup does the software, like awstats, need to be on the host
computer? I have a professional hosting package, 4-5 mountpoints of icecast
(different stations) remotely. Just so i know what to tell the host (he did
the awstats for me).
On Mon, Jan 16, 2012 at 6:23 AM, Niels Dettenbach <nd@xxxxxxxxxxxx> wrote:
> Am Sonntag, 15. Januar 2012, 13:31:23 schrieb GO DJ HaKa:
> > anyone with experience with awstats?
>
> Yes,
> we use awstats AND webalizer AND cacti (RRDTool).
>
>
> Why:
> ====
> Awstats and webalizer was developed for typical web server traffic, but not
> streaming traffic, even if it can read icecast logfiles (as they are
> "compatible" by format to other web logging formats) - so it did not offer
> us
> the most important details we want to know:
>
> - the number of current / concurrent listeners on each stream or at
> all
>
> We use awstats with GeoIP mainly to get a "geographical view" of where our
> listeners come from and some tech details about the interaction with our
> icecasts (i.e. what kind of user agents they use), but nothing more "really
> useful" as requests hits or visits could not be counted as is or
> interpreted
> without important limitations on radio streams.
>
> We use webalizer in parallel because awstats uses another set of algos to
> calculate "visitors" then i.e. webalizer - so the results differ up to *3.
>
> Most important thing our radio makers and heads want to know is how many
> listeners are in the audience currently or at any time in the past.
> Therefor i
> just found commercial solutions, but want a open source one.
>
> For this i've modified a set of small php scripts (icecast for cacti -
> found
> it somewhere in a forum but required some works to get running for me)
> which
> feeds CACTI (an RRDTool web frontend - as we use it for many other graphing
> jobs too and it has a nice GUI for end users and a smartphone app client
> version etc.) which produces graphes in many different time ranges (from
> i.e.
> the last hour up to several year or longer).
>
> See example screens here:
>
> http://www.syndicat.com/pub/darkice/mon/cacti/demo/cacti_main.png
>
> http://www.syndicat.com/pub/darkice/mon/cacti/demo/cacti_details1.png
>
> but the scripts may could used for other implementations too.
>
> hth
> cheers,
>
>
> Niels.
>
> --
> ---
> Niels Dettenbach
> Syndicat IT&Internet
> http://www.syndicat.com/
Other related posts:
