Monitoring agent setup and architecture

Qosifire agent is the front line for quality monitoring.

• You set up monitoring agent standalone software on your server node
• Agent tracks stream availability and quality parameters
• Check-over results are sent to web service to notify users and show stats

You can install it in any appropriate location. As example, that can be near your end users, so the quality tracking would be related to real-life user experience.
Learn more about use cases.

Agent architecture

When creating monitoring agent, we were inspired by microservices. This approach allows isolating separate functions from each other to minimize the impact of any possible failure.

Agent architecture has 4 microservices:

• Qosifire daemon controls the check-over tasks
• For each each stream there is a separate check-over task thread
• Notifier reads data from check-over tasks and saves all data to its database
• Reader connects Notifier and monitoring web service, to show stats and notify users about events

We rely onsystemd for controlling microservices. If any of them goes down for some reason, it's restarted by systemd automatically, all the data is safe and still saved to database for further processing. This gives a great robustness and reliability. systemd is the reason why we don't support older versions, other distros or OSes.