Revma Events

TABLE OF CONTENTS

• Events
  • multi_link_start
  • multi_link_stop
  • multi_link_swapped
  • link_broadcast_start
  • link_broadcast_stop 
  • stream_start 
  • stream_stop
  • relay_link_start
  • relay_link_stop
  •  
  • link_metadata
    
    
• Events example scenarios
  
  
• Loudness events

In the revma Events page, one can view the daily logs that take place in regards to specific actions/events for a station. These include source connections/disconnections, source swaps, metadata updates and more.

With the option “include all station relays” enabled, available only under primary stations, one can also view all non metadata events for all relay stations “under” that station. Aside from being able to view the events of the primary and the relay stations in the same page, the events can be filtered per stream, timestamp, event type and details, while their loudness chart can also be toggled between the primary and relay streams.

Additionally, a user has the option to only view the non metadata related events; this can be achieved by keeping the "Hide metadata updates" option ticked.

Events are represented in the timezone set in the station's settings

Noticing double event entries is expected, as both Revma streaming clusters populate them. 

For streaming only stations, the events will be double.
For relay and loop channel stations, there will be events when at least one listener from Europe or at least one from the rest of the world is connected. When listeners from both mentioned areas are connected, the events will be double.

The events might appear in a different order as the one expected, as they might correspond to the same timestamp. For example, a “multi_link_swapped” event might appear prior to the “multi_link_stop” event that caused the swap, but with the same timestamp.

Events

You can sort the events by pages of 10, 20, 30, 50 & 100; You can also search for specific event types, timestamps etc. via the search bar.

Here is a list of the Event logs and their whereabouts:

multi_link_start

• Description: A source (Primary, Failover or Failover Relay URL) is connected to the station. 
• Details: “Name” contains the source’s name (Primary, Failover or Failover Relay URL). “Cid” contains the connection’s channel id .

multi_link_stop

• Description: A source (Primary, Failover or Failover relay URL) is disconnected from the station. 
• Details: “Name” contains the source’s name (Primary, Failover or Failover Relay URL). “Cid” contains the connection’s channel id. “Reason” contains the reason of the disconnection, which can include:
  • none → if the source was disconnected by the user
  • shutdown → When a stream using a Failover Relay URL as its source has no listeners active or when Failover Relay URL stream becomes idle.
  • ALL_IDLE → Failover URL connection closes because the connection was considered IDLE due to no data being received.
  • unnecessary → Failover Relay URL is no longer needed, as a primary or failover connection has connected and become active.
  • URL changed → Failover Relay URL has changed, the current connection is closed and it should reconnect to the new URL. “URL changed” event also appears when the failover URL is removed.
  • IDLE → HLS encoder connection is disconnected abruptly and stops sending data to Revma.

multi_link_swapped

• Description: The source of the stream is swapped from one to another (e.g. from Primary to Failover). Primary, Failover and Failover relay URL are included as sources. This may happen for various reasons:
  • A source is disconnected
  • A source is silent 
  • A source that was previously silent becomes audible
  • Primary source connects and “persistence to failover source” is set to “switch to primary after # minutes”
  • “Persistence to failover source” changed from “always persistent” to “switch to primary after # minutes” or “switch to primary after # minutes” is changed to a lesser value.
• Details: “Active” contains the source that became the active one after the swap. “Swapped” contains the source that the stream swapped from, causing it to not be the active one any longer. “ActiveCid” contains the channel’s id of the active source’s connection (if any). “SwappedCid” contains the channel’s id of the swapped source’s connection (if any). “Reason” contains the reason of the swap, which can include:
  • input disconnected → the previously active source was disconnected
  • input connected → the source with higher priority has connected
  • input became silent → the previously active source was streaming silence for at least one minute
  • input became audible → a connected but inactive source that was previously streaming silence and has a “higher priority”, becomes audible. “Higher priority” can mean that the previously active source is a Failover relay URL or the Failover and “persistence to failover source” is set to “switch to primary after # minutes”
  • stickiness time achieved → the source swaps from Failover to Primary due to “persistence to failover source” being set to “switch to primary after # minutes”. More on thishere.
  • stickiness time updated →  the source swaps from Failover to Primary due to “persistence to failover source” being changed from “always  persistent” to “switch to primary after # minutes” or “switch to primary after # minutes” is changed to a lesser value. More on thishere.

multi_link_swapped event will also appear when a source connects and becomes the active one, even if there was no source connected and active previously. In these cases, the details' field “swapped” will be “none”.

multi_link_swapped event reason will be ‘input connected’ and not ‘stickiness time achieved’ in cases where ‘switch to primary after # minutes’ is set to '0’ and primary source connects, taking over from failover.

When a primary or failover encoder source disconnects and the source that becomes active is the failover URL, the “swapped” field of the “multi_link_swapped” events will be “none”; this is because this process is not technically a swap, but a stream that “closes” and “opens” again, even if the listener experience resembles a swap. 


This is not the case vice versa: when the failover URL is active and an encoder source connects, the  “swapped” field of the “multi_link_swapped” events will be the failover URL; this is because the stream never “closes” but the source with higher priority connect

Cid is simply a random identifier that represents the uniqueness of a connection. It can be of use internally only in certain required cases.

multi_link_{***} events are only present for streaming only stations.

link_broadcast_start

Description: the station accepts a source connection (encoder, relay, failover UL). This event will appear only for the first connection that the station accepts. 

In this sense, this event will appear when a source first connects to a streaming only station and it will also appear when the first listener connects to a relay or loop channel station. If the source is an encoder, the “link_broadcast_start” will appear at the time of the encoder connection. If the source is a relay or failover relay URL, the “link_broadcast_start” will appear at the time of the source’s connection as long as there is at least one active listener; if not, the “link_broaddcast_start” will appear as soon as the first listener connects.

This event has not details.

link_broadcast_stop

• Description: the station’s source disconnects. If there are multiple sources (i.e. primary and failover) this event will appear when the last one disconnects.
• Details: this event might contain the reason for this disconnection 
  • STREAM_IDLE will appear when the stream was idle and terminated. This occurs when a relay or loop channel station has no listener active for anywhere in between 30 and 40 seconds. It will also occur when a streaming only station with Failover Relay URL as its source has no listener active for anywhere in between 30 and 40 seconds or the Failover Relay URL stream delivers no data for 30-40 seconds.
  • STREAM_CONTROL will appear when the stream is restarted. Appart from the “Restart” option in a station’s Settings → Advanced tab, this action can occur by reseting the mount password or updating any of the following stream configuration settings: Burst buffer, Stream history, Delay buffer time. This event will appear for streaming only stations and simple relays that have at least one listener from outside of Europe. Furthermore, this event will never be double.

stream_start 

Description: when the first listener activates a stream that was inactive. This only applies for streams that use the transcoding cluster: loop channel and transcoding relay stations.

stream_stop

Description: the stream becomes inactive (0 listeners). This only applies for streams that use the transcoding cluster: loop channel and transcoding relay stations.

relay_link_start

• Description: The relay link source is connected. This applies only in transcoding relays and loop channel stations with a relay link as their source. Requires a connected listener.
• Details
  • “Uri” contains the source URL that was connected to this stream
  • “Swapped” dictates if there was a relay source that swapped to another in the case that there were multiple ones configured (via Failover relay link). In the “relay_link_start” event, this will always be “false”.

relay_link_stop

• Description: The relay link source is disconnected. This applies only in transcoding relays and loop channel stations with a relay link as their source. Requires a connected listener.
• Details
  • “Uri” contains the source URL that was disconnected from this stream 
  • “Swapped” dictates if there was a relay source that swapped to another in the case that there were multiple ones configured (via Failover relay link). In the “relay_link_stop” event, this will be “true” in cases where a Failover relay link was swapped to the primary Relay link or a Failover relay link of higher priority due to it becoming active.

Failover relay link is not to be confused with Failover Relay URL. The Failover relay link represents the additional URLs that can be added in the “primary Relay link” field of a stream, which will take over in case the “primary Relay link” or other Failover relay links of higher priority become inactive. 

The “relay_link_stop” event does not appear when a relay link is disabled via the UI field “enable primary relay” nor does it appear when the stream becomes idle due to no listeners being connected. It will appear when the stream used as the source (relay) is “closed”; for example, if the only encoder connected to it disconnects.

link_metadata

• Description: updates and logs the metadata of each playing track.
• Details
  • “title” contains the information of the track’s name
  • “artist” contains the information of the artist’s name

Events example scenarios

For the article’s purposes, the below scenarios will have single events instead of double.

Scenario 1: Primary encoder connects → Metadata transmitted → Failover encoder connects → Metadata transmitted → Primary encoder disconnects → Source swapped to failover → Metadata transmitted (failover) → Failover encoder disconnects → Source changes to failover URL → Metadata transmitted (from failover URL)

Scenario 2: Primary encoder disconnects → Source changes to failover URL → Metadata transmitted (from failover URL) → Failover URL stops - no listener.

Scenario 3: Primary encoder streams silence and source swaps to Failover → Metadata transmitted → Primary encoder begins streaming audio and source swaps to Primary → Metadata transmitted

Scenario 4: Primary encoder disconnects → source swaps to Failover → Metadata transmitted → Primary encoder connects → source swaps to Primary when “persistence to failover source” is set to “switch to primary after 5 minutes” and the 5 minutes are completed → Metadata transmitted

Scenario 5: First listener connects to “Loop channel” station → Playlist airs and transmits metadata → relay link enabled for “Loop channel” station → Relay stream source airs and transmits metadata → relay link disabled for “Loop channel” station → Playlist airs and transmits metadata → last listener disconnects from station → stream becomes “idle”

Loudness events

This graph represents the loudness events of a station shown in LUFS (Loudness Units Full Scale). The lower the LUFS, the lower the loudness (eg. -13 is louder than -15).

Silence is present when the LUFS are lower than -50.  

• If silence is present for at least 1 minute, “switch source on silence” is active and there is another audible encoder source connected, the source will switch; more on this here. 
• If silence is present for at least 2 minutes, no other source is connected and/or “switch source on silence” is not active, a user’s email registered for stream alerts via the settings will receive a “silence detected” email. More information on Stream Alerts here.