1137849 - Loop Server: Add new "status" action to POST /rooms/{token}

Status: RESOLVED FIXED

(Hello (Loop) :: Server, defect)

Description

[Adam Roach [:abr]]

+++ This bug was initially created as a clone of Bug #1137813 +++

To allow for analysis of room session states, the server should log status messages sent to the server as described in https://wiki.mozilla.org/Loop/Architecture/Rooms#Updating_Session_State

Aside from performing the same authentication and correlation that it does for "refresh" messages, the server should not have to do any additional processing for these messages other than logging their contents. Note that these log messages should include all of the reported fields (event, state, connections, sendStreams, and recvStreams). These messages also need to include room participant count (the "participants" field in the current logs) and roomConnectionId.

Comment 1

[Maire Reavy [:mreavy]]

Hi Alexis & Tarek -- Talking with abr, this bug (along with the matching client bug: bug 1137813) should give us the visibility we need to get good data out of our logs. Since better metrics is a big goal for Hello for this quarter, can you add this to your bug queue and give it a high priority?   Thanks.

Comment 2

[Alexis Metaireau (:alexis)]

Next week we will be focusing on loop-server, and hopefully we should see these bugs resolved.

Comment 3

[Mark Banner (:standard8)]

Attachment: Link to Github pull-request: https://github.com/mozilla-services/loop-server/pull/312

Moving across from bug 1137813 as it got attached to the wrong pile.

Comment 4

[Maire Reavy [:mreavy]]

FYI: Per our Loop cross team meeting today (11th of March), this will go out in the next server deployment.

Comment 5

[Alexis Metaireau (:alexis)]

https://github.com/mozilla-services/loop-server/commit/04efe1f6034dc189c8b05befdb131525a6902de7