CN107239502B - Database error daily record monitoring system based on salt - Google Patents
Database error daily record monitoring system based on salt Download PDFInfo
- Publication number
- CN107239502B CN107239502B CN201710324812.5A CN201710324812A CN107239502B CN 107239502 B CN107239502 B CN 107239502B CN 201710324812 A CN201710324812 A CN 201710324812A CN 107239502 B CN107239502 B CN 107239502B
- Authority
- CN
- China
- Prior art keywords
- salt
- database
- error log
- node
- error
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
Abstract
The Database error daily record monitoring system based on salt that the invention discloses a kind of, including Salt management ends, database node, memory node and Zabbix server-sides；Salt management ends manage salt clients, distribution instruction and file, obtain the database process information on database node, and acquisition monitoring data.Database node refers to the server for disposing database service, and regular miscut daily record sends error log to salt management ends.Memory node, by salt clients, is sent to memory node for storing error log after salt management ends are collected into all Database error daily records of all database nodes.Zabbix server-sides receive monitoring data, and are alerted according to warning strategies, and show the tendency chart of monitoring data.Present system monitoring deployment is simple, maintenance cost is low, accuracy is high and supports multiple types of data library.
Description
Technical field
The invention belongs to database monitoring fields, are mainly used in the various types of database monitorings of internet industry.
Background technology
For Internet company, database application is more and more universal, in order to improve database availability, needs for number
It disposes and monitors according to library.Conventional function monitor can not find database failure comprehensively, therefore, it is necessary to database error log into
Row monitoring, finds database problem in time, ensures database service quality.
The shortcomings that existing database monitoring system and method is：
(1) maintenance cost is high：Operating procedure is complicated, needs more manpower, maintenance cost relatively high
(2) lack automation：Almost all needs to be manually operated, and lacks automation, inefficiency
(3) monitoring scheme is complicated：Addition monitoring every time will produce a large amount of unwanted alarms, and addition operation is very complicated, lacks letter
Just property
Invention content
In view of the above-mentioned deficiencies in the prior art, it is an object of the present invention to provide a kind of Database error daily record prison based on salt
The monitoring of multitype database error log may be implemented in control system.
The purpose of the present invention is achieved through the following technical solutions：A kind of Database error daily record prison based on salt
Control system, including Salt management ends, database node, memory node and Zabbix server-sides；
Salt management ends are to manage the service of salt clients, including salt management modules, metamessage management module and adopt
Collect monitoring data module；Salt management ends manage salt clients, distribution instruction and file, obtain the data on database node
Library progress information, and acquisition monitoring data.
Database node refers to disposing the server of database service, including error log management module；Different data
Library services, and port is unique, and a salt client is disposed on each database node；Database node regular miscut day
Will sends error log to salt management ends.
For memory node for storing error log, all databases that salt management ends are collected into all database nodes are wrong
Accidentally after daily record, by salt clients, it is sent to memory node.
Zabbix server-sides are to support the monitoring server of short message and mail, including send monitoring data module and monitoring number
According to alarm module；Zabbix server-sides receive monitoring data, and are alerted according to warning strategies, and displaying monitoring data
Tendency chart.
Further, the salt management modules include：
Salt clients are disposed in all database nodes, salt management ends are deployed on an individual server.
Periodically salt is called to manage end interface, checks whether the salt clients on all database nodes are registered to
Salt management ends, it is such as unregistered, it calls salt to manage end interface, registers the salt clients；Such as registration failure, then send logical
Know to administrator.The salt clients of some database node of cancellation may be selected.
In salt management ends, whether periodic detection salt clients are sensible, such as obstructed, send notification to administrator.
Further, the metamessage management module includes：
Salt management ends periodically call metamessage management module, update the metamessage.The metamessage includes database
Node hostname, database node IP, database port and error log metamessage.Error log metamessage includes error log
Filename, memory node host name and store path；Memory node host name is the server host name where memory node.It deposits
Storage path is some absolute path of storage journal file on memory node.
First, salt management ends obtain all database node host name；Then, for each database node,
Salt management ends obtain database process all on each database node by sending instructions to salt clients；Parsing
Database process can obtain database port and data library error log file name.Meanwhile according to database node host name
Get database node IP.The database node host name, database node IP, database port and data library mistake day
Will filename is stored in meta-information file.Next, in salt management ends, meta-information file, incoming data library end are scanned
Mouthful, the user name password of database node IP and Zabbix server-side calls Zabbix to service end interface, automatically creates phase
The database host answered.Meanwhile according to the database host, parsing obtains monitoring template accordingly, is passed to the monitoring
Template, calls Zabbix to service end interface, and automatic carry monitors template, including error log acquisition item, error log accordingly
Alarm item and error log tendency chart.If some described database host does not need error log monitoring, may be used manually
Mode unloads corresponding monitoring template in the Zabbix server-side pages.Zabbix clothes can also be called according to specific requirements
Business end function, adjustment error log alarm item setting.
Further, the error log management module includes：
The incoming parameter is needed to be：Database node host name, error log file name；
Salt management ends periodically call the module, miscut daily record and transmission error log to salt management ends.
Salt management ends check error log file size according to incoming parameter by salt clients, if mistake
Log file size is more than 2MB, then the error log file is cut, meanwhile, filing error log file is sent to salt
Management end.If error log file size is less than 2MB, error log file need not be cut and sent.
Further, the acquisition monitoring data module includes：
The incoming parameter is needed to be：According to library node hostname, error log file name；
Salt management ends periodically send instructions to salt clients, and the instruction of salt client executings acquires error log number
According to returning to salt management ends.Described instruction obtains the row containing keyword error in error log file, records line number, leads to
Cross monitoring line number change monitoring error log.
Then, according to following format, monitoring data is written to monitoring data file：Database host, acquisition item, time
Stamp, collection value.The acquisition item is error log acquisition item, monitors in error log and is defined in template.Timestamp is to hold
The current time stamp of row acquisition monitoring data.Collection value is the line number containing keyword error.
Further, the storage error log module includes：
Need incoming parameter：Memory node host name, filing error log file name and store path；
Salt management ends are according to the parameter, and by salt clients, filing error log file is passed to storage section
Under the specified store path of point, if operation failure, administrator's processing is sent notification to；If operated successfully, record is as follows
In information to error log meta information table：Memory node host name, store path and error log file name, are looked into convenient for administrator
Read filing error log file information.
Further, the transmission monitoring data module includes：
The incoming parameter is needed to be：Zabbix server-sides host name, Zabbix server-sides port and monitoring data file；
Salt management ends call Zabbix to service end interface, are passed to the parameter, send monitoring data to Zabbix server-sides.
Further, the monitoring data alarm module includes：Short message and mail reception people are configured in Zabbix server-sides
Information, and warning strategies are set, then for Zabbix server-sides after receiving monitoring data, analysis monitoring data simultaneously generate announcement
It is alert, it is sent to specified recipient.
Beneficial effects of the present invention are as follows：
(1) monitoring deployment is simple：It only needs to dispose Zabbix server-sides, salt management ends and salt clients and formulates prison
Template is controlled, it is easy to operate.
(2) maintenance cost is low：After components above is disposed, for the database service newly increased, prison need not be safeguarded
Control may be implemented automatic collection and send monitoring data, maintenance cost zero.
(3) accuracy is high：This method monitors error log, can accurately reflect error log actual conditions, method is simple
And it is accurate.
(4) multiple types of data library is supported：Suitable for for relevant database and non-relational database.
Description of the drawings
Fig. 1 is the general frame figure of the Database error daily record monitoring system the present invention is based on salt；
Fig. 2 is the flow chart that modules of the present invention mutually call.
Specific implementation mode
Fig. 1 is the Database error daily record monitoring system general frame figure the present invention is based on salt.Generally include four parts：
Salt server-sides, database node, Zabbix server-sides and memory node.Salt server-sides obtain institute by salt clients
The database process for having database node parses to obtain database port according to the database process, then calls Zabbix
The automatic registration database host of end interface is serviced, according to the database process, error log cutting is periodically carried out and acquisition is wrong
Accidentally daily record analyzes each corresponding error log of database process in salt management ends, obtains monitoring data, send the monitoring
Data are to Zabbix server-sides, and finally, salt management ends send the error log by the salt clients on memory node
To memory node.
Fig. 2 is the flow chart that modules of the present invention mutually call.First, salt management modules are called, are managed in salt
The corresponding salt clients of all database nodes are registered at end, then by salt clients, are called metamessage management module, are obtained
The database process on all database nodes is taken, the database process is parsed, obtains the error log file path, is led to
Salt clients, regular call error log management module, cutting and collection error log are crossed, and is sent to salt management ends,
The error log is sent to the memory node simultaneously；By analyzing the error log, acquisition monitoring data mould is called
Block generates the monitoring data；Then it calls and sends monitoring data module, send monitoring data to Zabbix server-sides, call
Monitoring data alarm module sends error log and alerts to administrator.
The realization process of each module is described in detail below：
(1) salt management ends
Salt management ends are to manage the service of salt clients, are used for registration and unregistration salt clients, send instructions to
Salt clients.The operation that described instruction is completed generally by one or more Linux command.Salt management ends include
Salt management modules, metamessage management module and acquisition monitoring data module, function include management salt clients, and distribution refers to
Order and file obtain the database process information on database node, and acquisition monitoring data.
(2) database node
Database node refers to the server for disposing database service, these database services include common relationship type number
According to library and non-relational database, different database services, port is unique.
Include mainly error log management module, which is mainly regular miscut daily record, sends wrong day
Will is to salt management ends.
On each database node, it is required for one salt client of deployment.Salt clients are for receiving salt management
The instruction at end and file execute corresponding operation, return result to salt management ends.
(3) memory node
For memory node for storing error log, all databases that salt management ends are collected into all database nodes are wrong
Accidentally after daily record, by salt clients, it is sent to memory node.The error-logging information includes：Error log file name is deposited
Path, memory node host name are stored up, is stored in error log meta information table, for consulting history error log.
(4) Zabbix server-sides
Zabbix server-sides are a kind of monitoring servers for supporting short message and mail, receive monitoring data, and according to alarm
Strategy is alerted, and shows the tendency chart of monitoring data.Including sending monitoring data module and monitoring data alarm module,
Major function is to receive and store monitoring data and monitoring alarm.
Database host is the database service mark of Zabbix server-sides registration, each database service, database master
Machine indicates 3306 numbers on 10.1.1.11 database nodes using port _ host mode name, such as 3306_10.1.1.11
It is serviced according to library.
Monitoring template refers to the interface according to database, setting acquisition item, trigger and tendency chart, for being mounted to data
In the host of library.
Each submodule concrete function is as follows：
(1) salt management modules
Major function is to dispose salt clients in all database nodes, and salt management ends are deployed in an individual clothes
It is engaged on device.
Periodically salt is called to manage end interface, checks whether the salt clients on all database nodes are registered to
Salt management ends, detection mode are as follows：
#salt-key-L-acc | grep ' database nodes host name '
If return value is false, needs to call salt management end interfaces, register the salt clients, logon mode is such as
Under：
#salt-key-a-y ' database nodes host name '
Otherwise, the registration salt clients need not be called.If registration failure is sent notification at administrator
Reason.
If necessary to nullify the salt clients of some database node, need to manually perform as given an order：
#salt-key-d ' database nodes host name '
After the corresponding salt clients of all database nodes are all registered to salt management ends, salt management ends can
Salt clients are given to send instruction and file, complete specific operation.
Also, in salt management ends, whether periodic detection salt clients are sensible, and detection mode is as follows：
#salt' database nodes host name ' cmd.run'exit'
If return value is true, illustrate that salt clients can be sensible described in the database node host name；Otherwise, it needs
Administrator is sent notification to, artificial treatment is needed.
(2) metamessage management module
The metamessage includes database node host name, database node IP, database port and error log file
Name and error log metamessage.
Error log metamessage includes error log file name, memory node host name and store path；Memory node master
Machine name is the server host name where memory node.Store path is that some storage journal file is absolute on memory node
Path.
Salt management ends periodically call metamessage management module, update the metamessage.
First, salt management ends obtain all database node host name：Acquisition modes are as follows：
#salt-key-L | grep database node host name prefixes
Database node host name prefix is the prefix character of database node host name, and institute can be obtained by filtration based on this
Some database nodes.
Then, for each database node, salt management ends are obtained by sending instructions to salt clients per number
According to database process all on the node of library, order is as follows：
#salt ' database nodes host name ' cmd.run ' ps-ef | egrep database identifiers | egrep-v grep '
Database identifier is the mark of type of database, for example, mysql wide area information server identifiers are
Mysql, Redis wide area information server mark are redis-server.
Parsing database process can obtain database port and data library error log file name.Meanwhile according to data
Library node hostname gets database node IP.The database node host name, database node IP, database port and
Database error log file name is stored in meta-information file.
Next, in salt management ends, scanning meta-information file, incoming data library port, database node IP, and
The user name password of Zabbix server-sides calls Zabbix to service end interface, automatically creates the corresponding database host.Together
When, according to the database host, parsing obtains monitoring template accordingly, is passed to the monitoring template, calls Zabbix server-sides
Interface, automatic carry monitor template accordingly, including error log acquires item, error log alarm item and error log trend
Figure.
If some described database host does not need error log monitoring, manual mode may be used, taken in Zabbix
Business end page face unloads corresponding monitoring template.
Zabbix server-side functions, adjustment error log alarm item setting can also be called according to specific requirements.
(3) error log management module
The incoming parameter is needed to be：Database node host name, error log file name
Salt management ends periodically call the module, miscut daily record and transmission error log to salt management ends.
Salt management ends check error log file size according to incoming parameter by salt clients, if mistake
Log file size is more than 2MB, then the error log file is cut, meanwhile, filing error log file is sent to salt
Management end.Check that the instruction of error log file size is as follows：
#salt ' database nodes host name ' cmd.run ' du-s error log files name '
Explanation：The error log file name is absolute path, is not relative path.
The instruction of miscut journal file is as follows：
' cp error log file name error log file names works as the day before yesterday to #salt ' database nodes host name ' cmd.run
Qi ＆＆echo>Error log file name '
Explanation：Current date is date when described instruction executes, format yyyy-mm-dd
It is as follows to the instruction of salt management ends to send filing error log file：
#salt " database node host name " cp.push error log file name current dates
If error log file size is less than 2MB, error log file need not be cut and sent.
(4) monitoring data module is acquired
The incoming parameter is needed to be：According to library node hostname, error log file name
Salt management ends periodically send instructions to salt clients, and the instruction of salt client executings acquires error log number
According to returning to salt management ends.Described instruction is as follows：
#salt ' database nodes host name ' cmd.run ' egrep-I error error log file names | wc-l '
Explanation：Error log file name is absolute path, is not relative path
Described instruction obtains the row for containing keyword error (case-insensitive) in error log file, records line number,
By monitoring line number change monitoring error log, the monitoring method was not only simple but also efficient.
Then, according to following format, monitoring data is written to monitoring data file：
Database host acquires item timestamp collection value
The acquisition item is error log acquisition item, monitors in error log and is defined in template.
Timestamp is the current time stamp for executing acquisition monitoring data.
Collection value is line number described above, if not containing error (case-insensitive) keyword, the line number is
0。
(5) error log module is stored
Need incoming parameter：Memory node host name, filing error log file name and store path
Salt management ends are according to the parameter, and by salt clients, filing error log file is passed to storage section
Under the specified store path of point, mode of operation is as follows：
#salt' memory nodes host name ' cp.get_file salt:// filing error log file name/path/to/ returns
Shelves error log file name
Explanation：/ path/to/ indicates store path
After the completion of operation, if being returned as vacation, administrator's processing is sent notification to；If return value is true, record
In following information to error log meta information table：Memory node host name, store path and error log file name, convenient for management
Member consults filing error log file information.
(6) monitoring data module is sent
The incoming parameter is needed to be：Zabbix server-sides host name, Zabbix server-sides port and monitoring data file；
After acquiring monitoring data module trip, the monitoring data file is generated.
In salt management ends, Zabbix is called to service end interface, be passed to the parameter, sends monitoring data to Zabbix
Server-side, mode of operation are as follows：
#Zabbix_sender--Zabbix-server Zabbix server-side IP--port Zabbix server-sides port --
Input-file monitoring data files -- with-timestamps
Zabbix server-side IP and Zabbix server-sides port can be got in Zabbix server-side configuration files.
(7) monitoring data alarm module
This module is optional.It needs to configure short message and mail reception people's information in Zabbix server-sides, and alarm plan is set
Slightly, then for Zabbix server-sides after receiving monitoring data, analysis monitoring data simultaneously generate alarm, are sent to specified reception
People.
Claims (7)
1. a kind of Database error daily record monitoring system based on salt, which is characterized in that including salt management ends, database section
Point, memory node and Zabbix server-sides；
Salt management ends are to manage the service of salt clients, including salt management modules, metamessage management module and acquisition are supervised
Control data module；Salt management ends manage salt clients, distribution instruction and file, obtain database node on database into
Journey information, and acquisition monitoring data；
Database node refers to disposing the server of database service, including error log management module；Different database clothes
Business, port is unique, and a salt client is disposed on each database node；The regular miscut daily record of database node, hair
Send error log to salt management ends；
For memory node for storing error log, salt management ends are collected into all Database error days of all database nodes
After will, by salt clients, it is sent to memory node；
Zabbix server-sides are to support the monitoring server of short message and mail, including send monitoring data module and monitoring data announcement
Alert module；Zabbix server-sides receive monitoring data, and are alerted according to warning strategies, and show the trend of monitoring data
Figure；
The metamessage management module includes：
Salt management ends periodically call metamessage management module, update the metamessage；The metamessage includes database node
Host name, database node IP, database port and error log metamessage；Error log metamessage includes error log file
Name, memory node host name and store path；Memory node host name is the server host name where memory node；Store road
Diameter is some absolute path of storage journal file on memory node；
First, salt management ends obtain all database node host name；Then, for each database node, salt pipes
End is managed by sending instructions to salt clients, obtains database process all on each database node；Parse database
Process can obtain database port and data library error log file name；Meanwhile it being got according to database node host name
Database node IP；The database node host name, database node IP, database port and data library error log file
Name is stored in meta-information file；Next, in salt management ends, meta-information file, incoming data library port, database are scanned
The user name password of node IP and Zabbix server-sides calls Zabbix to service end interface, automatically creates corresponding database
Host；Meanwhile according to the database host, parsing obtains monitoring template accordingly, is passed to the monitoring template, calls Zabbix
End interface is serviced, automatic carry monitors template, including error log acquisition item, error log alarm item and error log accordingly
Tendency chart；If some described database host does not need error log monitoring, manual mode may be used, serviced in Zabbix
End page face unloads corresponding monitoring template；Zabbix server-side functions can also be called according to specific requirements, adjust mistake
Log alarming item is arranged.
2. a kind of Database error daily record monitoring system based on salt according to claim 1, which is characterized in that described
Salt management modules include：
Salt clients are disposed in all database nodes, salt management ends are deployed on an individual server；
Periodically salt is called to manage end interface, checks whether the salt clients on all database nodes are registered to salt pipes
End is managed, it is such as unregistered, it calls salt to manage end interface, registers the salt clients；Such as registration failure, then pipe is sent notification to
Reason person；The salt clients of some database node of cancellation may be selected；
In salt management ends, whether periodic detection salt clients are sensible, such as obstructed, send notification to administrator.
3. a kind of Database error daily record monitoring system based on salt according to claim 1, which is characterized in that described
Error log management module includes：
The incoming parameter is needed to be：Database node host name, error log file name；
Salt management ends periodically call the module, miscut daily record and transmission error log to salt management ends；
Salt management ends check error log file size according to incoming parameter by salt clients, if error log
File size is more than 2MB, then the error log file is cut, meanwhile, it sends filing error log file and is managed to salt
End；If error log file size is less than 2MB, error log file need not be cut and sent.
4. a kind of Database error daily record monitoring system based on salt according to claim 1, which is characterized in that described
Acquiring monitoring data module includes：
The incoming parameter is needed to be：According to library node hostname, error log file name；
Salt management ends periodically send instructions to salt clients, and the instruction of salt client executings acquires error log data, returns
Back to salt management ends；Described instruction obtains the row containing keyword error in error log file, records line number, passes through prison
Control line number change monitoring error log；
Then, according to following format, monitoring data is written to monitoring data file：Database host, acquisition item, timestamp,
Collection value；The acquisition item is error log acquisition item, monitors in error log and is defined in template；Timestamp is to execute to adopt
Collect the current time stamp of monitoring data；Collection value is the line number containing keyword error.
5. a kind of Database error daily record monitoring system based on salt according to claim 1, which is characterized in that described
Memory node includes storage error log module, and the storage error log module includes：
Need incoming parameter：Memory node host name, filing error log file name and store path；
Salt management ends are according to the parameter, by salt clients, filing error log file are passed to memory node and is referred to
Determine under store path, if operation failure, sends notification to administrator's processing；If operated successfully, following information is recorded
Into error log meta information table：Memory node host name, store path and error log file name are consulted convenient for administrator and are returned
Shelves error log file information.
6. a kind of Database error daily record monitoring system based on salt according to claim 1, which is characterized in that described
Sending monitoring data module includes：
The incoming parameter is needed to be：Zabbix server-sides host name, Zabbix server-sides port and monitoring data file；In salt
Management end calls Zabbix to service end interface, is passed to the parameter, sends monitoring data to Zabbix server-sides.
7. a kind of Database error daily record monitoring system based on salt according to claim 1, which is characterized in that described
Monitoring data alarm module includes：Short message and mail reception people's information are configured in Zabbix server-sides, and warning strategies are set,
Then for Zabbix server-sides after receiving monitoring data, analysis monitoring data simultaneously generate alarm, are sent to specified recipient.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710324812.5A CN107239502B (en) | 2017-05-10 | 2017-05-10 | Database error daily record monitoring system based on salt |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710324812.5A CN107239502B (en) | 2017-05-10 | 2017-05-10 | Database error daily record monitoring system based on salt |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107239502A CN107239502A (en) | 2017-10-10 |
| CN107239502B true CN107239502B (en) | 2018-07-17 |
Family
ID=59984216
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710324812.5A Active CN107239502B (en) | 2017-05-10 | 2017-05-10 | Database error daily record monitoring system based on salt |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107239502B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107819616A (en) * | 2017-10-30 | 2018-03-20 | 杭州安恒信息技术有限公司 | Automatically extract the method, apparatus and system of daily record |
| CN110569179A (en) * | 2018-06-06 | 2019-12-13 | 富晋精密工业（晋城）有限公司 | Data acquisition system and data acquisition method |
| CN109446024A (en) * | 2018-10-16 | 2019-03-08 | 杭州绿湾网络科技有限公司 | Using monitoring method and device |
| CN111045885A (en) * | 2019-11-11 | 2020-04-21 | 网联清算有限公司 | Database log file processing method and device and computer equipment |
| CN112506750A (en) * | 2020-09-28 | 2021-03-16 | 国网甘肃省电力公司信息通信公司 | Big data processing system for mass log analysis and early warning |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105159964A (en) * | 2015-08-24 | 2015-12-16 | 广东欧珀移动通信有限公司 | Log monitoring method and system |
| US9311144B1 (en) * | 2015-05-08 | 2016-04-12 | Xactly Corporation | Processing virtual transactions of a workflow in atomic manner in a workflow management computer system |
| CN106407350A (en) * | 2016-09-05 | 2017-02-15 | 广州视睿电子科技有限公司 | Error log information filtering method and device |
-
2017
- 2017-05-10 CN CN201710324812.5A patent/CN107239502B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9311144B1 (en) * | 2015-05-08 | 2016-04-12 | Xactly Corporation | Processing virtual transactions of a workflow in atomic manner in a workflow management computer system |
| CN105159964A (en) * | 2015-08-24 | 2015-12-16 | 广东欧珀移动通信有限公司 | Log monitoring method and system |
| CN106407350A (en) * | 2016-09-05 | 2017-02-15 | 广州视睿电子科技有限公司 | Error log information filtering method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107239502A (en) | 2017-10-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107239502B (en) | Database error daily record monitoring system based on salt | |
| CN107832196B (en) | Monitoring device and monitoring method for abnormal content of real-time log | |
| US7849227B2 (en) | Stream data processing method and computer systems | |
| CN107220304B (en) | The slow Log Administration Systems of magnanimity mongodb based on salt | |
| US7155514B1 (en) | Apparatus for event log management | |
| US7921459B2 (en) | System and method for managing security events on a network | |
| CN109800207B (en) | Log analysis method, device and equipment and computer readable storage medium | |
| CN110209518A (en) | A kind of multi-data source daily record data, which is concentrated, collects storage method and device | |
| US7676295B2 (en) | Processing information management in a plasma processing tool | |
| CN108509326B (en) | Service state statistical method and system based on nginx log | |
| CN107239379A (en) | Database performance Automatic monitoring systems based on salt | |
| US20100088197A1 (en) | Systems and methods for generating remote system inventory capable of differential update reports | |
| EP2639709B1 (en) | Method and system for storing and retrieving data | |
| US6765990B2 (en) | Database driven methods and systems for real time call tracing | |
| CN106940677A (en) | One kind application daily record data alarm method and device | |
| CN107659443A (en) | The monitoring method and its system of a kind of real time business | |
| CN105227367A (en) | A kind of warning analysis processing method of low delay | |
| US20100174386A1 (en) | Method and apparatus for routing data in an automatic identification system | |
| CN112052247A (en) | Index updating system, method and device of search engine, electronic equipment and storage medium | |
| US7099736B2 (en) | Operation management system | |
| CN115269515B (en) | Processing method for searching specified target document data | |
| CN113037549A (en) | Operation and maintenance environment warning method | |
| CN114595129A (en) | Configurable multi-dimensional data monitoring method and device and storage medium | |
| CN113055213A (en) | Alarm information management method, alarm information management system and server | |
| JP2003233417A (en) | Data communication device and its method, and data communication program and recording medium recorded thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220728 Address after: 310000 room 801, 8th floor, building 1, No. 108 Xiangyuan Road, Gongshu District, Hangzhou City, Zhejiang Province Patentee after: Hangzhou mingshitang Digital Technology Co.,Ltd. Address before: 310019 room 507, floor 5, building A15, No. 9, Jiusheng Road, Jianggan District, Hangzhou, Zhejiang Province Patentee before: HANGZHOU MISTONG EDUCATION SCIENCE & TECHNOLOGY DEVELOPMENT CO.,LTD. |