Icecast - May 2018 - How to log querystring values?

Dear Philipp,
  
 Thanks for you reply.
  
 My goal is to show in our analytics page segmented data (official apps, 
partner apps, third-party apps, demographic and geo). To do so each app 
pass some values in the query string (ie: app id, user id, lat, lng). And I 
need to know those values in order to do that.
  
 Today we are using nginx as a reverse proxy to Icecast to get those data 
but it double the cpu/mem usage =(
  
 I am welcome to any idea. =)
  
  
 Best,
 Thiago
  
  

----------------------------------------
 De: "Philipp Schafft" <lion at lion.leolix.org>
Enviado: domingo, 6 de maio de 2018 09:30
Para: subscription at nextdial.com.br, "Icecast streaming server user 
discussions" <icecast at xiph.org>
Assunto: Re: [Icecast] How to log querystring values?   
Dear Mr./Ms. subscription,

On Sun, 2018-05-06 at 08:35 -0300, subscription at nextdial.com.br
wrote:
> I need to get some values passed in the querystring request in the log
> file.
>
> Something like that bellow:
>
> ie: "GET /radio?id=1 HTTP/1.1" instead of only "GET /radio
HTTP/1.1"
>
> Do I need to change something in the source and compile? Or there is
> another way?
What exactly is your goal? Maybe you can give us a bit of an
understanding of the context.

Query parameters are to be interpreted by the server, in this case
Icecast, not external software. Therefore I suspect that there is a
better solution for your problem.

With best regards,

--
Philipp.
(Rah of PH2)
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20180506/afeef368/attachment.html>

Good Morning Thiago,

On Sun, 2018-05-06 at 10:23 -0300, subscription at nextdial.com.br
wrote:
> Dear Philipp,
>   
>  Thanks for you reply.
>   
>  My goal is to show in our analytics page segmented data (official apps, 
> partner apps, third-party apps, demographic and geo).
> To do so each app pass some values in the query string (ie: app id,
> user id, lat, lng). And I  need to know those values in order to do
> that.
I would recommend to add those to (a) custom header field(s). You can
then log that by using URL auth. This is to the standards and will also
add more flexibility to the system, such as real time stats.

If you really, really need to pass the parameters using query string
parameters we could implement a separate logfile for that. That would
keep the main log intact and provide a (probably better) parseable log
for those data. (If you're interested in this option contact me
off-list.)

>  Today we are using nginx as a reverse proxy to Icecast to get those data 
> but it double the cpu/mem usage =(
using a rproxy is not ideal and should be avoided. :)


with best regards,

> ----------------------------------------
>  De: "Philipp Schafft" <lion at lion.leolix.org>
> Enviado: domingo, 6 de maio de 2018 09:30
> Para: subscription at nextdial.com.br, "Icecast streaming server user 
> discussions" <icecast at xiph.org>
> Assunto: Re: [Icecast] How to log querystring values?   
> Dear Mr./Ms. subscription,
> 
> On Sun, 2018-05-06 at 08:35 -0300, subscription at nextdial.com.br wrote:
> > I need to get some values passed in the querystring request in the log
> > file.
> >
> > Something like that bellow:
> >
> > ie: "GET /radio?id=1 HTTP/1.1" instead of only "GET
/radio HTTP/1.1"
> >
> > Do I need to change something in the source and compile? Or there is
> > another way?
> 
> What exactly is your goal? Maybe you can give us a bit of an
> understanding of the context.
> 
> Query parameters are to be interpreted by the server, in this case
> Icecast, not external software. Therefore I suspect that there is a
> better solution for your problem.
-- 
Philipp Schafft (CEO/Geschäftsführer) 
Telephon: +49.3535 490 17 92

Löwenfelsen UG (haftungsbeschränkt)     Registration number:
Bickinger Straße 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20180507/d24d808d/attachment.sig>

Philipp,
  
 Thanks so much for your time and relpy.
  
 This dawn, before read your email, I worked to implement the URL authentication
and it worked like a charm. I am still using querystring instead of custom
header field because I have no control over the player. But, the excelent news
is, no more rproxy! =)
  
 And you were right, this way I have more possibilities than before!
  
 Again, thanks so much and congrats for the awesome job.
  
 ps: Icecast is so far more efficient than SHOUTcast and a lot websites says
they have no big differences, why?
  
  
 Best,
 Thiago
  
  
  

----------------------------------------
 De: "Philipp Schafft" <phschafft at de.loewenfelsen.net>
Enviado: segunda-feira, 7 de maio de 2018 03:40
Para: subscription at nextdial.com.br, "Icecast streaming server user
discussions" <icecast at xiph.org>
Assunto: Re: [Icecast] How to log querystring values?   
Good Morning Thiago,

On Sun, 2018-05-06 at 10:23 -0300, subscription at nextdial.com.br
wrote:
> Dear Philipp,
>
> Thanks for you reply.
>
> My goal is to show in our analytics page segmented data (official apps,
> partner apps, third-party apps, demographic and geo).
> To do so each app pass some values in the query string (ie: app id,
> user id, lat, lng). And I need to know those values in order to do
> that.
I would recommend to add those to (a) custom header field(s). You can
then log that by using URL auth. This is to the standards and will also
add more flexibility to the system, such as real time stats.

If you really, really need to pass the parameters using query string
parameters we could implement a separate logfile for that. That would
keep the main log intact and provide a (probably better) parseable log
for those data. (If you're interested in this option contact me
off-list.)
> Today we are using nginx as a reverse proxy to Icecast to get those data
> but it double the cpu/mem usage =(
using a rproxy is not ideal and should be avoided. :)

with best regards,
> ----------------------------------------
> De: "Philipp Schafft" <lion at lion.leolix.org>
> Enviado: domingo, 6 de maio de 2018 09:30
> Para: subscription at nextdial.com.br, "Icecast streaming server user
> discussions" <icecast at xiph.org>
> Assunto: Re: [Icecast] How to log querystring values?
> Dear Mr./Ms. subscription,
>
> On Sun, 2018-05-06 at 08:35 -0300, subscription at nextdial.com.br wrote:
> > I need to get some values passed in the querystring request in the log
> > file.
> >
> > Something like that bellow:
> >
> > ie: "GET /radio?id=1 HTTP/1.1" instead of only "GET
/radio HTTP/1.1"
> >
> > Do I need to change something in the source and compile? Or there is
> > another way?
>
> What exactly is your goal? Maybe you can give us a bit of an
> understanding of the context.
>
> Query parameters are to be interpreted by the server, in this case
> Icecast, not external software. Therefore I suspect that there is a
> better solution for your problem.
--
Philipp Schafft (CEO/Geschäftsführer)
Telephon: +49.3535 490 17 92

Löwenfelsen UG (haftungsbeschränkt) Registration number:
Bickinger Straße 21 HRB 12308 CB
04916 Herzberg (Elster) VATIN/USt-ID:
Germany DE305133015
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20180507/e3bd112c/attachment.html>