An MES system performance and log data monitoring method

Abstract

The invention relates to an MES system performance and log data monitoring method. The MES system performance and log data monitoring method comprises the following steps of obtaining page data of logmonitoring; transmitting the page data; binding and processing the request data and the request data; performing relational constraint on the data, performing serialized encryption, and compressing the log data into a log file in a specific format. According to the method, a serialized encryption mode is adopted for downloading of the log file, a user only needs to select time for downloading andcan download log information, the log user cannot open or modify the log information and can analyze the log information only through a software supplier, analyzed data are assembled, and the problemcan be located and solved in the fastest time.

Description

technical field [0001] The invention relates to the technical field of mold manufacturing control, in particular to a method for monitoring MES system performance and log data. Background technique [0002] When the mold industry applies production management software such as ERP and MES, it is usually not allowed to connect to the external network in the customer environment, and the server is isolated inside the customer company. Occurs: ①The performance is not stable enough, and cannot be detected in time, which will affect the user experience and functional defects, and even cause serious consequences such as machine jams, and cannot be detected in time; ②An error occurs in the user operating system, which involves user data security, and the database cannot be provided to the ERP provider , if the reason is analyzed only through the background log recorded by the system, the first log file is large, and the second text analysis is relatively slow; ③The administrator use...

AI Technical Summary

Problems solved by technology

[0006] 1) After the system is abnormal, manual dictation is subjective, and it is impossible to accurately know the impact on the software;

[0007] 2) Relying on manual feedback will cause lag, and problems cannot be found in time

Email notifications may not be able to reproduce the problems that occurred before, making it impossible to trace back;

[0008] 3) The task manager that comes with the system can only see the approximate performance, because the performance of the system is viewed for the entire server, and the project is often only one or several services in the entire system

[0010] 1) The function is single, and the system performance, web server performance, and JVM virtual machine performance can be seen in real time, compared with the overall system service, but historical data cannot be recorded in detail, only real-time monitoring is possible, and system performance indicators are not recorded in real time, which cannot be traced back;

[0011] 2) Expressed in numbers, it is not intuitive enough to see which people use the most frequently and which time periods request more frequently

It is impossible to compare the performance of the system during periods of high request frequency at the same time;

[0012] 3) Once the system encounters an exception, although it can be monitored in real time and when problems occur, it cannot feed back accurate data to the software supplier, and it takes a lot of time to analyze the cause of the problem

Images