Globecast Deploys Elecard Boro Monitoring System
Elecard’s Boro monitoring system is part of its Globecast’s cloud playout infrastructure as it migrates customers from traditional hardware-based operations to the cloud.
Boro is described as a client-server application consisting of two parts: software probes and a server designed to collect and process statistics. Boro probes were installed both on Windows and Linux virtual machines, as well as various workstations on-premise. The system is used to monitor 75 channels in SRT, RTP and HLS formats. Boro supports end-user managed installations (without an intermediary) for ad hoc placements throughout infrastructure. Each probe has been optimized for raising alarms pertinent to a particular location, and in a particular format. Boro was used as a troubleshooting tool during initial POC tests and as a full-time monitoring system for operators to check activities in the cloud and gain full QoS confidence for related terrestrial endpoints.
Chris Pulis, CTO Globecast Americas, said, “We knew that finding an all-encompassing solution for quality control was paramount for the success of cloud playout projects. With many cloud services built in data centers with shared foundations, we expected a greater number of resources were needed during the initial tests. Therefore, the ideal solution needed to be a flexible, pay-per-usage cost-model to support a greater number of resources on-demand, that would diminish over time once we got closer to the final assembly. Boro was the best fit because it delivered on our technical requirements. It is a very powerful lightweight tool in a software package that can be optimized per use-case by shutting off unnecessary functions, which further reduces overhead and operational costs.”
Elecard support provided the guidance to combine and tag services at different locations. This meant that operators could use a consolidated view of the service bouquet delineated by probes, regardless of their location, rather than seeing the same bouquet across each individual probe. This is said to improve the bottom line to pinpoint trouble areas providing faster reaction times and lessening consequence of human errors, as opposed to manual fetch of event data locally on the virtual machine.
The use of the internet for authentication and collection of logs is a part of this solution, making the user less focused on having to recall probe locations, IP addresses, and passwords. This architecture also means that users could share data and remote access to probes making collaboration with trusted partners a painless process.
Anton Proshutya, Elecard Boro Product Manager: "The main distinguishing feature of our solution is quick start and integration. We try to make Boro simple and easy to use. We are happy to hear that thanks to the user-friendly interface, customers have no trouble launching probes and start monitoring without delay. This project has allowed us to make sure that probes work well in the cloud.”
"The biggest benefit of this solution is the intuitive user interface, and the immediate practicality it provides with the minimal amount of training needed to operate,” Proshutya said. “We found the pricing model to be very fair given the totality of features offered. And with pricing tied to service counts rather than number of instances, eliminated any stress factors around costly one-off deployments in critical areas.”
You might also like...
HDR & WCG For Broadcast: Part 3 - Achieving Simultaneous HDR-SDR Workflows
Welcome to Part 3 of ‘HDR & WCG For Broadcast’ - a major 10 article exploration of the science and practical applications of all aspects of High Dynamic Range and Wide Color Gamut for broadcast production. Part 3 discusses the creative challenges of HDR…
IP Security For Broadcasters: Part 4 - MACsec Explained
IPsec and VPN provide much improved security over untrusted networks such as the internet. However, security may need to improve within a local area network, and to achieve this we have MACsec in our arsenal of security solutions.
Standards: Part 23 - Media Types Vs MIME Types
Media Types describe the container and content format when delivering media over a network. Historically they were described as MIME Types.
Building Software Defined Infrastructure: Part 1 - System Topologies
Welcome to Part 1 of Building Software Defined Infrastructure - a new multi-part content collection from Tony Orme. This series is for broadcast engineering & IT teams seeking to deepen their technical understanding of the microservices based IT technologies that are…
IP Security For Broadcasters: Part 3 - IPsec Explained
One of the great advantages of the internet is that it relies on open standards that promote routing of IP packets between multiple networks. But this provides many challenges when considering security. The good news is that we have solutions…