CN112187509A - Multi-architecture cloud platform execution log management method, system, terminal and storage medium - Google Patents
Multi-architecture cloud platform execution log management method, system, terminal and storage medium Download PDFInfo
- Publication number
- CN112187509A CN112187509A CN202010851494.XA CN202010851494A CN112187509A CN 112187509 A CN112187509 A CN 112187509A CN 202010851494 A CN202010851494 A CN 202010851494A CN 112187509 A CN112187509 A CN 112187509A
- Authority
- CN
- China
- Prior art keywords
- unique
- log
- execution
- content
- 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.)
- Withdrawn
Links
- 238000007726 management method Methods 0.000 title claims description 10
- 238000000034 method Methods 0.000 claims abstract description 35
- 238000004458 analytical method Methods 0.000 claims description 17
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 9
- 230000010354 integration Effects 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 9
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007639 printing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- 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
Abstract
The invention provides a method, a system, a terminal and a storage medium for managing execution logs of a multi-architecture cloud platform, wherein the method comprises the following steps: generating a unique ID for a user request, and recording a resource address and time of the user request; storing the unique ID with the resource address and time binding; collecting an execution log requested by the user, and integrally binding the execution log and the unique ID into an execution file; and analyzing the execution file to obtain a unique ID and execution log content, and binding the unique ID and the execution log content and then storing the bound unique ID and execution log content in a database. According to the method, when the operation and maintenance personnel use the cloud platform, if the cloud platform has a request error, the execution log of the corresponding request can be quickly tracked through the interface, the execution log does not need to be logged in a host to search for the execution log, the debugging efficiency is greatly improved, and good support can be provided on multi-architecture cloud platforms such as x86, arm and mips.
Description
Technical Field
The invention relates to the technical field of multi-architecture cloud platforms, in particular to a method, a system, a terminal and a storage medium for managing execution logs of a multi-architecture cloud platform.
Background
In the cloud computing era, virtualization technology is widely applied to data centers, massive business systems run in virtual machines on servers, utilization of the virtual machines improves utilization rate of hardware, and cost of enterprises is greatly saved. However, while saving the cost, the management of the huge number of virtual machines becomes an important problem, which brings great challenges to operation and maintenance. At present, many data centers are managed by a unified cloud platform, the management difficulty of operation and maintenance personnel is greatly facilitated, the operation and maintenance personnel can create and destroy a virtual machine through the cloud platform, mount a cloud hard disk on the virtual machine, configure a virtual machine network and the like, various operations are unified on the same operation interface, and execution details of a background are hidden, so that the operation and maintenance personnel are very convenient.
Because the specific execution details of the background are hidden, all operations are interacted with various services distributed in the background through http, the reason is difficult to locate when a problem occurs, and the checking of the execution log is a good method for troubleshooting the problem. However, various components in the background are deployed on different servers in a micro-service manner, the same request may span many services and be executed on different machines, it is quite troublesome to search a specific execution log, at present, a lot of machines need to be logged in to search in a log file for the problem of troubleshooting of an operation and maintenance person, and a lot of time is consumed in the process of searching the log by the operation and maintenance person.
Disclosure of Invention
In order to solve the above technical problems, the present invention provides a method, a system, a terminal, and a storage medium for managing execution logs of a multi-architecture cloud platform.
In a first aspect, the present invention provides a method for managing execution logs of a multi-architecture cloud platform, including:
generating a unique ID for a user request, and recording a resource address and time of the user request;
storing the unique ID with the resource address and time binding;
collecting an execution log requested by the user, and integrally binding the execution log and the unique ID into an execution file;
and analyzing the execution file to obtain a unique ID and execution log content, and binding the unique ID and the execution log content and then storing the bound unique ID and execution log content in a database.
Further, the method further comprises:
receiving a log query request sent by a user, and analyzing a resource address and time from the log query request;
searching the unique ID of the resource address and the time binding;
and inquiring the log content bound by the unique ID from the database through an inquiry interface of the database, and outputting and displaying the log content.
Further, after the generating the unique ID for the user request, the method further comprises:
the unique ID is placed as a parameter in the header of the response protocol.
Further, the collecting an execution log requested by the user and binding the execution log and the unique ID into an execution file includes:
fetching the unique ID from a header of a response protocol and placing the unique ID into a global environment variable before processing the user request;
processing the user request and generating an execution log of the user request;
and taking out the unique ID from the global environment variable, and integrating the unique ID and the execution log into an execution file.
Further, the analyzing the execution file to obtain the unique ID and the execution log content includes:
monitoring the updating of the execution file by using a log analysis tool;
and analyzing the updated execution file to obtain the unique ID, specifically analyzing each log, and summarizing the log analysis result into the log content.
In a second aspect, the present invention provides a multi-architecture cloud platform execution log management system, including:
the request recording unit is configured to generate a unique ID for a user request and record a resource address and time of the user request;
the recording storage unit is configured for storing the unique ID and the resource address and time binding;
the log integration unit is configured for acquiring an execution log requested by the user and integrating and binding the execution log and the unique ID into an execution file;
and the log storage unit is configured for analyzing the execution file to obtain a unique ID and execution log content, and storing the unique ID and the execution log content to a database after binding.
Further, the system further comprises:
the query analysis unit is configured for receiving a log query request sent by a user and analyzing a resource address and time from the log query request;
the ID searching unit is configured for searching the unique ID bound by the resource address and the time;
and the content display unit is configured to query the log content bound by the unique ID from the database through a query interface of the database and output and display the log content.
Further, the log saving unit includes:
the file monitoring module is configured for monitoring the updating of the execution file by using a log analysis tool;
and the file analysis module is configured for analyzing the updated execution file to obtain the unique ID, specifically analyzing each log and summarizing a log analysis result into log content.
In a third aspect, a terminal is provided, including:
a processor, a memory, wherein,
the memory is used for storing a computer program which,
the processor is used for calling and running the computer program from the memory so as to make the terminal execute the method of the terminal.
In a fourth aspect, a computer storage medium is provided having stored therein instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.
The beneficial effect of the invention is that,
according to the method, the system, the terminal and the storage medium for managing the execution log of the multi-architecture cloud platform, the unique ID is generated for the user request, the unique ID is bound with the resource address and the time of the user request, the unique ID is bound with the execution log content of the user request and stored, the user can search the unique ID through the resource address and the time, and then the corresponding execution log content is searched through the unique ID. According to the method, when the operation and maintenance personnel use the cloud platform, if the cloud platform has a request error, the execution log of the corresponding request can be quickly tracked through the interface, the execution log does not need to be logged in a host to search for the execution log, the debugging efficiency is greatly improved, and good support can be provided on multi-architecture cloud platforms such as x86, arm and mips.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention.
FIG. 2 is a schematic block diagram of a system of one embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and 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 invention.
The following explains key terms appearing in the present invention.
ELK is short for Elasticissearch, Logstash and Kibana.
The Elasticissearch is a real-time full-text search and analysis engine and provides three functions of collecting, analyzing and storing data; the system is an extensible distributed system which provides efficient search function by opening structures such as REST, JAVA API and the like. It is built on the Apache Lucene search engine library.
Logstash is a tool used to gather, analyze, and filter logs. It supports almost any type of log, including system logs, error logs, and custom application logs. It can receive logs from many sources, it can output data in a variety of ways, including email, websockets, and Elasticsearch.
Kibana is a Web-based graphical interface for searching, analyzing and visualizing log data stored in the Elasticissearch index. It utilizes the REST interface of the Elasticsearch to retrieve data, allowing users not only to create a customized dashboard view of their own data, but also allowing them to query and filter data in a special way.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention. The execution subject in fig. 1 may be a multi-architecture cloud platform execution log management system.
As shown in fig. 1, the method includes:
Specifically, the multi-architecture cloud platform execution log management method includes:
and S1, generating a unique ID for the user request, and recording the resource address and the time of the user request.
The method comprises the steps that a user requests cloud platform service, an http request is sent to a background component, a 32-bit UUID is generated before the request is sent each time and serves as a unique ID of the request, and the ID serves as a parameter and is placed into a header of the http.
S2, storing the unique ID and the resource address and the time binding.
The method comprises the steps of firstly recording a request before http is sent, binding and storing url (resource address) of the request and generated unique ID and time so as to record user operation, displaying the url (resource address) of the request and the generated unique ID and time which are bound and stored as operation records of a user on a display interface in a data bar mode, and inquiring the unique ID of the operation by the user according to the operation time and the url.
And S3, collecting the execution log requested by the user, and binding the execution log and the unique ID into an execution file in an integrated manner.
After receiving the user request, the background service system firstly analyzes the request, takes out the ID in the header of the http request, puts the ID into the global environment variable, then the service logic processes the request, the service logic prints the log into a file through the log processing device, before printing, the log processing device firstly takes out the ID of the request from the environment variable, then integrates the ID and the log printed by the service, and outputs the ID and the log printed by the service into an execution file of the system in a specific format.
And S4, analyzing the execution file to obtain a unique ID and execution log content, and binding the unique ID and the execution log content and then storing the bound unique ID and execution log content in a database.
The logstack is run on all servers and is responsible for monitoring logs printed by the log processing device, specifically resolving each log, because each log contains a requested unique ID and corresponding log content, resolving the unique ID and the specific log content, and sending the unique ID and the specific log content to an Elasticsearch database of the log storage device after being bound. The Elasticisearch database stores the transmitted unique ID and the log content of the binding and provides an interface call for the log query device to query.
S5, when receiving the log inquiry request of the user, firstly resolving the resource address and time from the request. And searching the bound unique ID according to the resource address and time, and calling an interface of an Elasticissearch database to inquire the log content bound by the unique ID. In addition, if the user specifies the unique ID of the execution log, the unique ID can be written in the log query request, and the system queries corresponding log content from the Elasticissearch database according to the unique ID. And displaying the queried execution log content through Kibana.
As shown in fig. 2, the system 200 includes:
a request recording unit 210 configured to generate a unique ID for a user request, and record a resource address and time of the user request;
a record storage unit 220 configured to store the unique ID with the resource address and the time binding;
a log integration unit 230 configured to collect an execution log requested by the user and integrate and bind the execution log and the unique ID as an execution file;
and the log saving unit 240 is configured to parse the execution file to obtain a unique ID and execution log content, and store the unique ID and the execution log content to the database after binding.
Optionally, as an embodiment of the present invention, the system further includes:
the query analysis unit is configured for receiving a log query request sent by a user and analyzing a resource address and time from the log query request;
the ID searching unit is configured for searching the unique ID bound by the resource address and the time;
and the content display unit is configured to query the log content bound by the unique ID from the database through a query interface of the database and output and display the log content.
Optionally, as an embodiment of the present invention, the log saving unit includes:
the file monitoring module is configured for monitoring the updating of the execution file by using a log analysis tool;
and the file analysis module is configured for analyzing the updated execution file to obtain the unique ID, specifically analyzing each log and summarizing a log analysis result into log content.
Fig. 3 is a schematic structural diagram of a terminal 300 according to an embodiment of the present invention, where the terminal 300 may be used to execute the multi-architecture cloud platform execution log management method according to the embodiment of the present invention.
Among them, the terminal 300 may include: a processor 310, a memory 320, and a communication unit 330. The components communicate via one or more buses, and those skilled in the art will appreciate that the architecture of the servers shown in the figures is not intended to be limiting, and may be a bus architecture, a star architecture, a combination of more or less components than those shown, or a different arrangement of components.
The memory 320 may be used for storing instructions executed by the processor 310, and the memory 320 may be implemented by any type of volatile or non-volatile storage terminal or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The executable instructions in memory 320, when executed by processor 310, enable terminal 300 to perform some or all of the steps in the method embodiments described below.
The processor 310 is a control center of the storage terminal, connects various parts of the entire electronic terminal using various interfaces and lines, and performs various functions of the electronic terminal and/or processes data by operating or executing software programs and/or modules stored in the memory 320 and calling data stored in the memory. The processor may be composed of an Integrated Circuit (IC), for example, a single packaged IC, or a plurality of packaged ICs connected with the same or different functions. For example, the processor 310 may include only a Central Processing Unit (CPU). In the embodiment of the present invention, the CPU may be a single operation core, or may include multiple operation cores.
A communication unit 330, configured to establish a communication channel so that the storage terminal can communicate with other terminals. And receiving user data sent by other terminals or sending the user data to other terminals.
The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments provided by the present invention when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).
Therefore, the unique ID is generated for the user request, the unique ID is bound with the resource address and the time of the user request, and the unique ID is bound with the execution log content of the user request and stored, so that the user can search the unique ID through the resource address and the time and search the corresponding execution log content through the unique ID. According to the method, when the operation and maintenance personnel use the cloud platform, if the cloud platform has a request error, the execution logs of the corresponding requests can be quickly tracked through the interface, the execution logs do not need to be logged in the host to search for the execution logs, the debugging efficiency is greatly improved, good support can be achieved on the multi-architecture cloud platforms such as x86, arm and mips, the technical effect which can be achieved by the embodiment can be referred to the description above, and the description is omitted here.
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be embodied in the form of a software product, where the computer software product is stored in a storage medium, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, and the storage medium can store program codes, and includes instructions for enabling a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, and the like) to perform all or part of the steps of the method in the embodiments of the present invention.
The same and similar parts in the various embodiments in this specification may be referred to each other. Especially, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant points can be referred to the description in the method embodiment.
In the embodiments provided in the present invention, it should be understood that the disclosed system and method can be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, systems or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
Although the present invention has been described in detail by referring to the drawings in connection with the preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A multi-architecture cloud platform execution log management method is characterized by comprising the following steps:
generating a unique ID for a user request, and recording a resource address and time of the user request;
storing the unique ID with the resource address and time binding;
collecting an execution log requested by the user, and integrally binding the execution log and the unique ID into an execution file;
and analyzing the execution file to obtain a unique ID and execution log content, and binding the unique ID and the execution log content and then storing the bound unique ID and execution log content in a database.
2. The method of claim 1, further comprising:
receiving a log query request sent by a user, and analyzing a resource address and time from the log query request;
searching the unique ID of the resource address and the time binding;
and inquiring the log content bound by the unique ID from the database through an inquiry interface of the database, and outputting and displaying the log content.
3. The method of claim 1, wherein after the generating a unique ID for a user request, the method further comprises:
the unique ID is placed as a parameter in the header of the response protocol.
4. The method of claim 3, wherein collecting the execution log of the user request and binding the execution log with the unique ID integration as an execution file comprises:
fetching the unique ID from a header of a response protocol and placing the unique ID into a global environment variable before processing the user request;
processing the user request and generating an execution log of the user request;
and taking out the unique ID from the global environment variable, and integrating the unique ID and the execution log into an execution file.
5. The method of claim 1, wherein parsing the execution file to obtain a unique ID and execution log content comprises:
monitoring the updating of the execution file by using a log analysis tool;
and analyzing the updated execution file to obtain the unique ID, specifically analyzing each log, and summarizing the log analysis result into the log content.
6. A multi-architecture cloud platform execution log management system is characterized by comprising:
the request recording unit is configured to generate a unique ID for a user request and record a resource address and time of the user request;
the recording storage unit is configured for storing the unique ID and the resource address and time binding;
the log integration unit is configured for acquiring an execution log requested by the user and integrating and binding the execution log and the unique ID into an execution file;
and the log storage unit is configured for analyzing the execution file to obtain a unique ID and execution log content, and storing the unique ID and the execution log content to a database after binding.
7. The system of claim 6, further comprising:
the query analysis unit is configured for receiving a log query request sent by a user and analyzing a resource address and time from the log query request;
the ID searching unit is configured for searching the unique ID bound by the resource address and the time;
and the content display unit is configured to query the log content bound by the unique ID from the database through a query interface of the database and output and display the log content.
8. The system of claim 6, wherein the log saving unit comprises:
the file monitoring module is configured for monitoring the updating of the execution file by using a log analysis tool;
and the file analysis module is configured for analyzing the updated execution file to obtain the unique ID, specifically analyzing each log and summarizing a log analysis result into log content.
9. A terminal, comprising:
a processor;
a memory for storing instructions for execution by the processor;
wherein the processor is configured to perform the method of any one of claims 1-5.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010851494.XA CN112187509A (en) | 2020-08-21 | 2020-08-21 | Multi-architecture cloud platform execution log management method, system, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010851494.XA CN112187509A (en) | 2020-08-21 | 2020-08-21 | Multi-architecture cloud platform execution log management method, system, terminal and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112187509A true CN112187509A (en) | 2021-01-05 |
Family
ID=73925001
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010851494.XA Withdrawn CN112187509A (en) | 2020-08-21 | 2020-08-21 | Multi-architecture cloud platform execution log management method, system, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112187509A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268464A (en) * | 2021-06-07 | 2021-08-17 | 平安科技（深圳）有限公司 | Log display method and device, electronic equipment and storage medium |
| CN113608906A (en) * | 2021-06-30 | 2021-11-05 | 苏州浪潮智能科技有限公司 | Cloud computing memory address segment abnormity testing method, system, terminal and storage medium |
-
2020
- 2020-08-21 CN CN202010851494.XA patent/CN112187509A/en not_active Withdrawn
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268464A (en) * | 2021-06-07 | 2021-08-17 | 平安科技（深圳）有限公司 | Log display method and device, electronic equipment and storage medium |
| CN113268464B (en) * | 2021-06-07 | 2023-06-23 | 平安科技（深圳）有限公司 | Log display method and device, electronic equipment and storage medium |
| CN113608906A (en) * | 2021-06-30 | 2021-11-05 | 苏州浪潮智能科技有限公司 | Cloud computing memory address segment abnormity testing method, system, terminal and storage medium |
| CN113608906B (en) * | 2021-06-30 | 2023-08-08 | 苏州浪潮智能科技有限公司 | Cloud computing memory address segment anomaly test method, system, terminal and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11768811B1 (en) | Managing user data in a multitenant deployment | |
| CN108427705B (en) | Electronic device, distributed system log query method and storage medium | |
| US11775343B1 (en) | Duty cycle estimation for job assignment | |
| Mayer et al. | An approach to extract the architecture of microservice-based software systems | |
| US9444899B2 (en) | Use of internet information services logging to collect user information in an asynchronous manner | |
| WO2021189954A1 (en) | Log data processing method and apparatus, computer device, and storage medium | |
| CN112491602B (en) | Behavior data monitoring method and device, computer equipment and medium | |
| US20220147542A1 (en) | Automation solutions for event logging and debugging on kubernetes | |
| US11301475B1 (en) | Transmission handling of analytics query response | |
| CN109783562B (en) | Service processing method and device | |
| CN113760641A (en) | Service monitoring method, device, computer system and computer readable storage medium | |
| CN112187509A (en) | Multi-architecture cloud platform execution log management method, system, terminal and storage medium | |
| EP3616061B1 (en) | Hyper dynamic java management extension | |
| CN113449339A (en) | Log collection method, system, computer device and computer readable storage medium | |
| CN107391528B (en) | Front-end component dependent information searching method and equipment | |
| US11526501B2 (en) | Materialized views assistant | |
| CN108696559B (en) | Stream processing method and device | |
| CN113535668A (en) | Log data processing method and device | |
| CN117389830A (en) | Cluster log acquisition method and device, computer equipment and storage medium | |
| CN112463549A (en) | Auditing method, device and equipment of cloud platform and computer readable storage medium | |
| CN110881030A (en) | Logstack-based method and device for recording operation logs of web service administrator | |
| CN116244186A (en) | Operating system test management method and device and computing equipment | |
| CN112416875B (en) | Log management method, device, computer equipment and storage medium | |
| CN114153703A (en) | Micro-service exception positioning method and device, electronic equipment and program product | |
| CN113448985A (en) | API (application program interface) interface generation method, calling method and device and electronic equipment |
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: 20210105 |
|
| WW01 | Invention patent application withdrawn after publication |