Results 1 to 6 of 6

Thread: Interpreting Data Transfer from logs.

  1. #1
    Join Date
    Feb 2010
    Posts
    25

    Default Interpreting Data Transfer from logs.

    I'm trying to interpret Wowza's logs (Wowza Media Server 3 for Amazon EC2 3.5.0 build2989) and am having trouble interpreting data transfer.

    According to the user guide, the following fields can be used for data transfer:
    • cs-bytes: Total number of bytes transferred from client to server (cumulative)
    • cs-stream-bytes: Total number of bytes transferred from client to server for stream x-stream-id (cumulative)
    • sc-bytes: Total number of bytes transferred from server to client (cumulative)
    • sc-stream-bytes: Total number of bytes transferred from server to client for stream x-stream-id (cumulative)


    This, to me, means that I can use "sc-bytes" to see the total data transfer and "sc-stream-bytes" for that particular play connection..am I correct?

    The issue is that the only populated field is "sc-stream-bytes", and I can't find the logic behind it. For example, I have tested one live stream only on entire server, it identifies itself (x-stream-id) as "1" on the "publish->stream" event, yet "play->stream" randomly returns anything from 1 - 5.

    Which fields should I use in order to gather the following statistics:

    1. Total bytes out from server
    2. Total bytes out from stream
    3. Total bytes out from play event

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    If you publish "myStream" from a live encoder, then 5 clients are playing it, that is 6 streams: 1 in and 5 out. Each will have a different clientID

    The publish stream will have significant cs-bytes. The playback streams will have significant cs-bytes.

    For Flash RTMP clients only there is a distinction between client and stream, which corresponds to NetConnection and NetStream.

    The logs will not show total bytes from server on any one line. You have to total rows with x-event "destroy".

    Look at the x-client-id for a new publish or play stream, then find the last row it appears in. That should be x-event "destroy" row, though it is possible that it is not a "destroy" row, the server may have shutdown suddenly for example

    Richard

  3. #3
    Join Date
    Feb 2010
    Posts
    25

    Default

    So in essence:

    Total bytes out from server = all x-event="destroy" added up

    Total bytes out from play event = x-event="destroy" for particular clientid

    Total bytes out from stream = all x-event="destroy" for particular xsname added up

    ...am I correct?

  4. #4
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Yes, except there should only be one "destroy" row for the 3rd example, per stream. There might be more than one stream per RTMP client if Netstream is stopped and started using one NetConnection, but in practice that does not happen usually.

    The best way to understand logs is to do short, isolated tests and look at the log results.

    Richard

  5. #5
    Join Date
    Feb 2010
    Posts
    25

    Default

    Thank you, that works great. Now to continue bothering you with questions...

    Publishing a stream creates a series of secondary events that I can't seem to connect to the primary publish/create event without searching through strings.

    For example, in the attached log extract, the event chain begins at 33626 with the "connect" event of a camera sending an rtsp stream, it is identified by the clientid "892717755", which matches a few of the secondary events afterwards, but the majority of the "comment->server->info" events have no field that can be used to directly match them to their parent event. Some of them have the string "live/_definst_/camara" in the xcomment which I can do a search for, but some (for example event 33635), has nothing that can be used to match it to its parent.

    Is there any way this can be modified so that the entire chain of events is identified by the same clientid or some other identifiable string in all the events?

    logid date time tz xevent xcategory xseverity xstatus xctx xcomment xvhost xapp xappinst xduration sip sport suri cip cproto creferrer cuseragent cclientid csbytes scbytes xstreamid xspos csstreambytes scstreambytes xsname xsnamequery xfilename xfileext xfilesize xfilelengtd xsuri xsuristem xsuriquery csuristem csuriquery
    33626 2013-01-26 12:53:58 UTC connect rtsp INFO 200 892717755 - _defaultVHost_ live _definst_ 86977.055 10.0.0.157 - rtsp://10.0.0.157:1935/live/camara 10.0.0.157 rtsp - - 892717755 0 - - - - - - - - - - - rtsp://10.0.0.157:1935/live/camara rtsp://10.0.0.157:1935/live/camara - - -
    33627 2013-01-26 12:53:58 UTC create stream INFO 200 - - _defaultVHost_ live _definst_ 0.0 10.0.0.157 - rtsp://10.0.0.157:1935/live/camara 10.0.0.157 rtsp - - 892717755 0 - 1 0 0 0 camara - - - - - rtsp://10.0.0.157:1935/live/camara rtsp://10.0.0.157:1935/live/camara - - -
    33628 2013-01-26 12:53:58 UTC announce rtsp INFO 200 892717755 - _defaultVHost_ live _definst_ 0.228 10.0.0.157 - rtsp://10.0.0.157:1935/live/camara 10.0.0.157 rtsp - - 892717755 0 - - - - - camara - - - - - rtsp://10.0.0.157:1935/live/camara rtsp://10.0.0.157:1935/live/camara - - -
    33629 2013-01-26 12:53:58 UTC comment server INFO 200 - RTPUDPTransport.bind[live/_definst_]: /10.0.0.157:6970 - - - 0.234 - - - - - - - - - - - - - - - - - - - - - - - - -
    33630 2013-01-26 12:53:58 UTC comment server INFO 200 - RTPUDPTransport.bind[live/_definst_]: /10.0.0.157:6971 - - - 0.242 - - - - - - - - - - - - - - - - - - - - - - - - -
    33631 2013-01-26 12:53:58 UTC publish stream INFO 200 camara - _defaultVHost_ live _definst_ 0.046 10.0.0.157 - rtsp://10.0.0.157:1935/live/camara 10.0.0.157 rtsp - - 892717755 0 - 1 0 0 0 camara - - - - - rtsp://10.0.0.157:1935/live/camara rtsp://10.0.0.157:1935/live/camara - - -
    33632 2013-01-26 12:53:58 UTC publish rtsp INFO 200 892717755 - _defaultVHost_ live _definst_ 0.249 10.0.0.157 - rtsp://10.0.0.157:1935/live/camara 10.0.0.157 rtsp - - 892717755 0 - - - - - camara - - - - - rtsp://10.0.0.157:1935/live/camara rtsp://10.0.0.157:1935/live/camara - - -
    33633 2013-01-26 12:53:59 UTC comment server INFO 200 - RTCPHandler.sendFirstRTCPRR[1810054795,6971,/10.0.0.157:5001] - - - 86977.54 - - - - - - - - - - - - - - - - - - - - - - - - -
    33634 2013-01-26 12:53:59 UTC comment server INFO 200 - UDPTransport.firstPacket: bind:/10.0.0.157:6971 msg:/10.0.0.157:5001 - - - 86977.615 - - - - - - - - - - - - - - - - - - - - - - - - -
    33635 2013-01-26 12:53:59 UTC comment server INFO 200 - UDPTransport.firstPacket: bind:/10.0.0.157:6970 msg:/10.0.0.157:5000 - - - 86977.616 - - - - - - - - - - - - - - - - - - - - - - - - -
    33636 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.init[live/_definst_/camara]: chunkDurationTarget: 10000 - - - 86977.622 - - - - - - - - - - - - - - - - - - - - - - - - -
    33637 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.init[live/_definst_/camara]: chunkDurationTolerance: 500 - - - 86977.623 - - - - - - - - - - - - - - - - - - - - - - - - -
    33638 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.init[live/_definst_/camara]: playlistChunkCount:4 - - - 86977.625 - - - - - - - - - - - - - - - - - - - - - - - - -
    33639 2013-01-26 12:53:59 UTC comment server INFO 200 - MediaStreamMap.getLiveStreamPacketizer: Create live stream packetizer: sanjosestreamingpacketizer:camara - - - 86977.626 - - - - - - - - - - - - - - - - - - - - - - - - -
    33640 2013-01-26 12:53:59 UTC comment server INFO 200 - SanJosePacketdandler.startStream[live/_definst_/camara] - - - 86977.632 - - - - - - - - - - - - - - - - - - - - - - - - -
    33641 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.handlePacket[live/_definst_/camara]: Video codec: H264 - - - 86977.634 - - - - - - - - - - - - - - - - - - - - - - - - -
    33642 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.init[live/_definst_/camara]: chunkDurationTarget: 10000 - - - 86977.636 - - - - - - - - - - - - - - - - - - - - - - - - -
    33643 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.init[live/_definst_/camara]: chunkDurationTolerance: 500 - - - 86977.712 - - - - - - - - - - - - - - - - - - - - - - - - -
    33644 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.init[live/_definst_/camara]: audioGroupCount: 3 - - - 86977.713 - - - - - - - - - - - - - - - - - - - - - - - - -
    33645 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.init[live/_definst_/camara]: playlistChunkCount:3 - - - 86977.714 - - - - - - - - - - - - - - - - - - - - - - - - -
    33646 2013-01-26 12:53:59 UTC comment server INFO 200 - MediaStreamMap.getLiveStreamPacketizer: Create live stream packetizer: cupertinostreamingpacketizer:camara - - - 86977.715 - - - - - - - - - - - - - - - - - - - - - - - - -
    33647 2013-01-26 12:53:59 UTC comment server INFO 200 - CupertinoPacketdandler.startStream[live/_definst_/camara] - - - 86977.724 - - - - - - - - - - - - - - - - - - - - - - - - -
    33648 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.handlePacket[live/_definst_/camara]: Video codec:H264 isCompatible:true - - - 86977.726 - - - - - - - - - - - - - - - - - - - - - - - - -
    33649 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.handlePacket[live/_definst_/camara][avc1.66.30]: H.264 Video info: {H264CodecConfigInfo: codec:H264, profile:Baseline, level:3.0, frameSize:352x240, displaySize:352x240, frameRate:20.0} - - - 86977.728 - - - - - - - - - - - - - - - - - - - - - - - - -
    33650 2013-01-26 12:53:59 UTC comment server INFO 200 - MediaStreamMap.getLiveStreamPacketizer: Create live stream packetizer: smootdstreamingpacketizer:camara - - - 86977.725 - - - - - - - - - - - - - - - - - - - - - - - - -
    33651 2013-01-26 12:53:59 UTC comment server INFO 200 - LiveStreamPacketizerSmootdStreaming.startStream[live/_definst_/camara] - - - 86977.731 - - - - - - - - - - - - - - - - - - - - - - - - -

  6. #6
    Join Date
    Feb 2010
    Posts
    25

    Default

    Regarding my last post, I've tried using a query parameter when publishing the stream "?ident=prueba" to see if that works, but it follows the same rules when filling in xsnamequery, so that doesn't help either.

Similar Threads

  1. Error in logs BufferUtils and show logs in terminal
    By livesreamingforall in forum General Forum
    Replies: 7
    Last Post: 06-30-2015, 06:53 AM
  2. Live. SMIL playlist. Data transfer from server to off-site destination
    By glorin in forum Live Streaming and Encoder Discussion
    Replies: 1
    Last Post: 05-18-2013, 12:42 PM
  3. How to transfer data between two servers?
    By lokki7 in forum Server-side Modules and Code Samples Discussion
    Replies: 2
    Last Post: 04-24-2012, 10:11 PM
  4. Help required in interpreting nDVR Log entry
    By josnidhin in forum AddOn: Wowza nDVR
    Replies: 2
    Last Post: 03-05-2012, 06:42 AM

Posting Permissions

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