Conflicts, errors, statistics and monitoring

By 7R5 | Broadcast TV | 21 May 2020


All systems have weaknesses, even those that are apparently more robust and tested

this is what I came across, a system that has been in use for 10 years and that has started to give problems for a day ... excluding hw / sw faults, what has changed in use?

from this moment an important daily and statistical monitoring analysis began, many variables, many false positives ...


a1c1dd15115221f5a3696d3359f9d69d53913ba552c8bc15ec171cfb440ad1eb.png

 


here we discover temporal conflicts between different events that make the same peripheral but the first chart is perplexing, the problem occurs even when there are few conflicts ... so how come the problem exists and persists?

 

93c1824e39b7ddc0d29645013cc67dfee11d15e4fc23432aa9150d74561a7af2.png

 

a second analysis differentiates the types of conflicts but also here without great success if not that of identifying exactly the typologies and intervening surreptitiously in the

 

b62ea16545d9ebba7c24f9ad9ddfb94d19843ce3565d18aa376447b0593802f7.png

 

To simplify the operation and make it accessible to everyone, I created a graph that in real time reads and displays all the conflicts, the thresholds are checked on the statistics and are still often varied but it is a basis on which to work

 

a1cb0ed385ca091c03d7c16d75306135a25bb19e682111f6881ec7560ce0072a.png

thanks to this monitoring system and on statistics you can see that the system sum of errors of several days but we still don't know exactly how many, we started from 3 days now we are at 5 ... the monitoring continues!

How do you rate this article?


0

0


Broadcast TV
Broadcast TV

Info on television production technique and new broadcast developments

Send a $0.01 microtip in crypto to the author, and earn yourself as you read!

20% to author / 80% to me.
We pay the tips from our rewards pool.