CN107239502A - Database error daily record monitoring system based on salt - Google Patents
Database error daily record monitoring system based on salt Download PDFInfo
- Publication number
- CN107239502A CN107239502A CN201710324812.5A CN201710324812A CN107239502A CN 107239502 A CN107239502 A CN 107239502A CN 201710324812 A CN201710324812 A CN 201710324812A CN 107239502 A CN107239502 A CN 107239502A
- 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.)
- Granted
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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a kind of Database error daily record monitoring system based on salt, including Salt management ends, database node, memory node and Zabbix service ends；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 is used to store error log, and salt management ends are collected into after all Database error daily records of all database nodes, by salt clients, are sent to memory node.Zabbix service ends 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, the degree of accuracy is high and supports multiple types of data storehouse.
Description
Technical field
The invention belongs to database monitoring field, the various types of database monitorings of internet industry are mainly used in.
Background technology
For Internet firm, database application is increasingly popularized, in order to improve database availability, it is necessary to be number
Dispose and monitor according to storehouse.Conventional function monitor can not find database failure comprehensively, accordingly, it would be desirable to enter to database error log
Row monitoring, finds database problem, it is ensured that database service quality in time.
The shortcoming of existing database monitoring system and method is：
(1) maintenance cost is high：Operating procedure complexity is, it is necessary to which more manpower, maintenance cost is higher
(2) automation is lacked：Almost all needs are manually operated, lack automation, inefficiency
(3) monitoring scheme is complicated：Addition monitoring every time, can produce a large amount of unwanted alarms, and addition operation is very complicated, lacks letter
Just property
The content of the invention
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
Control system, it is possible to achieve multitype database error log is monitored.
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 service ends；
Salt management ends are to manage the service of salt clients, including salt management modules, metamessage management module and are adopted
Collect monitoring data module；Salt management ends manage salt clients, distribution instruction and file, obtain the data on database node
Storehouse progress information, and acquisition monitoring data.
Database node refers to the server for disposing database service, including error log management module；Different data
Storehouse is serviced, and port is unique, and a salt client is disposed on each database node；The regular miscut day of database node
Will, sends error log to salt management ends.
Memory node is used to store error log, and all databases that salt management ends are collected into all database nodes are wrong
By mistake after daily record, by salt clients, memory node is sent to.
Zabbix service ends are to support the monitoring server of short message and mail, including send monitoring data module and monitoring number
According to alarm module；Zabbix service ends 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 a single server.
Periodically call salt to manage end interface, check whether the salt clients on all database nodes are registered to
Salt management ends, it is such as unregistered, call salt to manage end interface, register the salt clients；Such as registration failure, then send logical
Know to keeper.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 keeper.
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.Deposit
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 processes all on each database node by sending instructions to salt clients；Parsing
Database process can obtain database port and data storehouse 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 storehouse mistake day
Will filename is stored in meta-information file.Next, in salt management ends, scanning meta-information file, incoming data storehouse end
The user name password of mouth, database node IP, and Zabbix service ends, calls Zabbix to service end interface, automatically creates phase
The database host answered.Meanwhile, according to the database host, parsing obtains monitoring template accordingly, the incoming monitoring
Template, calls Zabbix to service end interface, and automatic carry monitors template, including error log collection item, error log accordingly
Alarm item and error log tendency chart., can be using manual if some described database host does not need error log monitoring
Mode, in the corresponding monitoring template of Zabbix service ends page unloading.According to real needs Zabbix can also be called to take
Business end function, adjustment error log alarm item is set.
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 are according to incoming parameter, by salt clients, check error log file size, if mistake
Log file size is more than 2MB, then the cutting error log file, meanwhile, filing error log file is sent to salt
Management end.If error log file size is less than 2MB, it is not necessary to cutting and transmission error log file.
Further, the acquisition monitoring data module includes：
The incoming parameter is needed to be：According to storehouse node hostname, error log file name；
Salt management ends periodically send instructions to salt clients, and the instruction of salt client executings gathers error log number
According to returning to salt management ends.The 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 form, monitoring data is written to monitoring data file：Database host, collection item, time
Stamp, collection value.The collection item is error log collection item, is defined in error log monitoring 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；
Filing error log file, by salt clients, is passed to storage section by Salt management ends according to the parameter
Under the specified store path of point, if operation failure, keeper's processing is sent notification to；If operated successfully, then record is as follows
Information is into error log meta information table：Memory node host name, store path and error log file name, are easy to keeper to look into
Read filing error log file information.
Further, the transmission monitoring data module includes：
The incoming parameter is needed to be：Zabbix service ends host name, Zabbix service ends port and monitoring data file；
Salt management ends, call Zabbix to service end interface, and the incoming parameter sends monitoring data to Zabbix service ends.
Further, the monitoring data alarm module includes：Short message and mail reception people are configured in Zabbix service ends
Information, and warning strategies are set, then Zabbix service ends are after monitoring data is received, and analysis monitoring data simultaneously produce announcement
It is alert, it is sent to the recipient specified.
Beneficial effects of the present invention are as follows：
(1) monitoring deployment is simple：Only need to deployment Zabbix service ends, salt management ends and salt clients and formulate prison
Template is controlled, it is simple to operate.
(2) maintenance cost is low：After components above deployment is finished, for the database service newly increased, it is not necessary to safeguard prison
Control, it is possible to achieve automatic data collection and transmission monitoring data, maintenance cost is zero.
(3) degree of 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 storehouse is supported：Suitable for for relevant database and non-relational database.
Brief description of the drawings
Fig. 1 is the general frame figure of the Database error daily record monitoring system of the invention based on salt；
Fig. 2 is the flow chart that modules of the present invention are mutually called.
Embodiment
Fig. 1 is the Database error daily record monitoring system general frame figure of the invention based on salt.Generally include four parts：
Salt service ends, database node, Zabbix service ends and memory node.Salt service ends obtain institute by salt clients
There is the database process of database node, database port is obtained according to database process parsing, Zabbix is then called
The automatic registration database main frame of end interface is serviced, according to the database process, error log cutting is periodically carried out and collection is wrong
Daily record by mistake, each corresponding error log of database process is analyzed in salt management ends, obtains monitoring data, sends the monitoring
Data are to Zabbix service ends, 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 are mutually called.First, salt management modules are called, in salt management
The corresponding salt clients of end all database nodes of registration, then by salt clients, call metamessage management module, obtain
The database process on all database nodes is taken, the database process is parsed, obtains the error log file path, is led to
Cross salt clients, regular call error log management module and collects error log at cutting, and be 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, produces the monitoring data；Then transmission monitoring data module is called, monitoring data is sent to Zabbix service ends, calls
Monitoring data alarm module, sends error log and alerts to keeper.
The implementation process of each module is described in detail below：
(1) salt management ends
Salt management ends are to manage the service of salt clients, for registration and unregistration salt clients, are sent instructions to
Salt clients.The operation that the 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, and these database services include conventional relationship type number
According to storehouse and non-relational database, different database services, port is unique.
Mainly include error log management module, the functions of modules is mainly regular miscut daily record, send wrong day
Will is to salt management ends.
On each database node, it is required for disposing a salt client.Salt clients are used to receive salt management
The instruction at end and file, perform corresponding operation, return result to salt management ends.
(3) memory node
Memory node is used to store error log, and all databases that salt management ends are collected into all database nodes are wrong
By mistake after daily record, by salt clients, memory node is sent to.The error-logging information includes：Error log file name, deposit
Path, memory node host name are stored up, is stored in error log meta information table, for consulting history error log.
(4) Zabbix service ends
Zabbix service ends 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 reception and stores monitoring data, and monitoring alarm.
Database host is the database service mark of Zabbix service ends registration, each database service, database master
Machine represents 3306 numbers on 10.1.1.11 database nodes using port _ host mode name, such as 3306_10.1.1.11
Serviced according to storehouse.
Monitoring template refers to the interface according to database, collection item, trigger and tendency chart is set, for being mounted to data
In the main frame of storehouse.
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 a single clothes
It is engaged on device.
Periodically call salt to manage end interface, check whether the salt clients on all database nodes are registered to
Salt management ends, detection mode is as follows：
#salt-key-L-acc | grep ' database nodes host name '
If return value is false, it is necessary to call salt to manage end interface, the salt clients are registered, logon mode is such as
Under：
#salt-key-a-y ' database nodes host name '
Otherwise, it is not necessary to call the registration salt clients.If registration failure, then send notification at keeper
Reason.
The salt clients of some database node are nullified if desired, it is necessary to manually perform as given an order：
#salt-key-d ' database nodes host name '
The corresponding salt clients of all database nodes are all registered to after salt management ends, and salt management ends can
Salt clients are given to send instruction and file, specific operation is completed.
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 the database node host name described in salt clients can be with sensible；Otherwise, it is necessary to
Keeper is sent notification to, it is necessary to artificial treatment.
(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 filtrated to get based on this
Some database nodes.
Then, for each database node, salt management ends are obtained per number by sending instructions to salt clients
According to database process all on the node of storehouse, order as follows：
#salt ' database nodes host name ' and cmd.run ' ps-ef | egrep database identifiers | egrep-v grep '
Database identifier is the mark of type of database, such as, and 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 storehouse error log file name.Meanwhile, according to data
Storehouse node hostname gets database node IP.The database node host name, database node IP, database port and
Database error journal file name is stored in meta-information file.
Next, in salt management ends, meta-information file is scanned, incoming data storehouse port, database node IP, and
The user name password of Zabbix service ends, calls Zabbix to service end interface, automatically creates the corresponding database host.Together
When, according to the database host, parsing obtains monitoring template accordingly, and the incoming monitoring template calls Zabbix service ends
Interface, automatic carry monitors template, including error log collection item, error log alarm item and error log trend accordingly
Figure.
If some described database host does not need error log monitoring, manual mode can be used, in Zabbix clothes
Being engaged in, the unloading of end page face is corresponding to monitor template.
Zabbix service end functions can also be called according to real needs, adjustment error log alarm item is set.
(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 are according to incoming parameter, by salt clients, check error log file size, if mistake
Log file size is more than 2MB, then the cutting error log file, 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：
#salt ' database nodes host name ' ' cp error log files name error log file name works as the day before yesterday to cmd.run
Qi ＆＆echo>Error log file name '
Explanation：Current date is the date when instruction is performed, and form is yyyy-mm-dd
Send filing error log file as follows to the instruction of salt management ends：
#salt " database node host name " cp.push error log files name current dates
If error log file size is less than 2MB, it is not necessary to cutting and transmission error log file.
(4) acquisition monitoring data module
The incoming parameter is needed to be：According to storehouse node hostname, error log file name
Salt management ends periodically send instructions to salt clients, and the instruction of salt client executings gathers error log number
According to returning to salt management ends.The instruction is as follows：
#salt ' database nodes host name ' and cmd.run ' egrep-I error error log files name | wc-l '
Explanation：Error log file name is absolute path, is not relative path
The 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 form, monitoring data is written to monitoring data file：
Database host gathers item timestamp collection value
The collection item is error log collection item, is defined in error log monitoring template.
Timestamp is the current time stamp for performing 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
Filing error log file, by salt clients, is passed to storage section by Salt management ends according to the parameter
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/ represents store path
After the completion of operation, if being returned as vacation, keeper's processing is sent notification to；If return value is true, then record
Following information is into error log meta information table：Memory node host name, store path and error log file name, are easy to management
Member consults filing error log file information.
(6) monitoring data module is sent
The incoming parameter is needed to be：Zabbix service ends host name, Zabbix service ends port and monitoring data file；
After acquisition monitoring data module trip terminates, the monitoring data file is produced.
In salt management ends, Zabbix is called to service end interface, the incoming parameter sends monitoring data to Zabbix
Service end, mode of operation is as follows：
#Zabbix_sender--Zabbix-server Zabbix service end IP--port Zabbix service ends port --
Input-file monitoring data files -- with-timestamps
Zabbix service end IP and Zabbix service ends port can be got in Zabbix service end configuration files.
(7) monitoring data alarm module
This module is optional.Need to configure short message and mail reception people's information in Zabbix service ends, and alarm plan is set
Slightly, then Zabbix service ends are after monitoring data is received, and analysis monitoring data simultaneously produce alarm, are sent to the reception specified
People.
Claims (8)
1. a kind of Database error daily record monitoring system based on salt, it is characterised in that including Salt management ends, database section
Point, memory node and Zabbix service ends；
Salt management ends are to manage the service of salt clients, including salt management modules, metamessage management module and collection prison
Control data module；Salt management ends manage salt clients, distribution instruction and file, and the database obtained on database node enters
Journey information, and acquisition monitoring data.
Database node refers to the server for disposing 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
Error log is sent to salt management ends.
Memory node is used to store error log, and salt management ends are collected into all Database errors day of all database nodes
After will, by salt clients, memory node is sent to.
Zabbix service ends are to support the monitoring server of short message and mail, including send monitoring data module and monitoring data announcement
Alert module；Zabbix service ends receive monitoring data, and are alerted according to warning strategies, and show the trend of monitoring data
Figure.
2. a kind of Database error daily record monitoring system based on salt according to claim 1, it is characterised in that described
Salt management modules include：
Salt clients are disposed in all database nodes, salt management ends are deployed on a single server.
Periodically call salt to manage end interface, check whether the salt clients on all database nodes are registered to salt pipes
End is managed, it is such as unregistered, call salt to manage end interface, register 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 keeper.
3. a kind of Database error daily record monitoring system based on salt according to claim 1, it is characterised in that described
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
Footpath 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
Reason end obtains database processes all on each database node by sending instructions to salt clients；Parse database
Process can obtain database port and data storehouse error log file name.Meanwhile, got according to database node host name
Database node IP.The database node host name, database node IP, database port and data storehouse error log file
Name is stored in meta-information file.Next, in salt management ends, scanning meta-information file, incoming data storehouse port, database
Node IP, and Zabbix service ends user name password, call Zabbix to service end interface, automatically create the corresponding number
According to storehouse main frame.Meanwhile, according to the database host, parsing is obtained monitoring template accordingly, and the incoming monitoring template is called
Zabbix services end interface, and automatic carry monitors template, including error log collection item, error log alarm item and mistake accordingly
Miss daily record tendency chart.If some described database host does not need error log monitoring, manual mode can be used,
The corresponding monitoring template of Zabbix service ends page unloading.Zabbix service end work(can also be called according to real needs
Can, adjustment error log alarm item is set.
4. a kind of Database error daily record monitoring system based on salt according to claim 1, it is characterised 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 are according to incoming parameter, by salt clients, check error log file size, if error log
File size is more than 2MB, then the cutting error log file, meanwhile, send filing error log file and managed to salt
End.If error log file size is less than 2MB, it is not necessary to cutting and transmission error log file.
5. a kind of Database error daily record monitoring system based on salt according to claim 1, it is characterised in that described
Acquisition monitoring data module includes：
The incoming parameter is needed to be：According to storehouse node hostname, error log file name；
Salt management ends periodically send instructions to salt clients, and the instruction of salt client executings gathers error log data, returned
Back to salt management ends.The 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 form, monitoring data is written to monitoring data file：Database host, collection item, timestamp,
Collection value.The collection item is error log collection item, is defined in error log monitoring template.Timestamp is to perform to adopt
Collect the current time stamp of monitoring data.Collection value is the line number containing keyword error.
6. a kind of Database error daily record monitoring system based on salt according to claim 1, it is characterised in that described
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, and filing error log file is passed to memory node and referred to
Determine under store path, if operation failure, send notification to keeper's processing；If operated successfully, then record following information
Into error log meta information table：Memory node host name, store path and error log file name, are easy to keeper to consult and return
Shelves error log file information.
7. a kind of Database error daily record monitoring system based on salt according to claim 1, it is characterised in that described
Sending monitoring data module includes：
The incoming parameter is needed to be：Zabbix service ends host name, Zabbix service ends port and monitoring data file；In salt
Management end, calls Zabbix to service end interface, and the incoming parameter sends monitoring data to Zabbix service ends.
8. a kind of Database error daily record monitoring system based on salt according to claim 1, it is characterised in that described
Monitoring data alarm module includes：Short message and mail reception people's information are configured in Zabbix service ends, and warning strategies are set,
Then Zabbix service ends are after monitoring data is received, and analysis monitoring data simultaneously produce alarm, are sent to the recipient specified.
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 true CN107239502A (en) | 2017-10-10 |
| CN107239502B 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) |
Cited By (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 |
| CN109446024A (en) * | 2018-10-16 | 2019-03-08 | 杭州绿湾网络科技有限公司 | Using monitoring method and device |
| CN110569179A (en) * | 2018-06-06 | 2019-12-13 | 富晋精密工业（晋城）有限公司 | Data acquisition system and data acquisition method |
| 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 |
Cited By (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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107239502B (en) | 2018-07-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107239502B (en) | Database error daily record monitoring system based on salt | |
| CN107239379B (en) | Database performance Automatic monitoring systems based on salt | |
| CN107832196B (en) | Monitoring device and monitoring method for abnormal content of real-time log | |
| RU2394262C2 (en) | System for configuring devices and method of preventing abnormal situations on production plant | |
| US7921459B2 (en) | System and method for managing security events on a network | |
| CN110209518A (en) | A kind of multi-data source daily record data, which is concentrated, collects storage method and device | |
| CN101751032B (en) | Method and system for managing automatic control system and video monitoring system | |
| CN103546343B (en) | The network traffics methods of exhibiting of network traffic analysis system and system | |
| CN107220304B (en) | The slow Log Administration Systems of magnanimity mongodb based on salt | |
| US20100088197A1 (en) | Systems and methods for generating remote system inventory capable of differential update reports | |
| CN106972978A (en) | A kind of ALM method for pushing and device | |
| CN109871392B (en) | Slow sql real-time data acquisition method under distributed application system | |
| CN110764834B (en) | Automatic safety monitoring platform, management method and storage medium | |
| CN107659443A (en) | The monitoring method and its system of a kind of real time business | |
| CN109254901B (en) | A kind of Monitoring Indexes method and system | |
| CN105227367A (en) | A kind of warning analysis processing method of low delay | |
| US7099736B2 (en) | Operation management system | |
| CN112905261A (en) | API (application program interface) control method and device and electronic equipment | |
| CN110677514A (en) | IP filing information management method and device | |
| CN107171873A (en) | A kind of method and apparatus of Message Processing | |
| CN113037549A (en) | Operation and maintenance environment warning method | |
| CN111371570A (en) | Fault detection method and device for NFV network | |
| CN110989537A (en) | Production data processing method, apparatus, medium, and system | |
| JP2003233417A (en) | Data communication device and its method, and data communication program and recording medium recorded thereof | |
| CN107888714A (en) | A kind of method and device for selecting local cache DNS |
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. |