CN113688002A - Log collection method and related device - Google Patents
Log collection method and related device Download PDFInfo
- Publication number
- CN113688002A CN113688002A CN202110856520.2A CN202110856520A CN113688002A CN 113688002 A CN113688002 A CN 113688002A CN 202110856520 A CN202110856520 A CN 202110856520A CN 113688002 A CN113688002 A CN 113688002A
- Authority
- CN
- China
- Prior art keywords
- log
- container
- configuration file
- target
- path
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000004458 analytical method Methods 0.000 claims abstract description 33
- 238000004590 computer program Methods 0.000 claims description 11
- 230000008569 process Effects 0.000 abstract description 8
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 32
- 238000005516 engineering process Methods 0.000 description 5
- 238000004422 calculation algorithm Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000006378 damage Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000013515 script Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a log collection method, which comprises the following steps: determining container log information according to the log path of the target container; matching a corresponding log analysis rule from a log collection template library according to the container log information; generating a corresponding configuration file according to the log analysis rule; and carrying out log collection on the target container according to the configuration file. The corresponding container log information is determined through the log path of the target container, then the log analysis rule is matched in the template library, and finally the corresponding configuration file is generated according to the log analysis rule, so that the automatic configuration file generation process of the container is realized, the corresponding configuration file does not need to be manually generated, the labor cost is reduced, and the log collection efficiency is improved. The application also discloses a log collection device, a server and a computer readable storage medium, which have the beneficial effects.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a log collection method, a log collection device, a server, and a computer-readable storage medium.
Background
With the continuous development of the cloud platform technology, a container technology appears, and the application management difficulty is reduced. A large number of container instances are operated on the cloud platform, and the container instances are created and scheduled on different cluster machines at any time. When a service has a problem, technicians need to check logs printed by the application for location and investigation, but the logs are distributed at different positions and are difficult to check and search, so that a uniform log management platform is needed to manage the logs.
In the related art, the efk (elastic search Kibana fluent) technology stack can perform centralized collection and display of logs, the elastic search is used for data storage, the Kibana is used for log display, and the fluent is used for log collection. The fluent is used as a log collection tool, and a plurality of log collection plug-ins are provided, so that various logs can be collected. However, the path of the collected log file is determined by the configuration file, the path of the collected log file needs to be fixed before each start, and in the face of insufficient log capacity of a docker container managed under kubenates, if the container is dynamically added or deleted, the collected file path can be dynamically adjusted, and the adjustment operation needs to be manually performed on the configuration file, so that the normal log collection operation can be performed on the container after the change, the labor cost is increased, and the efficiency of log collection is reduced.
Therefore, how to improve the efficiency of the log collection operation on the container and reduce the labor cost are important issues to be focused on by those skilled in the art.
Disclosure of Invention
The application aims to provide a log collection method, a log collection device, a server and a computer readable storage medium, which can reduce the labor cost of collecting container logs and improve the efficiency of log collection operation.
In order to solve the above technical problem, the present application provides a log collecting method, including:
determining container log information according to the log path of the target container;
matching a corresponding log analysis rule from a log collection template library according to the container log information;
generating a corresponding configuration file according to the log analysis rule;
and carrying out log collection on the target container according to the configuration file.
Optionally, determining container log information according to a preset path of the target container includes:
when a new container is created, taking the new container as the target container;
determining the log path according to the ID of the target container;
and combining the ID of the target container, the container information and the log path to obtain the container log information.
Optionally, determining container log information according to a preset path of the target container includes:
acquiring all container lists, and taking containers in all container lists as target containers;
determining the corresponding log path according to the ID of each target container;
and combining the ID, the container information and the log path of each target container to obtain corresponding container log information.
Optionally, obtaining a list of all containers includes:
the list of all containers is obtained by dockerrapi.
Optionally, the method further includes:
judging whether a container deleting event occurs according to a preset period;
and if so, deleting the configuration file of the container corresponding to the container deleting event.
Optionally, performing log collection on the target container according to the configuration file includes:
and adopting a fluent service to collect logs of the target container according to the configuration file.
Optionally, the method further includes:
and restarting the fluent service when the configuration file is updated.
The present application further provides a log collection device, including:
the log information determining module is used for determining container log information according to the log path of the target container;
the analysis rule matching module is used for matching a corresponding log analysis rule from a log collection template base according to the container log information;
the configuration file generation module is used for generating a corresponding configuration file according to the log analysis rule;
and the log acquisition module is used for acquiring logs of the target container according to the configuration file.
The present application further provides a server, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the log collection method as described above when executing the computer program.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the log collection method as described above.
The application provides a log collection method, which comprises the following steps: determining container log information according to the log path of the target container; matching a corresponding log analysis rule from a log collection template library according to the container log information; generating a corresponding configuration file according to the log analysis rule; and carrying out log collection on the target container according to the configuration file.
The corresponding container log information is determined through the log path of the target container, then the log analysis rule is matched in the template library, and finally the corresponding configuration file is generated according to the log analysis rule, so that the automatic configuration file generation process of the container is realized, the corresponding configuration file does not need to be manually generated, the labor cost is reduced, and the log collection efficiency is improved.
The application also provides a log collection device, a server and a computer readable storage medium, which have the beneficial effects, and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a log collection method according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a log collection device according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a log collection method, a log collection device, a server and a computer readable storage medium, so that the labor cost of collecting container logs is reduced, and the efficiency of log collection operation is improved.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all 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 application.
In the related art, the EFK technology stack can perform centralized collection and presentation of logs, the elastic search is used for data storage, the Kibana is used for log presentation, and the fluent is used for log collection. The fluent is used as a log collection tool, and a plurality of log collection plug-ins are provided, so that various logs can be collected. However, the path of the collected log file is determined by the configuration file, the path of the collected log file needs to be fixed before each start, and in the face of insufficient log capacity of a docker container managed under kubenates, if the container is dynamically added or deleted, the collected file path can be dynamically adjusted, and the adjustment operation needs to be manually performed on the configuration file, so that the normal log collection operation can be performed on the container after the change, the labor cost is increased, and the efficiency of log collection is reduced.
Therefore, the log collection method provided by the application determines the corresponding container log information through the log path of the target container, then matches the log analysis rule in the template library, and finally generates the corresponding configuration file according to the log analysis rule, so that the automatic configuration file generation process of the container is realized, the corresponding configuration file does not need to be manually generated, the labor cost is reduced, and the log collection efficiency is improved.
The following describes a log collection method provided by the present application with an embodiment.
Referring to fig. 1, fig. 1 is a flowchart of a log collecting method according to an embodiment of the present disclosure.
In this embodiment, the method may include:
s101, determining container log information according to a log path of a target container;
this step is intended to determine container log information from the log path of the target container;
wherein the container log information may include: container id, type, name, log path, etc.
Further, the step may include:
step 1, when a new container is created, taking the new container as a target container;
step 2, determining a log path according to the ID of the target container;
and 3, combining the ID of the target container, the container information and the log path to obtain container log information.
It can be seen that the present alternative scheme mainly explains how to obtain container log information. In the alternative scheme, when a new container is created, the new container is used as a target container, a log path is determined according to the ID of the target container, and the ID of the target container, container information and the log path are combined to obtain container log information.
That is to say, in this alternative scheme, mainly when a new container is dynamically created, the corresponding configuration file is automatically generated, so that the corresponding configuration file is dynamically generated for the created new container.
Further, the step may include:
step 1, acquiring all container lists, and taking containers in all container lists as target containers;
step 2, determining a corresponding log path according to the ID of each target container;
and 3, combining the ID, the container information and the log path of each target container to obtain corresponding container log information.
It can be seen that the present alternative scheme mainly explains how to obtain container log information. In this embodiment, all container lists are obtained, the containers in all the container lists are used as target containers, a corresponding log path is determined according to the ID of each target container, and the ID, the container information and the log path of each target container are combined to obtain corresponding container log information. That is, according to the present embodiment, multiple containers can be realized to automatically generate corresponding configuration files.
Further, the step of acquiring all container lists in the above optional technical solution may include:
all container lists were obtained by dockerAPI.
It can be seen that in this alternative scheme, all container lists are obtained mainly by dockerrapi. Wherein, dockerAPI is a management interface provided by docker software to the outside.
S102, matching corresponding log analysis rules from a log collection template library according to container log information;
on the basis of S101, this step aims to match the corresponding log parsing rule from the log collection template library according to the container log information.
The log collection template library mainly stores log analysis rules of various containers. In the daily use process, the log analysis rules of different types of containers are collected to obtain the log collection template library, and then the matching is performed according to the types to determine the log analysis rule corresponding to the current target container.
Therefore, in the present embodiment, the corresponding log parsing rule may be matched by the type in the container log information.
S103, generating a corresponding configuration file according to the log analysis rule;
on the basis of S102, this step aims to generate a corresponding configuration file according to the log parsing rule. That is, the configuration file mainly includes what analysis method the content has acquired the corresponding log data. Therefore, on the basis of determining the log analysis rule, a corresponding configuration file can be generated. Further, in this step, the log parsing rule may be generated into a corresponding configuration file according to the format of the collection service.
And S104, carrying out log collection on the target container according to the configuration file.
On the basis of S103, this step is intended to log the target container according to the configuration file.
Further, the step may include:
and adopting a fluent service to perform log collection on the target container according to the configuration file.
Therefore, in the alternative scheme, the fluent service is mainly adopted to log the target container according to the configuration file. The fluent is a log management tool, which simplifies the collection, processing and storage of logs, and technicians can write special log processing scripts without maintenance.
Based on the above alternatives, this embodiment may further include:
and restarting the fluent service when the configuration file is updated.
That is, a new configuration file may not be applied whenever the fluent service is restarted, enabling dynamic management of the log collection process.
In addition, the present embodiment may further include:
step 1, judging whether a container deleting event occurs according to a preset period;
and 2, if so, deleting the configuration file of the container corresponding to the deleted container event.
Therefore, the alternative scheme mainly explains that when the container is deleted, the corresponding configuration file is dynamically adjusted, manual operation is avoided, and the efficiency of log collection is improved.
In summary, in this embodiment, the corresponding container log information is determined through the log path of the target container, then the log parsing rule is matched in the template library, and finally the corresponding configuration file is generated according to the log parsing rule, so that an automatic configuration file generation process for the container is realized, and the corresponding configuration file does not need to be manually generated, thereby reducing the labor cost and improving the efficiency of log collection.
A log collection method provided in the present application is further described below with reference to a specific embodiment.
The system can comprise a docker container event management device, a fluent configuration file management device, a docker log collection template management device and a fluent collection plug-in management device.
The docker container event management device obtains a current container list and sends the full-size list to the fluent configuration file management device. The fluent configuration file management device analyzes the information sent by the docker container event management device, analyzes the data in the information, and makes a request to the docker log collection template management device according to the information of each container to obtain a collection configuration template of the current container, and generates an independent configuration file for the existing container according to the template. After the configuration file is generated, the fluent configuration file management device sends information to the fluent acquisition plug-in management device, and starts fluent service to collect logs.
In addition, the docker container event management device can continuously monitor the progress of docker, acquire which containers are newly created and deleted, and send the information to the fluent configuration file management device after being collated, the fluent configuration file management device can add or delete the configuration file according to the sent information again, and send the information to the fluent acquisition plug-in management device after the configuration file is completed, and restart the fluent so as to dynamically update the configuration file.
Further, the process in this embodiment may include:
step 1, when a container of each application is used for making a mirror image, a log is required to be printed on a console, the console log is collected through a docker service, a file named by a container ID is generated for each container, and the log file is put into a log file of/var/lib/docker/contacts/< contact > -json.
The log file is in a json format and comprises three fields of log, stream and time, wherein the log field is specifically printed content.
And 2, the docker container event management device can acquire a container list which is running at present through the docker service on the host, and can find the log output file position of the corresponding container.
And 3, the docker container event management device sends each container information (mainly comprising container id, type, name, log path and the like) to the fluent configuration file management device.
And 4, the fluent configuration file management device requests the log collection template management device according to the type of the container, if the log analysis rule of the container of the corresponding type is found in the log collection template management, the configuration file is generated according to the corresponding rule, and if not, the analysis rule is not generated.
And 5, after the configuration file is generated, the fluent configuration file management device sends a restart signal to the fluent acquisition plug-in management device.
And 6, restarting the fluent service after the fluent acquisition plug-in management device receives the received restart signal, wherein the configuration file is generated newly.
The configuration file generates the position of the read log by default, and repeated reading is prevented after restarting.
In addition, the docker container event management device can continuously monitor events of the docker service, acquire creation or destruction of the containers, and correspondingly send a request to the fluent configuration file management device.
And the fluent configuration file management device repeats the steps to achieve the purpose of dynamically acquiring the docker logs.
Therefore, in the embodiment, the corresponding container log information is determined through the log path of the target container, then the log analysis rule is matched in the template library, and finally the corresponding configuration file is generated according to the log analysis rule, so that the automatic configuration file generation process of the container is realized, the corresponding configuration file does not need to be manually generated, the labor cost is reduced, and the log collection efficiency is improved.
In the following, the log collecting device provided by the embodiment of the present application is introduced, and the log collecting device described below and the log collecting method described above may be referred to correspondingly.
Referring to fig. 2, fig. 2 is a schematic structural diagram of a log collecting device according to an embodiment of the present disclosure.
In this embodiment, the apparatus may include:
a log information determining module 100, configured to determine container log information according to a log path of a target container;
the analysis rule matching module 200 is used for matching a corresponding log analysis rule from the log collection template base according to the container log information;
a configuration file generating module 300, configured to generate a corresponding configuration file according to the log parsing rule;
and the log collection module 400 is configured to collect logs of the target container according to the configuration file.
Optionally, the log information determining module 100 is specifically configured to, when a new container is created, take the new container as a target container; determining a log path according to the ID of the target container; and combining the ID of the target container, the container information and the log path to obtain container log information.
Optionally, the log information determining module 100 is specifically configured to obtain all container lists, and use containers in all container lists as target containers; determining a corresponding log path according to the ID of each target container; and combining the ID, the container information and the log path of each target container to obtain corresponding container log information.
Optionally, the apparatus may further include:
the dynamic deleting module is used for judging whether a container deleting event occurs according to a preset period; and if so, deleting the configuration file of the container corresponding to the deleted container event.
An embodiment of the present application further provides a server, including:
a memory for storing a computer program;
a processor for implementing the steps of the log collection method as described in the above embodiments when executing the computer program.
The embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the log collection method according to the above embodiment are implemented.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above provides a log collection method, a log collection device, a server and a computer readable storage medium. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A log collection method, comprising:
determining container log information according to the log path of the target container;
matching a corresponding log analysis rule from a log collection template library according to the container log information;
generating a corresponding configuration file according to the log analysis rule;
and carrying out log collection on the target container according to the configuration file.
2. The log collection method of claim 1, wherein determining container log information according to the preset path of the target container comprises:
when a new container is created, taking the new container as the target container;
determining the log path according to the ID of the target container;
and combining the ID of the target container, the container information and the log path to obtain the container log information.
3. The log collection method of claim 1, wherein determining container log information according to the preset path of the target container comprises:
acquiring all container lists, and taking containers in all container lists as target containers;
determining the corresponding log path according to the ID of each target container;
and combining the ID, the container information and the log path of each target container to obtain corresponding container log information.
4. The log collection method of claim 3, wherein obtaining a list of all containers comprises:
the list of all containers is obtained by dockerrapi.
5. The log collection method of claim 1, further comprising:
judging whether a container deleting event occurs according to a preset period;
and if so, deleting the configuration file of the container corresponding to the container deleting event.
6. The log collection method of claim 1, wherein collecting logs for the target container according to the configuration file comprises:
and adopting a fluent service to collect logs of the target container according to the configuration file.
7. The log collection method of claim 6, further comprising:
and restarting the fluent service when the configuration file is updated.
8. A log collection device, comprising:
the log information determining module is used for determining container log information according to the log path of the target container;
the analysis rule matching module is used for matching a corresponding log analysis rule from a log collection template base according to the container log information;
the configuration file generation module is used for generating a corresponding configuration file according to the log analysis rule;
and the log acquisition module is used for acquiring logs of the target container according to the configuration file.
9. A server, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the log collection method of any one of claims 1 to 7 when executing said computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, realizes the steps of the log collection method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110856520.2A CN113688002A (en) | 2021-07-28 | 2021-07-28 | Log collection method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110856520.2A CN113688002A (en) | 2021-07-28 | 2021-07-28 | Log collection method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113688002A true CN113688002A (en) | 2021-11-23 |
Family
ID=78578080
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110856520.2A Withdrawn CN113688002A (en) | 2021-07-28 | 2021-07-28 | Log collection method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113688002A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114371888A (en) * | 2022-01-14 | 2022-04-19 | 中国电信股份有限公司 | Method and device for hot updating of log collection plug-in, electronic equipment and readable medium |
| CN114756301A (en) * | 2022-04-24 | 2022-07-15 | 北京百度网讯科技有限公司 | Log processing method, device and system |
| CN116760682A (en) * | 2023-08-22 | 2023-09-15 | 深圳前海环融联易信息科技服务有限公司 | Log acquisition and filtration method, device, equipment and medium |
-
2021
- 2021-07-28 CN CN202110856520.2A patent/CN113688002A/en not_active Withdrawn
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114371888A (en) * | 2022-01-14 | 2022-04-19 | 中国电信股份有限公司 | Method and device for hot updating of log collection plug-in, electronic equipment and readable medium |
| CN114756301A (en) * | 2022-04-24 | 2022-07-15 | 北京百度网讯科技有限公司 | Log processing method, device and system |
| CN114756301B (en) * | 2022-04-24 | 2023-09-01 | 北京百度网讯科技有限公司 | Log processing method, device and system |
| CN116760682A (en) * | 2023-08-22 | 2023-09-15 | 深圳前海环融联易信息科技服务有限公司 | Log acquisition and filtration method, device, equipment and medium |
| CN116760682B (en) * | 2023-08-22 | 2023-12-05 | 深圳前海环融联易信息科技服务有限公司 | Log acquisition and filtration method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113688002A (en) | Log collection method and related device | |
| CN110956269B (en) | Method, device, equipment and computer storage medium for generating data model | |
| CN113392005B (en) | Large file processing test method and system | |
| CN113448752A (en) | Index data acquisition method and device, electronic equipment and storage medium | |
| CN112181695A (en) | Abnormal application processing method, device, server and storage medium | |
| CN106656592B (en) | Service management method and device based on role configuration | |
| CN118277221A (en) | System abnormal data acquisition method and device, electronic equipment and storage medium | |
| CN113641384A (en) | Probe upgrading management method, device and system | |
| CN113304469B (en) | Game player matching method and device and computer equipment | |
| CN113849356A (en) | Equipment testing method and device, electronic equipment and storage medium | |
| CN113741930A (en) | Application upgrading method and device, electronic equipment and computer readable storage medium | |
| CN111672128A (en) | Game mall game recommendation method and system based on local reserved time identification | |
| CN112328616A (en) | Data updating method, device and storage medium | |
| JP2018067241A (en) | Operation log generation device, operation log generation system, operation log generation method, and operation log generation program | |
| CN108363671B (en) | Interface switching method, terminal equipment and storage medium | |
| CN115455059A (en) | Method, device and related medium for analyzing user behavior based on underlying data | |
| CN114650211A (en) | Fault repairing method, device, electronic equipment and computer readable storage medium | |
| CN110909072A (en) | Data table establishing method, device and equipment | |
| CN114691768A (en) | Data processing method, accounting system and related equipment | |
| CN114490432A (en) | Memory processing method and device, electronic equipment and computer readable storage medium | |
| CN111581432A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111159988A (en) | Model processing method and device, computer equipment and storage medium | |
| CN112035425B (en) | Log storage method and device and computer system | |
| CN117411915A (en) | Device binding method and device, electronic device and computer storage medium | |
| CN116016257B (en) | State monitoring method, device, equipment and storage medium |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20211123 |
|
| WW01 | Invention patent application withdrawn after publication |