This tutorial walks through the use of AudioEngine to monitor your stream and configure alerts


Once the account is setup by our deployments team, you will first select Publishers tab from the dashboard menu on the left side of the screen.



Next, you'll want to select the resources that you would like to be monitored. Click into the Monitoring tab and then the Select resources button.



Select which ingest servers and which egress servers you want to monitor from the drop-down list. The ingest server will first receive the audio feed and will then send it to the egress servers. Be sure to click Save to commit your selection.


These servers are distributed for load balancing purposes and will be located in different geographic areas. In case one of the egress servers goes down, the other one will take over. Normally you’d want to monitor all of them, but we do provide the option to exclude some egress servers based on your preference.



The next step will be to access the Configure Alerts screen by clicking the named button. Here, you can set the tolerance before an alert should be sent to a list of desired email addresses



Our monitoring tool checks the station every minute. When it detects that a station is down or that the metadata has not changed, the station will be flagged and (depending on the interval) it will notify the alert recipients. For example, if the alert is set to be received immediately, notifications are sent straight away. 


If you have a different interval (10 minutes for metadata, for example), it will keep checking the station every minute. Following this example scenario, if that resource is still down after 10 minutes then it will fire a separate e-mail for each resource that is down. 


Another example is that you can monitor by separate resources. You can have two egress servers configured for e-mail notifications. If the station is only down on one egress server, a single e-mail will fire for that particular server. If the station is down on both egress servers, two e-mails will fire, one for each server. 


The Do Not Disturb feature will disable the notification for a specific time frame. The most common use case for this feature is when the station is being put offline deliberately.



Outcomes of having multiple resources selected

In the example below we have 3 ingest servers and 2 egress servers selected for monitoring.




The last feature of the Monitoring tool is using Enter maintenance mode. Clicking on this button prompts you to confirm disabling your configured alerts until the maintenance mode is manually lifted.