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...
Designing IP Broadcast Systems - The Book
Designing IP Broadcast Systems is another massive body of research driven work - with over 27,000 words in 18 articles, in a free 84 page eBook. It provides extensive insight into the technology and engineering methodology required to create practical IP based broadcast…
Demands On Production With HDR & WCG
The adoption of HDR requires adjustments in workflow that place different requirements on both people and technology, especially when multiple formats are required simultaneously.
If It Ain’t Broke Still Fix It: Part 2 - Security
The old broadcasting adage: ‘if it ain’t broke don’t fix it’ is no longer relevant and potentially highly dangerous, especially when we consider the security implications of not updating software and operating systems.
Standards: Part 21 - The MPEG, AES & Other Containers
Here we discuss how raw essence data needs to be serialized so it can be stored in media container files. We also describe the various media container file formats and their evolution.
NDI For Broadcast: Part 3 – Bridging The Gap
This third and for now, final part of our mini-series exploring NDI and its place in broadcast infrastructure moves on to a trio of tools released with NDI 5.0 which are all aimed at facilitating remote and collaborative workflows; NDI Audio,…