FAQ. Problems with object activity: различия между версиями
Нет описания правки |
|||
(не показаны 2 промежуточные версии этого же участника) | |||
Строка 1: | Строка 1: | ||
[[FAQ._Problems_with_object_activity|en]] | [[FAQ._Проблемы_с_активностью_объектов|ru]] | [[FAQ._Problems_with_object_activity|en]] | [[FAQ._Проблемы_с_активностью_объектов|ru]] | ||
'''In the equipment list - some/all equipment is shown in red as inactive. Open the equipment card - ping is performed. The equipment in the list turns green. After 15 minutes it's red again.''' | |||
The web-interface of the system itself does not control which equipment is active and which is not. Only when the user acts actively ''(e.g. by opening the equipment card)'' does the system find out what is wrong with the device - is it active or not? Read the article "[[Activity]]". | |||
To have always up-to-date information about the hardware you need to put modules which do that. In particular, the [[usm_checker_EN|usm_checker]] module. It is this module which you'd better use and put into your system cron. It checks whether the device is active and then the user will always see the current information in the web-interface. |
Текущая версия от 16:38, 29 марта 2024
In the equipment list - some/all equipment is shown in red as inactive. Open the equipment card - ping is performed. The equipment in the list turns green. After 15 minutes it's red again.
The web-interface of the system itself does not control which equipment is active and which is not. Only when the user acts actively (e.g. by opening the equipment card) does the system find out what is wrong with the device - is it active or not? Read the article "Activity".
To have always up-to-date information about the hardware you need to put modules which do that. In particular, the usm_checker module. It is this module which you'd better use and put into your system cron. It checks whether the device is active and then the user will always see the current information in the web-interface.