Детектор черного экрана/en: различия между версиями
FuzzyBot (обсуждение | вклад) (Обновление для соответствия новой версии исходной страницы.) |
FuzzyBot (обсуждение | вклад) м (FuzzyBot переименовал страницу "Детектор" черного экрана (Пользователь)/en в Детектор черного экрана/en без оставления перенаправления: Часть переводимой страницы "Детектор" черного экрана (Пользователь).) |
||
| (не показаны 4 промежуточные версии 2 участников) | |||
| Строка 3: | Строка 3: | ||
=== '''Description of the situation''' === | === '''Description of the situation''' === | ||
The user started having problems with broadcasts. During playback of broadcasts on devices, the content is interrupted, and a "black screen" appears. Because of this, the user is dissatisfied with our work and product. | The user started having problems with broadcasts. During playback of broadcasts on devices, the content is interrupted, and a "black screen" appears. Because of this, the user is dissatisfied with our work and product. | ||
[[File:Пример черного экрана в ЛК.png|thumb|An example of displaying the "Black" screen in the user's personal account|700px]] | |||
=== '''Reason''' === | === '''Reason''' === | ||
On devices operating on-site during content playback, a "black screen" appears. | On devices operating on-site during content playback, a "black screen" appears.<br>The reasons for this problem can vary. From unsupported codecs used in the video to issues with losing network connection.<br> | ||
Therefore, it was decided to make an automated solution that will more promptly notify and work with this problem. | Therefore, it was decided to make an automated solution that will more promptly notify and work with this problem. | ||
=== '''Concept of the solution''' === | === '''Concept of the solution''' === | ||
To solve the problem and automate it, it was decided to create a "Black Screen Detector." Its function is to warn us in advance about the problem that has occurred on a particular device. This feature allows us to work proactively and not wait for a customer notification about the problem. | To solve the problem and automate it, it was decided to create a "Black Screen Detector." Its function is to warn us in advance about the problem that has occurred on a particular device. This feature allows us to work proactively and not wait for a customer notification about the problem. | ||
{{Note|This functionality is not available to the user in the personal account. Contact the system administrator to enable it.|warn}} | {{Note|This functionality is not available to the user in the personal account. Contact the system administrator to enable it.|warn}} | ||
=== '''Principle of action''' === | === '''Principle of action''' === | ||
The detector works with all specialists that are used by OUR. By default, it is disabled and is enabled only on a specific network.<br> | |||
Every company working in our application has its unique ID. It can be found in the personal account. All company devices are tied to this ID.<br> | Every company working in our application has its unique ID. It can be found in the personal account. All company devices are tied to this ID.<br> | ||
When a "black screen" error occurs on one or more devices, our server sends an "event" to these devices. The device starts this "event." When launching the "event," the "detector" takes a screenshot. And this screenshot is checked for the presence of a "black screen."<br> | When a "black screen" error occurs on one or more devices, our server sends an "event" to these devices. The device starts this "event." When launching the "event," the "detector" takes a screenshot. And this screenshot is checked for the presence of a "black screen."<br> | ||
| Строка 25: | Строка 21: | ||
=== '''Final result''' === | === '''Final result''' === | ||
After receiving information about the problem, its prompt resolution begins. Thus, we always know about the problem first and do not unnecessarily worry our clients. | After receiving information about the problem, its prompt resolution begins. Thus, we always know about the problem first and do not unnecessarily worry our clients. | ||
=== '''Final result''' === | |||
After receiving information about the problem, its operational solution begins. Thus, we are always the first to know about the problem and do not make our customers worry once again. | |||
=== '''Details''' === | |||
More details can be found in the version of the document: | |||
Текущая версия от 22:10, 24 октября 2023
Description of the situation
The user started having problems with broadcasts. During playback of broadcasts on devices, the content is interrupted, and a "black screen" appears. Because of this, the user is dissatisfied with our work and product.
Reason
On devices operating on-site during content playback, a "black screen" appears.
The reasons for this problem can vary. From unsupported codecs used in the video to issues with losing network connection.
Therefore, it was decided to make an automated solution that will more promptly notify and work with this problem.
Concept of the solution
To solve the problem and automate it, it was decided to create a "Black Screen Detector." Its function is to warn us in advance about the problem that has occurred on a particular device. This feature allows us to work proactively and not wait for a customer notification about the problem.
Principle of action
The detector works with all specialists that are used by OUR. By default, it is disabled and is enabled only on a specific network.
Every company working in our application has its unique ID. It can be found in the personal account. All company devices are tied to this ID.
When a "black screen" error occurs on one or more devices, our server sends an "event" to these devices. The device starts this "event." When launching the "event," the "detector" takes a screenshot. And this screenshot is checked for the presence of a "black screen."
After starting the detector, two types of answers can be obtained:
- After launching the "event," there is no black screen - the system continues to work in normal mode.
- After launching the "event," a black screen is detected - the server sends a repeated, verification "event." The interval for resending is 10 seconds.
If option "2" confirms the presence of the problem, a notification is sent to the email from the server side.
Final result
After receiving information about the problem, its prompt resolution begins. Thus, we always know about the problem first and do not unnecessarily worry our clients.
Final result
After receiving information about the problem, its operational solution begins. Thus, we are always the first to know about the problem and do not make our customers worry once again.
Details
More details can be found in the version of the document:
