CN111897704A - Session log analysis method, electronic device and storage medium - Google Patents
Session log analysis method, electronic device and storage medium Download PDFInfo
- Publication number
- CN111897704A CN111897704A CN202010601450.1A CN202010601450A CN111897704A CN 111897704 A CN111897704 A CN 111897704A CN 202010601450 A CN202010601450 A CN 202010601450A CN 111897704 A CN111897704 A CN 111897704A
- Authority
- CN
- China
- Prior art keywords
- session
- log analysis
- analysis result
- identification information
- log
- 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
- 238000004458 analytical method Methods 0.000 title claims abstract description 106
- 238000000034 method Methods 0.000 claims abstract description 35
- 230000004931 aggregating effect Effects 0.000 claims abstract description 6
- 238000013507 mapping Methods 0.000 claims description 2
- 238000013024 troubleshooting Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 5
- 230000006854 communication Effects 0.000 description 4
- 238000004891 communication Methods 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
- 238000012545 processing Methods 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000001174 ascending effect Effects 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 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/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a session log analysis method, electronic equipment and a storage medium. The method comprises the following steps: acquiring a service log of a plurality of equipment terminals, wherein the plurality of equipment terminals comprise a terminal, a server terminal and an opposite terminal; aggregating the service logs belonging to the same session in the service logs of the multiple equipment terminals to obtain the service logs of the same session; and analyzing the service log of the session to obtain a log analysis result corresponding to the session. By means of the method, the efficiency and the accuracy of session log analysis can be improved.
Description
Technical Field
The present application relates to the field of network communication technologies, and in particular, to a session log analysis method, an electronic device, and a storage medium.
Background
The log refers to messages output by the service at the equipment end in the execution process, and the messages output by the same service can be associated through a session. When a service fails in the execution process, the reason of the failure can be found by analyzing the corresponding log. The existing method for analyzing the logs is to analyze the multi-end logs participating in the conversation manually, so the efficiency of analysis and the accuracy of the analysis result are limited by the self analysis capability of people.
Disclosure of Invention
The application provides a conversation log analysis method, an electronic device and a storage medium, which can solve the problem that the efficiency and the accuracy of the existing conversation log analysis method are not high enough.
In order to solve the technical problem, the application adopts a technical scheme that: provided is a session log analysis method, including: acquiring a service log of a plurality of equipment terminals, wherein the plurality of equipment terminals comprise a terminal, a server terminal and an opposite terminal; aggregating the service logs belonging to the same session in the service logs of the multiple equipment terminals to obtain the service logs of the same session; and analyzing the service log of the session to obtain a log analysis result corresponding to the session.
In order to solve the above technical problem, another technical solution adopted by the present application is: an electronic device is provided, which comprises a processor and a memory connected with the processor, wherein the memory stores program instructions; the processor is configured to execute the program instructions stored by the memory to implement the above-described method.
In order to solve the above technical problem, the present application adopts another technical solution that: there is provided a storage medium storing program instructions that when executed enable the above method to be implemented.
By the mode, the service logs belonging to the same session in the service logs of the multiple equipment ends are aggregated together for automatic analysis, and the log analysis result of each session is obtained, so that the log analysis process is simplified, and compared with manual log analysis, the efficiency and accuracy of log analysis are improved.
Drawings
FIG. 1 is a schematic flow chart diagram illustrating a first embodiment of a session log analysis method according to the present application;
FIG. 2 is a flowchart illustrating a second embodiment of a session log analysis method according to the present application;
FIG. 3 is a flowchart illustrating a third embodiment of a session log analysis method according to the present application;
FIG. 4 is a flowchart illustrating a fourth embodiment of a session log analysis method according to the present application;
FIG. 5 is a flowchart illustrating a fifth embodiment of a session log analysis method according to the present application;
FIG. 6 is a schematic structural diagram of an embodiment of an electronic device of the present application;
FIG. 7 is a schematic structural diagram of an embodiment of a storage medium according to the present application.
Detailed Description
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 only a part of the embodiments of the present application, 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 application.
The terms "first", "second" and "third" in this application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implying any indication of the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of the feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless explicitly specifically limited otherwise.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those skilled in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.
When a service at a device end fails in an execution process, the service cannot be normally executed, and in order to find a cause of the failure, the existing scheme is as follows:
downloading corresponding service logs from terminals related to service execution respectively, then manually finding out session identifications appearing in the two service logs to form a session identification list, and analyzing the service end logs one by one according to the session identification list to find out the reasons of service failures.
Therefore, the existing scheme needs a large amount of trivial manual operation, and requires a high proficiency level of a person who analyzes the service, otherwise, the reason of the fault is difficult to be checked according to the log. Therefore, the application provides a conversation log analysis method, which specifically comprises the following steps:
fig. 1 is a schematic flow chart of a first embodiment of a session log analysis method according to the present application. It should be noted that, if the result is substantially the same, the flow sequence shown in fig. 1 is not limited in this embodiment. As shown in fig. 1, the present embodiment includes:
s110: and acquiring a service log of the multi-device terminal.
The multi-device end comprises a terminal, a server end and an opposite end. The terminal and the opposite terminal can be devices or devices with communication functions, such as a mobile phone, a camera, a computer and the like. The server can be a server or a cloud platform established on the server.
The information output in the service execution process of the device end is called a service log. The service log referred to in the present application is a log of a session-based service, that is, information output in a session-type service execution process at a device side. Conversational services are generally real-time, so conversational services may also be referred to as conversational real-time streaming services, which are capable of providing bi-directional communication between a plurality of end users. The session type service may include a call service, a video service, and the like.
The execution of one session type service is accompanied with the generation and storage of a log. Moreover, for the same session type service, the terminal, the server and the opposite terminal involved in the execution process all store corresponding logs, so the logs of the session type service can be obtained from the logs of the terminal, the server and the opposite terminal. The service log can be obtained from the multi-device side log according to a preset time length, and the service log can also be obtained from the multi-device side log under external triggering.
S120: and aggregating the service logs belonging to the same session in the service logs of the multiple equipment ends to obtain the service logs of the same session.
The service logs of multiple device ends can be aggregated by taking the session as a dimension, so that the service logs of the same session can be obtained.
Optionally, in the service logs of the multiple device ends, the service logs containing the same session identification information are aggregated into the service log of the same session.
In the process of executing the service, the server establishes a session for the service and gives a session identifier, and the session identifier is recorded in a service log. The session identifiers recorded in the logs of the same service are the same, so that the service logs can be aggregated based on the session identifier information recorded in the service logs, and the service logs recorded with the same identifier information, namely the service logs of the same session, are obtained.
S130: and analyzing the service log of the session to obtain a log analysis result corresponding to the session.
The service log of each session obtained by aggregation may be analyzed based on the service logic and/or information recorded in the log, so as to obtain a log analysis result of each session.
Optionally, a service log of the session is analyzed, and at least one of the following log analysis results of the corresponding session may be obtained: whether the session is successful, the reason for the failure, the session link, the session duration, the software version of at least one device side, and the session setup time.
The information contained in the log can be analyzed based on the service logic to judge whether the session is successful or not, and find out the reason of failure and the session link. The session duration, the device software version and the session establishment time can be directly obtained based on the information contained in the log.
By the mode, the service logs belonging to the same session in the service logs of the multiple equipment ends are aggregated together for automatic analysis, and the log analysis result of each session is obtained, so that the log analysis process is simplified, and compared with manual log analysis, the efficiency and accuracy of log analysis are improved.
Fig. 2 is a flowchart illustrating a second embodiment of a session log analysis method according to the present application. It should be noted that, if the result is substantially the same, the flow sequence shown in fig. 2 is not limited in this embodiment. This embodiment is a further extension of the first embodiment, and please refer to the first embodiment as above, as shown in fig. 2, in this embodiment, after S130, the method further includes:
s210: and storing the log analysis result of the session to a preset storage space.
When a failure occurs in the service execution process, the reason for the transmission failure can be obtained based on the log analysis result of the corresponding session. In order to facilitate the search of the subsequent log analysis result, the log analysis result of the session can be stored in a preset storage space. The preset storage space may be, but not limited to, MongoDB, ElasitcSearch, Redis, HBase.
For convenient storage, the log analysis result of the session can be structurally stored in a preset storage space. Specifically, a structured log analysis result may be generated based on each log analysis result of the same session, where the structured log analysis result includes each log analysis result of the same session, and then stored in a preset storage space. Of course, in other embodiments, the log analysis results of the same session may be directly stored in the preset storage space. The selection of the specific storage mode can be determined according to actual requirements.
S220: and receiving a query instruction of the session, and searching and displaying a log analysis result of the session from a preset storage space.
The query instruction may be an instruction input by a user according to a fault query requirement, and is used for querying a log analysis result of the session. Optionally, the query instruction includes identification information of at least one device side or identification information of a session to be queried.
For example, when a service sends a failure in the execution process, a user wants to query the cause of the failure, and may search a log analysis result of a session from a preset storage space based on a corresponding device identifier or session identifier, and then obtain the cause of the failure based on the displayed log analysis result.
By the mode, the log analysis result of the session can be stored in the preset storage space, and the reason of the fault is recorded in the structured log analysis result of the session corresponding to the fault service, so that when a user has a fault query requirement, the log analysis result of the corresponding session can be directly queried from the preset storage space, and the fault reason can be obtained based on the queried log analysis result.
Fig. 3 is a flowchart illustrating a third embodiment of the session log analysis method according to the present application. It should be noted that, if the result is substantially the same, the flow sequence shown in fig. 3 is not limited in this embodiment. In this embodiment, the predetermined storage space is a search server (e.g., ElasitcSearch), wherein S310 to S320 are further extensions of S210 in the second embodiment, and S330 to S340 are further extensions of S220 in the second embodiment. As shown in fig. 3, the present embodiment includes:
s310: and storing the log analysis result of the session and the corresponding identification information into the search server.
The corresponding identification information is identification information of at least one device participating in the session and/or identification information of the session.
S320: and receiving a query instruction input by a user through the fault query website.
Optionally, the trouble shooting website is established based on Vue or boottrap. And may be constructed in other ways in other embodiments, and is not limited herein. The user can input a query instruction in the fault query website according to the fault query requirement. Optionally, the query instruction includes identification information of at least one device side or identification information of a session to be queried.
S330: and sending a query request containing the identification information in the query instruction to the search server.
The search server is associated with the fault query website, so that a corresponding query request can be generated and sent to the search server based on a query instruction input by a user through the fault query website.
S340: and displaying a log analysis result of the session corresponding to the identification information in the query request, which is fed back by the search server, on the fault query website.
The search server can find out the log analysis result of the corresponding session according to the received query request and feed the log analysis result back to the fault query website, so that the fault query website displays the log analysis result of the found session.
Through the method, the log analysis result of the corresponding session can be searched from the search server based on the fault query website and displayed to the user, so that the user can know the reason of the fault.
Fig. 4 is a flowchart illustrating a fourth embodiment of the session log analysis method according to the present application. It should be noted that, if the result is substantially the same, the flow sequence shown in fig. 4 is not limited in this embodiment. In this embodiment, the preset storage space is a search server (e.g., elastcsearch) and a preset database (e.g., HBase), where S410 to S420 are further extensions of S210 in the second embodiment, and S430 to S450 are further extensions of S220 in the second embodiment, as shown in fig. 4, this embodiment includes:
s410: and storing the log analysis result of the session into a preset database, and acquiring a storage index of the log analysis result of the session.
The log analysis results of the session can be directly stored in a preset database, and the log analysis results of the session can also be structurally stored in the preset database. A storage index may be established for the log analysis result record of each session stored in the preset data, where the storage index is used to indicate a location where the log analysis result of the corresponding session is stored in the preset database.
When the log analysis results of a session are directly stored in a preset database, a corresponding storage index needs to be established for each log analysis result of the same session, and the storage indexes of each log analysis result of the same session may be the same or different. And when the log analysis results of the session are structurally stored in a preset database, the log analysis results of the same session correspond to a storage index.
S420: and storing the mapping relation between the storage index of the session and the corresponding identification information in the search server.
The identification information corresponding to the storage index may include at least one of session identification and device-side identification participating in the session.
S430: and receiving a query instruction input by a user through the fault query website.
S440: and sending a query request containing the identification information in the query instruction to the search server.
For detailed descriptions of S430-S440, refer to S320-330 above, and are not repeated here.
S450: and displaying a log analysis result of the session corresponding to the identification information in the query request, which is fed back by the search server, on the fault query website.
And the fed-back log analysis result of the session is searched by the search server from a preset database.
Different from the third embodiment, in this embodiment, the fault query website is associated with the search server and the preset database, the fault query website may generate a query request based on a query instruction input by a user and send the query request to the search server, and the search server may find out a storage index corresponding to identification information carried in the query request, and search for a corresponding log analysis result in the preset database based on the storage index and feed the log analysis result back to the fault query website, so that the fault query website displays the log analysis result to the user.
According to the method, the log analysis results of the session are stored in the preset database, and the storage index corresponding to each log analysis result record stored in the preset database is stored in the search server, so that when a user has a query requirement, a query instruction can be input through fault query, the storage index of the log analysis result corresponding to the session is found in the search server, and then the log analysis result corresponding to the session is found in the preset database based on the storage index, so that the query efficiency of the search server can be improved.
Fig. 5 is a flowchart illustrating a fifth embodiment of a session log analysis method according to the present application. It should be noted that, if the result is substantially the same, the flow sequence shown in fig. 5 is not limited in this embodiment. The present embodiment is a further extension of S340 and/or S450, where the query instruction includes identification information of the device side. As shown in fig. 5, the present embodiment may include:
s510: and receiving a log analysis result of the session corresponding to the identification information of the equipment terminal fed back by the search server.
S520: if a plurality of received conversations corresponding to the identification information of the equipment end exist, displaying log analysis results of the plurality of received conversations corresponding to the identification information in the query request on the fault query website according to the sequence of the conversation establishment time.
When a plurality of sessions corresponding to the identification information of the equipment end exist, the fault query website can display corresponding log analysis results in an ascending order or a descending order according to the session establishment time, and a user can conveniently check the log analysis results.
Fig. 6 is a schematic structural diagram of an embodiment of an electronic device according to the present application. As shown in fig. 6, the electronic device includes a processor 610, a memory 620 coupled to the processor.
Wherein the memory 620 stores program instructions for implementing the methods of any of the embodiments described above; the processor 610 is configured to execute program instructions stored by the memory 620 to implement the steps of the above-described method embodiments. The processor 610 may also be referred to as a Central Processing Unit (CPU). The processor 610 may be an integrated circuit chip having signal processing capabilities. The processor 610 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
FIG. 7 is a schematic structural diagram of an embodiment of a storage medium according to the present application. As shown in fig. 7, a storage medium 700 of the embodiment of the present application stores program instructions 710, and the program instructions 710 implement the methods provided by the above-mentioned embodiments of the present application when executed. The program instructions 710 may form a program file stored in the storage medium 700 in the form of a software product, so as to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute all or part of the steps of the methods according to the embodiments of the present application. And the aforementioned storage medium 700 includes: various media capable of storing program codes, such as a usb disk, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, or terminal devices, such as a computer, a server, a mobile phone, and a tablet.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, 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, devices or units, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. The above embodiments are merely examples and are not intended to limit the scope of the present disclosure, and all modifications, equivalents, and flow charts using the contents of the specification and drawings of the present disclosure or those directly or indirectly applied to other related technical fields are intended to be included in the scope of the present disclosure.
Claims (10)
1. A method for analyzing a session log, comprising:
acquiring a service log of a plurality of equipment terminals, wherein the plurality of equipment terminals comprise a terminal, a server terminal and an opposite terminal;
aggregating the service logs belonging to the same session in the service logs of the multiple equipment terminals to obtain the service logs of the same session;
and analyzing the service log of the session to obtain a log analysis result corresponding to the session.
2. The method according to claim 1, wherein the aggregating the service logs belonging to the same session in the service logs of the multiple device sides to obtain the service logs of the same session includes:
and aggregating the service logs containing the same session identification information into the service log of the same session in the service logs of the multiple equipment ends.
3. The method of claim 1, wherein the analyzing the service log of the session to obtain a log analysis result corresponding to the session comprises:
analyzing the service log of the session to obtain at least one log analysis result corresponding to the session: whether the session is successful, the reason for the failure, the session link, the session duration, the software version of at least one device side, and the session setup time.
4. The method according to claim 1, wherein after analyzing the service log of the session to obtain a log analysis result corresponding to the session, the method further comprises:
storing the log analysis result of the session to a preset storage space;
and receiving a query instruction of the conversation, and searching and displaying a log analysis result of the conversation from the preset storage space.
5. The method according to claim 4, wherein the storing the log analysis result of the session to a preset storage space comprises:
and storing the log analysis result of the conversation to the preset storage space in a structured manner.
6. The method according to claim 4, wherein the storing the log analysis result of the session to a preset storage space comprises:
storing the log analysis result of the session and the corresponding identification information into a search server; the corresponding identification information is identification information of at least one device participating in the conversation and/or identification information of the conversation; and the number of the first and second groups,
the receiving the query instruction of the session, and searching and displaying the log analysis result of the session from the preset storage space includes:
receiving a query instruction input by a user through a fault query website, wherein the query instruction comprises identification information of at least one equipment terminal or identification information of a session to be queried;
sending a query request containing the identification information in the query instruction to the search server;
and displaying the log analysis result of the session corresponding to the identification information in the query request, which is fed back by the search server, on the fault query website.
7. The method according to claim 4, wherein the storing the log analysis result of the session to a preset storage space comprises:
storing the log analysis result of the session into a preset database, and acquiring a storage index of the log analysis result of the session;
storing a mapping relationship between the storage index of the session and corresponding identification information in the search server;
the receiving the query instruction of the session, and searching and displaying the log analysis result of the session from the preset storage space includes:
receiving a query instruction input by a user through a fault query website, wherein the query instruction comprises identification information of at least one equipment terminal or identification information of a session to be queried;
sending a query request containing the identification information in the query instruction to the search server;
displaying, on the fault query website, a log analysis result of the session corresponding to the identification information in the query request, which is fed back by the search server, where the fed back log analysis result of the session is found by the search server from the preset database.
8. A method according to claim 6 or 7, wherein the troubleshooting website is established based on Vue or Bootstrap, and/or,
the query instruction includes identification information of the device side, and the displaying, at the fault query website, a log analysis result of the session corresponding to the identification information in the query request, which is fed back by the search server, includes:
receiving a log analysis result of the session corresponding to the identification information of the equipment terminal, which is fed back by the search server;
if a plurality of received conversations corresponding to the identification information of the equipment end exist, displaying log analysis results of the plurality of received conversations corresponding to the identification information in the query request on the fault query website according to the sequence of the conversation establishment time.
9. An electronic device comprising a processor, a memory coupled to the processor, wherein,
the memory stores program instructions;
the processor is configured to execute the program instructions stored by the memory to implement the method of any of claims 1-8.
10. A storage medium, characterized in that the storage medium stores program instructions that, when executed, implement the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010601450.1A CN111897704A (en) | 2020-06-28 | 2020-06-28 | Session log analysis method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010601450.1A CN111897704A (en) | 2020-06-28 | 2020-06-28 | Session log analysis method, electronic device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111897704A true CN111897704A (en) | 2020-11-06 |
Family
ID=73207083
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010601450.1A Pending CN111897704A (en) | 2020-06-28 | 2020-06-28 | Session log analysis method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111897704A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116723079A (en) * | 2022-10-31 | 2023-09-08 | 荣耀终端有限公司 | Log grabbing method, electronic equipment and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103838867A (en) * | 2014-03-20 | 2014-06-04 | 网宿科技股份有限公司 | Log processing method and device |
| CN109687991A (en) * | 2018-09-07 | 2019-04-26 | 平安科技（深圳）有限公司 | User behavior recognition method, apparatus, equipment and storage medium |
| CN111026616A (en) * | 2019-12-24 | 2020-04-17 | 北京奇艺世纪科技有限公司 | Information processing method and device, electronic equipment and storage medium |
| CN111209258A (en) * | 2019-12-31 | 2020-05-29 | 航天信息股份有限公司 | Tax end system log real-time analysis method, equipment, medium and system |
-
2020
- 2020-06-28 CN CN202010601450.1A patent/CN111897704A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103838867A (en) * | 2014-03-20 | 2014-06-04 | 网宿科技股份有限公司 | Log processing method and device |
| CN109687991A (en) * | 2018-09-07 | 2019-04-26 | 平安科技（深圳）有限公司 | User behavior recognition method, apparatus, equipment and storage medium |
| CN111026616A (en) * | 2019-12-24 | 2020-04-17 | 北京奇艺世纪科技有限公司 | Information processing method and device, electronic equipment and storage medium |
| CN111209258A (en) * | 2019-12-31 | 2020-05-29 | 航天信息股份有限公司 | Tax end system log real-time analysis method, equipment, medium and system |
Non-Patent Citations (1)
| Title |
|---|
| 周继恩 等: "银行卡跨行交易系统群的故障分析方法", 《计算机系统应用》, vol. 26, no. 11, 30 November 2017 (2017-11-30), pages 60 - 66 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116723079A (en) * | 2022-10-31 | 2023-09-08 | 荣耀终端有限公司 | Log grabbing method, electronic equipment and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109981349B (en) | Call chain information query method and device | |
| US20110141919A1 (en) | Method and system for virtual agent session monitoring and barge-in | |
| CN108810657B (en) | Method and system for setting video cover | |
| CN112069034B (en) | Fast application exception handling method and device, electronic equipment and storage medium | |
| CN107181821A (en) | A kind of information push method and device based on SSE specifications | |
| EP3657335A1 (en) | Method, device, and apparatus for tracking and monitoring software behavior | |
| CN113839977A (en) | Message pushing method and device, computer equipment and storage medium | |
| CN108733666B (en) | Server information pushing method, terminal information sending method, device and system | |
| US20230269304A1 (en) | Method and apparatus for processing notification trigger message | |
| CN107329976B (en) | Webpage paging method and device, computer equipment and computer readable storage medium | |
| CN115951923B (en) | Subscription event management method, display system, device and storage medium | |
| CN110166823B (en) | Screen projection method and related device | |
| CN116055551A (en) | Information pushing method, device and system, electronic equipment and storage medium | |
| CN111897704A (en) | Session log analysis method, electronic device and storage medium | |
| CN114416508A (en) | Application performance monitoring method and device, storage medium and electronic equipment | |
| CN112235615B (en) | Method and system for communicating and using portrait data of television terminal user | |
| CN108390770B (en) | Information generation method and device and server | |
| US9485458B2 (en) | Data processing method and device | |
| CN116233048A (en) | Customer service session request processing method and related equipment | |
| WO2022262472A1 (en) | Frame rate processing method and apparatus, storage medium, and terminal | |
| CN112965835A (en) | Method and terminal for efficiently displaying offline message | |
| CN111130983B (en) | Method and equipment for sending information and generating result information | |
| CN110233747B (en) | Data reporting method and cloud platform | |
| CN114449031A (en) | Information acquisition method, device, equipment and storage medium | |
| CN110401841B (en) | Method, device, equipment and storage medium for analyzing messages in live broadcast room |
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 |