From jnkernel 1.31.2, there will always be a statistics log file in joinnet log folder for a meeting session. The file name is in the format of stat_log_xxxx_xx.txt where xxxx is the year, and xx is the month The statistics log files that are of more than one year old will be deleted by JoinNet automatically. Each line in the statistics log has the format of Thu Dec 13 17:56:01 (0:02,135289) xxxxxx where 0:02 is the hour:minute since the meeting start time 135289 is the millisecond since the meeting start time A meeting session's statistics log always starts with a line of () ==================== 1542038966 ==================== where 1542038966 is the anchor number, which can be used to find the corresponding joinnet session in the joinnet log file in this example, the corresponding joinnet log file will contain a line 4968:2.750 statistics log anchor 1542038966 This number can be used for easy cross reference between the joinnet log file and statistics log file Other lines have the following meaning and format: 1. Meeting Information () connected with mcu 67.19.188.75[67.19.188.75]:443 () info: meeting session,ssrc=0,session_index=1 These lines show the MCU's IP and port, also the joinnet's ssrc and the meeting's session index. 2. Rate Control Information - using TCP () enter media tcp thread This line indicates that the joinnet start to use TCP for the media transmission. () before leave media tcp thread, relaunch self This line indicates that the joinnet relaunch a new tcp thread when the current tcp media connection is broken. () leave media tcp thread This line indicates that the joinnet finish a tcp media connection. () tcp_media_rate_control,worst_command = 1,targetrate = 54000,queue=0,avg=0 When joinnet uses TCP for media, this line shows how the rate control decide the sending target rate (every 2-5 seconds). where worst_command could be 1(to increase target rate); 0(keep same); -1(to decrease target rate); -2(local queue drop, to decrease target rate fast) targetrate: the new sending target rate for video queue=t: t is queue size avg=a: a is the moving-average queue size along time 3. Rate Control Information - using UDP () rate_control,worst_command = 1,targetrate = 54000 When joinnet uses UDP for media, the rate control is done by MCU. This line shows the result (every 2-5 seconds). where worst_command could be 1(to increase target rate); 0(keep same); -1(to decrease target rate); -2(5% or more loss detected, to decrease target rate fast) targetrate: the new sending target rate for video 4. Total Raw Receiving Rate () total_raw_audio_recv_rate,54000 () total_raw_video_recv_rate,97000 These examples show that the total audio receiving rate is 54000bps and total video receiving rate is 97000bps 5. Audio Info () audio_send_rate,7543 () audio_send_rate2,7517 () audio_recv_rate(channel 1,ssrc 1) 54000 () audio_loss_rate(channel 1,ssrc 1),2345 () audio_jitter(channel 1,ssrc 1),13423(unit: 1/100ms) These examples show that audio sending rate(UDP) is 7543bps; audio sending rate(TCP) is 7517bps; For user ssrc 1 at channel 1, audio receiving rate 54000bps; For user ssrc 1 at channel 1, audio loss rate 23.45%; For user ssrc 1 at channel 1, audio jitter 134.23ms 6. Video Info () video_send_rate,54000 () video_send_rate2,36000 () video_recv_rate(channel 1,ssrc 1),54000 () video_loss_rate(channel 1,ssrc 1),2345 These examples show that video sending rate(UDP) is 54000bps; video sending rate(TCP) is 36000bps; For user ssrc 1 at channel 1, video receiving rate 54000bps; For user ssrc 1 at channel 1, video loss rate of 23.45% 7. AppData Channel () appdata_new_channel,0,Shared Desktop{E5AF1A56-E29C-4BA6-839A-24C2F30EED02},max_rate=1280000,ssrc=0 This line indicate that user ssrc 0 start a new appdata channel 0 for Shared Desktop{E5AF1A56-E29C-4BA6-839A-24C2F30EED02} with max rate 1280000bps () appdata_set_recv_prio(channel 0) 12 This line indicate that the joinnet only receive data of priority level 12 or higher () appdata channel 1, data rate 54000 -> 56000 This line show the joinnet's rate control algorithm adjusts the appdata channel 1's sending rate from 54000 to 56000bps () appdata_send_rate,54000 () appdata_send_rate2,36000 () appdata_recv_rate(channel 1,ssrc 1),54000 () appdata_loss_rate(channel 1,ssrc 1),2345 These examples show that appdata sending rate(UDP) is 54000bps; appdata sending rate(TCP) is 36000bps; For user ssrc 1 at channel 1, appdata receiving rate 54000bps; For user ssrc 1 at channel 1, appdata loss rate of 23.45% Note, when appdata_loss_rate shows non-zero value while the appdata_set_recv_prio also shows non-zero value, the loss may not be caused by the network: the loss could be caused by the joinnet's skipping of lower priority data.