CN111858536A - Service log transmission method and terminal - Google Patents
Service log transmission method and terminal Download PDFInfo
- Publication number
- CN111858536A CN111858536A CN202010766772.1A CN202010766772A CN111858536A CN 111858536 A CN111858536 A CN 111858536A CN 202010766772 A CN202010766772 A CN 202010766772A CN 111858536 A CN111858536 A CN 111858536A
- Authority
- CN
- China
- Prior art keywords
- log
- service
- log file
- current
- file
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 230000005540 biological transmission Effects 0.000 title claims abstract description 39
- 238000005520 cutting process Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 14
- 230000000903 blocking effect Effects 0.000 abstract description 7
- 241000322338 Loeseliastrum Species 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000004083 survival effect Effects 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000007639 printing Methods 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
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/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- 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/172—Caching, prefetching or hoarding of files
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)
- Debugging And Monitoring (AREA)
Abstract
The application relates to the technical field of information transmission, in particular to a service log transmission method and a terminal, wherein the method comprises the following steps: after the service log is obtained, if the current log file exists in the log server, writing the service log into the current log file; and if the current log file does not exist in the log server, creating a new current log file in the log server, and writing the service log into the new current log file. The service log transmission method can avoid the situation that when the current log file in the log server is deleted by mistake, the service log cannot be uploaded to the log server, and new service logs are accumulated in the transmission channel, so that service blocking is further avoided, and a normal service process is kept.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a service log transmission method and a terminal.
Background
The service log is used for storing and recording detailed information of system operation conditions and user use conditions, and the information is a main basis for checking system operation states and troubleshooting problems. For example, when an application crashes, a technician can find relevant records from the event log of the application for analyzing the cause of the crash and solving the crash problem.
The service log is usually read from the standard input by the log component through a transmission channel, and the read service log is uploaded to the log directory of the log server by the log component. In the transmission process, when the log component fails to upload the service log to the log server, the service log uploading operation is continuously repeated; while the log component is still constantly reading new traffic logs from the standard input, causing the traffic logs to accumulate in the transmission channel. After the amount of the accumulated service logs reaches the maximum capacity of the transmission channel, new service logs cannot be written into the service logs, service blockage is caused finally, and the system cannot process other requests.
Disclosure of Invention
In order to solve the problem that a system cannot process other requests due to service blocking caused by uploading service logs to a log server, the application provides a service log transmission method and a terminal.
In a first aspect, an embodiment of the present application provides a service log transmission method, where the method includes:
acquiring a service log;
when a current log file exists, writing the service log into the current log file;
and when the current log file does not exist, creating a new current log file, and writing the service log into the new current log file.
In a second aspect, an embodiment of the present application provides a terminal, including:
the service network element is used for generating a service log;
the transmission channel is used for transmitting the service log;
the log server comprises a current log file, and the current log file is used for writing the service log;
the log component is to perform:
acquiring the service log from a transmission channel;
when a current log file exists, writing the service log into the current log file;
and when the current log file does not exist, creating a new current log file, and writing the service log into the new current log file.
The technical scheme provided by the application comprises the following beneficial effects: after the service log is obtained, if the current log file exists in the log server, writing the service log into the current log file; and if the current log file does not exist in the log server, creating a new current log file in the log server, and writing the service log into the new current log file. Therefore, when the current log file in the log server is deleted by mistake, the service log cannot be uploaded to the log server, and a new service log is accumulated in the transmission channel, thereby further avoiding service blockage and keeping a normal service process.
Drawings
In order to more clearly explain the technical solution of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious to those skilled in the art that other drawings can be obtained according to the drawings without any creative effort.
Fig. 1 shows a timing diagram of a service log transmission method provided in an embodiment of the present application;
fig. 2 is a schematic flow chart illustrating a service log transmission method according to an embodiment of the present application;
fig. 3 illustrates a terminal framework diagram provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Reference throughout this specification to "embodiments," "some embodiments," "one embodiment," or "an embodiment," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases "in various embodiments," "in some embodiments," "in at least one other embodiment," or "in an embodiment" or the like throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Thus, the particular features, structures, or characteristics shown or described in connection with one embodiment may be combined, in whole or in part, with the features, structures, or characteristics of one or more other embodiments, without limitation. Such modifications and variations are intended to be included within the scope of the present application.
Fig. 1 is a timing diagram of a service log transmission method according to an embodiment of the present application.
As shown in fig. 1, the system of the embodiment of the present application includes a service network element, a transmission channel, a log component, and a log server. In the working process of the system, the log component continuously reads data from the standard input of the service network element, and then writes the read data into the log server as a service log of a certain service. Specifically, the service network element writes the service log into the transmission channel, the log component reads the service log from the transmission channel, and then writes the service log into the log server.
In the transmission process, if the current log file in the log server is deleted by mistake, the service log cannot be uploaded to the log server, and finally service blocking is caused. For example, in a production environment, a calico service (calico is a pure three-tier data center network scheme based on the BGP protocol, which provides controllable IP communication through an iptables (firewall) and is used as a container communication base component), if a current log file of a confd component of the calico is deleted, a service log of the confd cannot be uploaded to a log server, and the confd is blocked in a dead loop. When a node is newly added on the line, the Bird configuration file cannot be updated due to the service blockage of the confd component.
Further, the reason that the Bird configuration file cannot be updated results in that the newly added node cannot be refreshed to the Bird component, and the newly added node cannot establish a BGP (Border Gateway Protocol) relationship with the problem node. At this time, the newly added node frequently tries to reconnect the problem node and tries to establish the BGP relationship, but the problem node is not fully configured and connection is denied. And the method causes the Bird component to continuously upload an error log "unknown connection from unknown address", and when the size of the current log file of the Bird component exceeds 1M, causes the log component to cut the current log file of the Bird, further causing the log component (such as svlog) to block from exiting in a dead loop. The blocking of the log component can cause the blocking of the Bird component, the Bird component cannot send BGP connection survival information, and after the connection survival time reaches a preset time, the BGP connection of the node with the problem is deleted, so that the BGP connection is disconnected finally, and the route is lost.
In order to solve the above problem, an embodiment of the present application provides a service log transmission method, including the following steps:
step St0t, acquiring a service log; for example, in the embodiment of the present application, a service log is generated in a service process of a service network element, the service log is written into a transmission channel, and then a log component reads the service log from the transmission channel.
Step St02, when a current log file exists, writing the service log into the current log file; for example, before writing the service log into the log server, the log component determines whether a current log file exists in the log server, and if the current log file exists in the log server, the service log is written into the current service log.
Step S102, when the current log file does not exist, a new current log file is created, and the service log is written into the new current log file. For example, when it is determined that the current log file does not exist in the log server, a new current log file is created in the log server, and the service log is written into the new current log file.
It can be seen from the above steps that in the service log transmission method in the embodiment of the present application, when the current log file in the log server is deleted, the service log can be always uploaded to the log server by the new current log file created in the log server, so that the log component is prevented from repeating the above uploading operation to cause accumulation of the new service log in the transmission channel, further service blocking is avoided, and a normal service process is maintained.
In some embodiments, as shown in the schematic flow chart of the service log transmission method in fig. 2, when the current log file exists, it needs to be further determined whether the current service log content of the current log file reaches the capacity threshold. And if the content of the current service log of the current log file is less than the capacity threshold, writing the service log into the current log file, namely uploading the service log into a log server. And if the content of the current service log of the current log file is equal to the capacity threshold, the current log file needs to be cut, and the operation of writing the service log can be continued.
In some embodiments, when the current traffic log content of the current log file is equal to the capacity threshold, the current log file is cut into a first log file and a second log file. Wherein the first log file contains all the service logs contained in the current log file, and the second log file is empty. And writing the service log to a second log file.
In some embodiments, when the current log file is cut, if the current log file is deleted, a new current log file may be further created, and the service log may be written into the new current log file.
In some embodiments, in the process of creating a new current log file when the current log file does not exist, if a log directory in the log server exists and a disk for storing the service log is not full, the new current log file may be stored in the log directory, and further, the service log may be written in the new current log file.
In some embodiments, when the current log file does not exist, in the process of creating a new current log file, if a log directory in the log server is deleted, or the log file reaches a specified maximum reserved number, or the service log has no access right to the log directory, the created new current log file cannot be saved to the log directory, that is, an available current log file cannot be created. Further, the service log cannot be written into a new current log file, and the service log cannot be uploaded to the log server. To avoid traffic congestion caused by the continuous attempt to write the traffic log to the log server, the traffic log is written to the standard output (the standard input adds a non-blocking identification). Thereby realizing the effect of keeping normal business process. And printing an alarm log while writing the service log into the standard input.
In some embodiments, when the current log file does not exist, in the process of creating a new current log file, if the disk space where the log directory to which the current log file needs to be saved is full, all files in the disk are deleted, so that the created new current log file is saved to the log directory. Further, the service log is saved to a new current log file.
In some embodiments, when the current log file does not exist, in the process of creating a new current log file, if the disk space where the log directory to which the current log file needs to be saved is full and the disk where the current log file needs to be saved is not allowed to delete the file (possibly, the current log file does not have the authority to delete the file), saving the created new current log file to the log directory cannot be achieved. Further, the service log is written into the label input, and the alarm log is printed at the same time.
Based on the embodiment corresponding to fig. 1, an embodiment of the present application provides a terminal, configured to execute the embodiment corresponding to fig. 1, and as shown in fig. 3, the service log transmission apparatus provided by the present application includes:
a service network element 201, configured to generate a service log;
a transmission channel 202, configured to transmit the service log;
the log server 203 comprises a current log file, and the current log file is used for writing the service log;
the log component 204 is operative to perform:
acquiring the service log from a transmission channel;
when a current log file exists, writing the service log into the current log file;
and when the current log file does not exist, creating a new current log file, and writing the service log into the new current log file.
In some embodiments, the log component, as shown in fig. 3, specifically includes:
a first log writing sub-component 2041, configured to write the service log into the current log file when a current service log content of the current log file is less than a capacity threshold;
a log file cutting subassembly 2042, configured to cut the current log file to obtain a first log file and a second log file when the current service log content of the current log file is equal to the capacity threshold, where the first log file includes all service logs in the current log file, and the second log file is empty;
a second log writing sub-component 2043, configured to write the service log into the second log file.
In some embodiments, the second log writing subcomponent 2043 is specifically configured to:
when the created new current log file can be saved in a log directory, the new current log file is created, the new current log file is saved in the log directory, and the service log is written in the new current log file.
In some embodiments, the second log writing sub-component 2043 is further configured to: and writing the service log into a standard output when the created new current log file cannot be saved to a log directory.
In some embodiments, the step of not saving the created new current log file to the log directory specifically includes:
when the log directory is deleted, the created new current log file cannot be saved to the log directory; or when the disk space where the log directory is located is full, the created new current log file cannot be saved to the log directory.
In some embodiments, the second log writing subcomponent 2043 is specifically configured to:
when the disk space where the log directory is located is full, deleting all files in the disk;
and creating a new current log file, saving the new current log file to the log directory, and writing the service log into the new current log file.
What has been described above includes examples of implementations of the invention. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the claimed subject matter, but it is to be appreciated that many further combinations and permutations of the subject innovation are possible. Accordingly, the claimed subject matter is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Moreover, the foregoing description of illustrated implementations of the present application, including what is described in the "abstract," is not intended to be exhaustive or to limit the disclosed implementations to the precise forms disclosed. While specific implementations and examples are described herein for illustrative purposes, various modifications are possible which are considered within the scope of such implementations and examples, as those skilled in the relevant art will recognize.
In particular and in regard to the various functions performed by the above described components, devices, circuits, systems and the like, the terms used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary aspects of the claimed subject matter. In this regard, it will also be recognized that the innovation includes a system as well as a computer-readable storage medium having computer-executable instructions for performing the acts and/or events of the various methods of the claimed subject matter.
The above-described systems/circuits/modules have been described with respect to interaction between several components/blocks. It can be appreciated that such systems/circuits and components/blocks can include those components or the referenced stator components, some of the specified components or sub-components, and/or additional components, and in various permutations and combinations of the above. Sub-components can also be implemented as components communicatively coupled to other components rather than included within parent components (hierarchical). Additionally, it should be noted that one or more components may be combined into a single component providing aggregate functionality or divided into several separate sub-components, and any one or more middle layers (e.g., a management layer) may be provided to communicatively couple to such sub-components in order to provide comprehensive functionality. Any components described herein may also interact with one or more other components not specifically described herein but known to those of skill in the art.
Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the invention are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. Any numerical value, however, inherently contains certain errors necessarily resulting from the standard deviation found in their respective testing measurements. Moreover, all ranges disclosed herein are to be understood to encompass any and all subranges subsumed therein. For example, a range of "less than or equal to 11" can include any and all subranges between (and including) the minimum value of zero and the maximum value of 11, i.e., any and all subranges have a minimum value equal to or greater than zero and a maximum value of equal to or less than 11 (e.g., 1 to 5). In some cases, the values as described for the parameters can have negative values.
In addition, while a particular feature of the subject innovation may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms "includes," "including," "has," "incorporates," variants thereof, and other similar words are used in either the detailed description or the claims, these terms are intended to be inclusive in a manner similar to the term "comprising" as an open transition word without precluding any additional or other elements.
Reference throughout this specification to "one implementation" or "an implementation" means that a particular feature, structure, or characteristic described in connection with the implementation is included in at least one implementation. Thus, the appearances of the phrases "in one implementation" or "in an implementation" in various places throughout this specification are not necessarily all referring to the same implementation. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more implementations.
Furthermore, reference throughout this specification to "an item" or "a file" means that a particular structure, feature, or object described in connection with the implementation is not necessarily the same object. Further, "file" or "item" can refer to objects in various formats.
The terms "node," "component," "module," "system," and the like as used herein are generally intended to refer to a computer-related entity, either hardware (e.g., circuitry), a combination of hardware and software, or an entity associated with an operating machine having one or more specific functionalities. For example, a component may be, but is not limited to being, a process running on a processor (e.g., a digital signal processor), a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. Although individual components are depicted in various implementations, it is to be appreciated that the components can be represented using one or more common components. Further, the design of each implementation can include different component placements, component selections, etc. to achieve optimal performance. Furthermore, "means" can take the form of specially designed hardware; generalized hardware specialized by the execution of software thereon (which enables the hardware to perform specific functions); software stored on a computer readable medium; or a combination thereof.
Moreover, the word "exemplary" or "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word "exemplary" or "exemplary" is intended to present concepts in a concrete fashion. As used herein, the term "or" is intended to mean including "or" rather than exclusive "or". That is, unless specified otherwise, or clear from context, "X employs A or B" is intended to mean that it naturally includes either of the substitutions. That is, if X employs A; x is B; or X employs both A and B, then "X employs A or B" is satisfied under any of the above examples. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form.
Claims (10)
1. A method for transmitting service logs is characterized by comprising the following steps:
acquiring a service log;
when a current log file exists, writing the service log into the current log file;
and when the current log file does not exist, creating a new current log file, and writing the service log into the new current log file.
2. The service log transmission method according to claim 1, wherein when the current log file exists, the method specifically includes:
when the content of the current service log of the current log file is smaller than a capacity threshold value, writing the service log into the current log file;
when the current service log content of the current log file is equal to the capacity threshold, cutting the current log file to obtain a first log file and a second log file, wherein the first log file comprises all service logs in the current log file, and the second log file is empty;
and writing the service log into the second log file.
3. The service log transmission method according to claim 1, wherein when the current log file does not exist, the method specifically includes:
when the created new current log file can be saved in a log directory, the new current log file is created, the new current log file is saved in the log directory, and the service log is written in the new current log file.
4. The service log transmission method according to claim 3, wherein when the current log file does not exist, the method further includes: and writing the service log into a standard output when the created new current log file cannot be saved to a log directory.
5. The service log transmission method according to claim 4, wherein the step of not saving the created new current log file to a log directory specifically comprises:
when the log directory is deleted, the created new current log file cannot be saved to the log directory;
or when the disk space where the log directory is located is full, the created new current log file cannot be saved to the log directory.
6. The service log transmission method according to claim 3, wherein when the current log file does not exist, the method specifically includes:
when the disk space where the log directory is located is full, deleting all files in the disk;
and creating a new current log file, saving the new current log file to the log directory, and writing the service log into the new current log file.
7. A terminal, comprising:
the service network element is used for generating a service log;
the transmission channel is used for transmitting the service log;
the log server comprises a current log file, and the current log file is used for writing the service log;
the log component is to perform:
acquiring the service log from a transmission channel;
when a current log file exists, writing the service log into the current log file;
and when the current log file does not exist, creating a new current log file, and writing the service log into the new current log file.
8. The terminal of claim 7, wherein when the current log file exists, the log component is specifically configured to perform:
when the content of the current service log of the current log file is smaller than a capacity threshold value, writing the service log into the current log file;
when the current service log content of the current log file is equal to the capacity threshold, cutting the current log file to obtain a first log file and a second log file, wherein the first log file comprises all service logs in the current log file, and the second log file is empty;
and writing the service log into the second log file.
9. The terminal of claim 7, wherein when the current log file does not exist, the log component is specifically configured to perform:
when the created new current log file can be saved in a log directory, the new current log file is created, the new current log file is saved in the log directory, and the service log is written in the new current log file.
10. The terminal of claim 9, wherein when the current log file does not exist, the log component is further specifically configured to:
and writing the service log into a standard output when the created new current log file cannot be saved to a log directory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010766772.1A CN111858536A (en) | 2020-08-03 | 2020-08-03 | Service log transmission method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010766772.1A CN111858536A (en) | 2020-08-03 | 2020-08-03 | Service log transmission method and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111858536A true CN111858536A (en) | 2020-10-30 |
Family
ID=72952791
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010766772.1A Pending CN111858536A (en) | 2020-08-03 | 2020-08-03 | Service log transmission method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111858536A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103645983A (en) * | 2013-12-17 | 2014-03-19 | 山东中创软件工程股份有限公司 | Method and device for generating journal file in domestic environment |
| CN104601489A (en) * | 2015-02-02 | 2015-05-06 | 迈普通信技术股份有限公司 | Log block transmitting method and apparatus |
| CN109299052A (en) * | 2018-09-03 | 2019-02-01 | 平安普惠企业管理有限公司 | Log cutting method, device, computer equipment and storage medium |
| CN109522177A (en) * | 2017-09-20 | 2019-03-26 | 阿里巴巴集团控股有限公司 | A kind of task daily record processing system, method and device |
| CN109542733A (en) * | 2018-12-05 | 2019-03-29 | 焦点科技股份有限公司 | A kind of highly reliable real-time logs collection and visual m odeling technique method |
| CN109753488A (en) * | 2019-01-04 | 2019-05-14 | 烽火通信科技股份有限公司 | A kind of server operation blog management method and system based on HTTP |
| CN111026728A (en) * | 2019-11-19 | 2020-04-17 | 山东中创软件商用中间件股份有限公司 | Log data processing method and related device |
-
2020
- 2020-08-03 CN CN202010766772.1A patent/CN111858536A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103645983A (en) * | 2013-12-17 | 2014-03-19 | 山东中创软件工程股份有限公司 | Method and device for generating journal file in domestic environment |
| CN104601489A (en) * | 2015-02-02 | 2015-05-06 | 迈普通信技术股份有限公司 | Log block transmitting method and apparatus |
| CN109522177A (en) * | 2017-09-20 | 2019-03-26 | 阿里巴巴集团控股有限公司 | A kind of task daily record processing system, method and device |
| CN109299052A (en) * | 2018-09-03 | 2019-02-01 | 平安普惠企业管理有限公司 | Log cutting method, device, computer equipment and storage medium |
| CN109542733A (en) * | 2018-12-05 | 2019-03-29 | 焦点科技股份有限公司 | A kind of highly reliable real-time logs collection and visual m odeling technique method |
| CN109753488A (en) * | 2019-01-04 | 2019-05-14 | 烽火通信科技股份有限公司 | A kind of server operation blog management method and system based on HTTP |
| CN111026728A (en) * | 2019-11-19 | 2020-04-17 | 山东中创软件商用中间件股份有限公司 | Log data processing method and related device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11573725B2 (en) | Object migration method, device, and system | |
| US11003367B2 (en) | Data storage, reading, and cleansing method and device, and cloud storage system | |
| US20080086561A1 (en) | Method for obtaining log information from network element device by network management server, a network element device and a network management server | |
| CN101447895A (en) | Collocation method for synchronizing network management and network element and device thereof | |
| CN109246182B (en) | Distributed lock manager and implementation method thereof | |
| CN105407117A (en) | Distributed data backup method, device and system | |
| CN112463882A (en) | Data synchronization method, cloud platform and edge terminal | |
| CN114979158B (en) | Resource monitoring method, system, equipment and computer readable storage medium | |
| CN109885577A (en) | Data processing method, device, terminal and storage medium | |
| JP7514336B2 (en) | Cluster capacity reduction/expansion method and system, capacity reduction/expansion control terminal, and medium | |
| US10970148B2 (en) | Method, device and computer program product for managing input/output stack | |
| CN111208934A (en) | Data storage method and device | |
| US10897402B2 (en) | Statistics increment for multiple publishers | |
| CN110502510A (en) | A kind of real-time analysis of WIFI terminal equipment track data and De-weight method and system | |
| CN111858536A (en) | Service log transmission method and terminal | |
| EP1370026A1 (en) | Automatic and dynamic reconfiguration of a network based on rules retrieved upon receiving a stimulus | |
| CN108628864B (en) | Data access method and data management device | |
| CN110177142A (en) | A kind of method of data synchronization, device and electronic equipment | |
| JP2006080615A (en) | Method and apparatus for managing network, and program | |
| CN110011850B (en) | Management method and device for services in cloud computing system | |
| CN112000390B (en) | User information management method, device, electronic equipment and storage medium | |
| EP4171076A1 (en) | Methods for reporting usage, and network function and storage medium | |
| CN111935703B (en) | Network connection management method and terminal equipment | |
| CN109376135B (en) | Cluster file system management method and system | |
| CN102387031A (en) | Simple network management protocol (SNMP) network equipment identification and data acquisition method based on state machine |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201030 |