| View previous topic :: View next topic |
| Author |
Message |
Guest
|
Posted: Tue Jan 03, 2006 9:56 am Post subject: icecast 2.x statistics |
|
|
Hello guys !
Only one question: what's plans for implementing statistics to subj as one i'm found in icecast 1.x ?
-PER MOUNT(!) listener clients HITS (not browsers or other!), traffic out, traffic in
is this very difficult job for icecast 2.x server?
Don't ask me to start new icecast instance per mount! It's costs my server resources... |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Jan 03, 2006 4:05 pm Post subject: |
|
|
Many people have suggested expanding on the stats handling but fail to give specifics. Feel free to suggest ones you think are missing.
karl. |
|
| Back to top |
|
 |
Guest
|
Posted: Tue Jan 03, 2006 10:45 pm Post subject: icecast 2.x statistics |
|
|
Hi Karl!
Let me introduce some examples...
Today: (URL http://127.0.0.1:8000/admin/stats.xml)
bitrate 128
genre icecast
listener_peak 0
listeners 0
listenurl http://127.0.0.1:8100/master
max_listeners unlimited
public 0
server_description XXX
server_name XXX
server_type audio/mpeg
server_url http://www.icecast.org/
slow_listeners 0
source_ip 127.0.0.1
stream_start Tue, 03 Jan 2006 22:34:19 +0000
total_bytes_read 2626400
total_bytes_sent 0
And what i want ? Some small addins:
PER MOUNT(!):
...
<listener_hits/>
<average_listen_time/>
....
in global stats (OVER SERVER!):
...
<total_bytes_sent/>
<total_bytes_read/>
<average_listen_time/>
... |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Jan 03, 2006 11:42 pm Post subject: |
|
|
so global server byte totals, maybe kbytes would be better for that measure and that would probably include file serve links like /status.xsl. per-mount accumulated connections could be kept easily
average listen time is more awkward, it probably shouldn't include file serving. I do have average bitrate per-mount in the -kh branch, maybe the same mechanism can work for the last N listeners.
karl. |
|
| Back to top |
|
 |
Guest
|
Posted: Wed Jan 04, 2006 9:19 am Post subject: icecast 2.x statistics |
|
|
Hi again Karl!
It's better (in my opinion) to add second counter special to measuring file serve job.
global stats will be like this:
...
<total_Kbytes_sent/>
<total_Kbytes_read/>
<total_Kbytes_sent_fserve/>
<total_Kbytes_read_fserve/>
so the "total_Kbytes_sent" variable holds all mount-points traffic EXCEPT 'file serve'.
and second question - what's about <listener_hits/> variable in per-mount stats. It is necessary-whether to expect it?
---
ddn |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed Jan 04, 2006 4:16 pm Post subject: |
|
|
The per-mount accumulated listener count is certainly easily added, just add a report on trac.xiph.org so that those suggestions are not forgotten about.
karl. |
|
| Back to top |
|
 |
Guest
|
Posted: Thu Jan 05, 2006 9:55 am Post subject: |
|
|
| karl, sorry for some offtopic: how can i do this ? |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Jan 05, 2006 10:02 am Post subject: |
|
|
| Use your browser and go to http://trac.xiph.org, click new ticket and fill out the details. Make sure the component is icecast |
|
| Back to top |
|
 |
|