Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: wms-plugin-collection

  1. #1

    Default wms-plugin-collection

    hi,
    i just installed wms-plugin-collection, and added ModuleLogViewerCounts, its all fine i am able to see update on cmd box after every 10 sec, but i want to know how do i access this info at http.

  2. #2
    Join Date
    Dec 2007
    Posts
    25,642

    Default

    That collection module will not work over HTTP. It wouldn't work as an HTTProvider because it is logging every 10 seconds, so it needs to be started with an Application.

    Richard

  3. #3

    Default

    Quote Originally Posted by rrlanham View Post
    That collection module will not work over HTTP. It wouldn't work as an HTTProvider because it is logging every 10 seconds, so it needs to be started with an Application.

    Richard
    can you give me some idea how to make that application to have in on http

  4. #4
    Join Date
    Dec 2007
    Posts
    25,642

    Default

    Use the built-in HTTPRovider, "HTTPConnectionInfo":

    http://[wowza-address]:8086/connectioncounts

    Richard

  5. #5

    Default

    Quote Originally Posted by rrlanham View Post
    Use the built-in HTTPRovider, "HTTPConnectionInfo":

    http://[wowza-address]:8086/connectioncounts

    Richard
    there is a problem
    i tried it but it given me a issue
    one stream was on as "1" and there was around 100 viewers and then i make it off but its still saying <ConnectionsCurrent>49</ConnectionsCurrent>, its like 10 mins and still saying 49 how 49 viewers when its off and how status is still <Status>loaded</Status>

  6. #6
    Join Date
    Dec 2007
    Posts
    25,642

    Default

    I can explain: If you turn on your encoder and publish a stream, then 100 people subscribe to it, then you turn off the encoder, and 51 people close the browser, you will still see 49 connection subscribed to the stream. They aren't seeing any video because the encoder is turned off, but they are still subscribed to that stream. If you turn the encoder back on and start publishing a stream with the same name to the same application, those 49 clients will start receiving video again.

    Richard

  7. #7

    Default

    Quote Originally Posted by rrlanham View Post
    I can explain: If you turn on your encoder and publish a stream, then 100 people subscribe to it, then you turn off the encoder, and 51 people close the browser, you will still see 49 connection subscribed to the stream. They aren't seeing any video because the encoder is turned off, but they are still subscribed to that stream. If you turn the encoder back on and start publishing a stream with the same name to the same application, those 49 clients will start receiving video again.

    Richard
    yes correct, but actually i want a way that can tell me that stream is live or offline whats the way to check it ? if need http provider so is there any ready to install ?

  8. #8

    Default

    so no idea ?

  9. #9
    Join Date
    Dec 2007
    Posts
    25,642

    Default

    You could use the Watchdog module:
    http://www.wowzamedia.com/forums/showthread.php?t=6903

    Also, with the HTTPServerInfoXML HTTProvider ( http://[wowza-address]:8080/serverinfo) you would see client node like this

    <Client>
    <ClientId>1265242471</ClientId>
    <FlashVersion>FMLE/3.0 (compatible; FMSc/1.0)</FlashVersion>
    <IpAddress>127.0.0.1</IpAddress>
    - <Referrer>
    - <![CDATA[ rtmp://localhost/live
    ]]>
    </Referrer>
    <TimeRunning>3.172</TimeRunning>
    <DateStarted>Mon, Apr 19 2010 14:56:22 -0400</DateStarted>
    - <URI>
    - <![CDATA[ rtmp://localhost/live
    ]]>
    </URI>
    <Protocol>RTMP</Protocol>
    <IsSSL>false</IsSSL>
    <IsEncrypted>false</IsEncrypted>
    <Port>1935</Port>
    </Client>
    But you would see that if FMLE is connected and not streaming, so it doesn't tell you if a stream live.

    Richard

  10. #10

    Default

    Quote Originally Posted by rrlanham View Post
    Use the built-in HTTPRovider, "HTTPConnectionInfo":

    http://[wowza-address]:8086/connectioncounts

    Richard
    We're polling this for use in munin, and find that it's wildly inaccurate compared to fetching the same value via JMX.

    The JMX graph (in bytes/sec) is here:


    and the HTTP based graph (granted, bits per second.. but still vastly different) is:
    Last edited by denefoster; 08-15-2010 at 06:45 PM.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •