Wowza API can promote to track its data just in time. But by default all we have is a special monitoring webpage at the Wowza Streaming Engine Manager. Configuration of your own monitoring would be the best solution for streaming infrastructure control. By means of JMX console we can get as much data as possible for Java application. By means of Zabbix we can visualize all data we’ve got from JMX.
HTTPS means HTTP implementation over Secure Sockets Layer (SSL) protocol. This protocol is able to encrypt HTTP streaming traffic such as HLS, HDS, and Smooth. I explained HTTPS deployment in webserver at my post, but media streaming field is a little bit different for this goal.
There is a myriad of webpages about this question. But here is just my way of look at it. Multicast customization is not too tricky, but I’d like to explain how and why it works.
Many people think that the problem of application performance, security and networking lies in supported services. Like Nginx is proxying too slow or remote DBMS cannot see my network. Frequently the problem in OS. Default values of system settings can restrict our environment to make the service jobs quick and simple. The best way to change your system configuration – change the system variables.
