Logging and monitoring Material Management
Service
Material Management uses json based logging, the way of the logging is defined by IAS
In IAS all logs are logged by our application to stdout and then saved in docker’s log directory on the host machine (VM (Virtual Machine), […]).
Filebeat collects these and parses them (JSON, when Logging guidelines are implemented in all IAS Modules).
MatClimateControl & MaterialInfoPanel
The MatClimateControl & MaterialInfoPanel by default are logging to the windows EventLog. In case its required to log to a different target, it is possible to use the OpCon.Diagnostics and the MES EventLogger Service.
In order to switch the default behaviour and target the EventLogger service, the OpCon.Diagnostics.Config.xml configuration file has to be edited under '[DRIVE]:\OpCon\Config\MatClimateControl' or '[DRIVE]:\OpCon\Config\MaterialInfoPanel' respectively, where the commented out section has to be re-enabled:
MaterialInfoPanel system health logging
MSD InfoPanel System Health Events are logged using the MES EventLogger- service events. Two cyclical messages are written to the EventLog:
-
SYSTEM_ALIVE — The MSD InfoPanel application is running.
-
SYSTEM_OK — The MSD InfoPanel application is running and is functioning properly.
If the SYSTEM_ALIVE message does not appear, this usually means:
-
MSD InfoAgent is not running
-
The EventLogger service is not running
If the SYSTEM_OK message does not appear, this usually means:
-
A connection cannot be established to Material Management
-
Material Management is not providing any valid data records
-
The material being monitored is blocked
-
The EventLogger service is not running