CN110888790A - Log management method and device, electronic equipment and storage medium - Google Patents

Log management method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN110888790A
CN110888790A CN201911205624.6A CN201911205624A CN110888790A CN 110888790 A CN110888790 A CN 110888790A CN 201911205624 A CN201911205624 A CN 201911205624A CN 110888790 A CN110888790 A CN 110888790A
Authority
CN
China
Prior art keywords
log
client
number information
server
logs
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201911205624.6A
Other languages
Chinese (zh)
Other versions
CN110888790B (en
Inventor
李佳琦
符志清
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou DPTech Technologies Co Ltd
Original Assignee
Hangzhou DPTech Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hangzhou DPTech Technologies Co Ltd filed Critical Hangzhou DPTech Technologies Co Ltd
Priority to CN201911205624.6A priority Critical patent/CN110888790B/en
Publication of CN110888790A publication Critical patent/CN110888790A/en
Application granted granted Critical
Publication of CN110888790B publication Critical patent/CN110888790B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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

Abstract

The application provides a log management method and device, electronic equipment and a storage medium; the method is applied to a server side, and a log generated by the server side is configured with corresponding number information; the method may include: receiving a log query request sent by a client, wherein the log query request comprises history number information of a log acquired by the client from a server; comparing the historical number information with number information of a locally generated log to judge whether an unacquired log corresponding to the client exists or not; and when the fact that the logs which correspond to the client and are not obtained exist is judged, returning a judgment result to the client. According to the method and the system, whether the log which is not acquired exists is judged by comparing the number information of the log stored by the client with the number information of the log generated by the server, so that an administrator can conveniently acquire the log which is not acquired in time, and the system is maintained according to the log information.

Description

Log management method and device, electronic equipment and storage medium
Technical Field
The present application relates to the field of network communications, and in particular, to a log management method and apparatus, an electronic device, and a storage medium.
Background
The log is a very critical file during the operation of the system. The log can help a user of the system to fully know the running environment of the system, and the user can know events occurring before and after the system fails so that the user can perform corresponding processing according to the condition of the system. In addition, in case of an emergency such as an attack, an emergency log different from other logs is generated to inform the user of the message of the attack and the specific situation of the system after the attack.
Disclosure of Invention
In view of this, the present application provides a log management method and apparatus, an electronic device, and a storage medium, which can help an administrator to timely know whether there is an unacquired log, so that the administrator can timely acquire the unacquired log, and maintain a system according to acquired log information.
In order to achieve the above purpose, the present application provides the following technical solutions:
according to a first aspect of the present application, a log management method is provided, which is applied to a server, where a log generated by the server is configured with corresponding number information; the method comprises the following steps:
receiving a log query request sent by a client, wherein the log query request comprises history number information of a log acquired by the client from a server;
comparing the historical number information with number information of a locally generated log to judge whether an unacquired log corresponding to the client exists or not;
and when the log which is not acquired is judged to exist, returning a judgment result to the client.
According to a second aspect of the present application, a log management method is provided, which is applied to a client; the log is generated by a server side, and the log generated by the server side is configured with corresponding number information; the method comprises the following steps:
creating a log query request, wherein the log query request comprises history number information of a log acquired by the client from the server;
sending a log query request to the server, so that the server compares the historical number information with the number information of the log locally generated by the server, and judges whether an unacquired log corresponding to the client exists or not;
and receiving a judgment result returned by the server, wherein the judgment result is generated when the server judges that the unacquired log exists.
According to a third aspect of the present application, a log management apparatus is provided, which is applied to a server, and a log generated by the server is configured with corresponding number information; the device comprises:
the system comprises a receiving unit, a log query unit and a log processing unit, wherein the log query unit receives a log query request sent by a client, and the log query request comprises history number information of a log acquired by the client from a server;
the comparison unit is used for comparing the historical number information with the number information of the locally generated log so as to judge whether the log which is not acquired and corresponds to the client exists or not;
and the returning unit returns a judgment result to the client when judging that the unacquired log exists.
According to a fourth aspect of the present application, a log management apparatus is provided, which is applied to a client; the log is generated by a server side, and the log generated by the server side is configured with corresponding number information; the method comprises the following steps:
the creating unit is used for creating a log query request, wherein the log query request comprises the historical number information of the log acquired by the client from the server;
the sending unit is used for sending a log query request to the server so that the server compares the historical number information with the number information of the log locally generated by the server to judge whether the log which is not acquired and corresponds to the client exists or not;
and the receiving unit is used for receiving a judgment result returned by the server, and the judgment result is generated when the server judges that the unacquired log exists.
According to a fifth aspect of the present application, there is provided an electronic device comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method as in any of the above embodiments by executing the executable instructions.
According to a sixth aspect of the present application, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method as described in any of the above embodiments.
In the technical scheme of the application, the server configures number information for the generated log, and the client records the number information of the obtained log after obtaining the log from the server. Based on the mechanism for numbering the logs, when a requirement for acquiring a log newly generated by a server exists, the client can send a request containing the number information of the log stored by the client to the server, so that the server can judge whether an unacquired log corresponding to the client exists or not by comparing the number information of the log stored by the client with the number information of the log generated by the server, and return the judged result to the client, and inform an administrator of the existence of the unacquired log.
Furthermore, when the logs which are not acquired and correspond to the client exist, the logs which are not acquired are determined in a comparison number mode, so that the logs which are acquired and the logs which are not acquired are distinguished, an administrator can conveniently manage the logs respectively, and the situations that the working efficiency is low and the logs are missed to be read due to the fact that the logs which are acquired and the logs which are not acquired cannot be distinguished are avoided.
Drawings
Fig. 1 is a flowchart illustrating a method for server-based log management according to an exemplary embodiment of the present application.
Fig. 2 is a flowchart illustrating a method for client-based log management according to an exemplary embodiment of the present application.
Fig. 3 is an interaction diagram illustrating a log management method according to an exemplary embodiment of the present application.
Fig. 4 is an interaction diagram illustrating another log management method according to an exemplary embodiment of the present application.
Fig. 5 is a schematic structural diagram of a server-based electronic device according to an exemplary embodiment of the present application.
Fig. 6 is a block diagram illustrating a server-based log management apparatus according to an exemplary embodiment of the present application.
Fig. 7 is a schematic structural diagram of a client-based electronic device according to an exemplary embodiment of the present application.
Fig. 8 is a block diagram of a client-based log management apparatus according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The log plays an extremely important role in the system operation process, and can help an administrator to know the system operation condition so as to maintain the system according to the information reflected by the log in real time. In addition, under the condition that the system is attacked, the log system can generate an emergency log immediately to inform an administrator of the message that the system is attacked, so that the administrator can process the attack condition of the system as soon as possible.
In order to facilitate the administrator to review the log in time, the related art places the log message in a function bar at the top of the WEB page, so that the administrator can open the log display page for review by clicking the log message when the administrator wants to review the log.
However, in the related art, the client cannot timely know whether a new log that has not been acquired exists at the server, and cannot distinguish a history unacquired log from a history acquired log in the acquired logs after acquiring the new log.
In order to solve the technical problem, the application provides a log management method. Referring to fig. 1, fig. 1 is a flowchart illustrating a method for server-based log management according to an exemplary embodiment of the present application. As shown in fig. 1, the method is applied to a server, and a log generated by the server is configured with corresponding number information; the method may comprise the steps of:
step S102, receiving a log query request sent by a client, wherein the log query request comprises history number information of a log acquired by the client from the server.
In the present embodiment, one server for log management may correspond to a plurality of clients in most cases. Therefore, in order to distinguish between multiple clients, each client is configured with a corresponding administrator identification. In this case, the server may configure a block of storage space for each client to store the log corresponding to each client.
In such a log management system, a log query request sent by a client includes an administrator identifier corresponding to the client. When a server receives a log query request, firstly reading an administrator identification in the received log query request to determine a client side sending the log query request; and acquiring the number information of the locally generated log from a storage space configured for the client in the server, and comparing the number information with the historical number information corresponding to the administrator identification acquired from the log query request to determine whether an unacquired log corresponding to the client exists in the server.
In this step, the history number information included in the log query request may be detected by the client from the number of the log that has been obtained locally from the server, and when the log query request is created, the detected number is written into a certain field of the log query request, so that the server reads the field to obtain the history number information when receiving the log query request. Of course, how to write the history number information into the log query request by the client may be different according to the actual situation by those skilled in the art, and is not limited in detail herein.
In addition, in order to obtain whether a message of not obtaining a log exists in time, the client may send a log query request to the server at regular time. Of course, the timing operation mode can be determined by those skilled in the art according to practical situations, and is not limited herein. The timing time can be set by an administrator according to actual needs and the condition of the system.
Step S104, comparing the historical number information with the number information of the locally generated log to judge whether the log which is not acquired and corresponds to the client exists.
In the embodiment of the application, there may be a plurality of configuration methods for configuring the number information for the log generated by the server, and for different configuration methods, there may also be a plurality of cases for the history number information of the log obtained from the server included in the log query request.
In an embodiment, the server sorts the generated logs according to the time sequence of generation to obtain the number of each log. In this case, the history number information included in the log query request may be the maximum number of the log acquired by the client from the server. At this time, whether a log that the client has not acquired exists can be determined by comparing the maximum number with the maximum number of the log generated by the server. When the maximum number is judged to be smaller than the maximum number of the log generated by the server, determining that the log which is not acquired and corresponds to the client exists; otherwise, it is determined that there is no uncaptured log corresponding to the client.
The advantage of numbering the logs by the temporal order of generation is that the client only needs to write one log number when generating the log query request. Secondly, when the server compares the historical number information with the number information of the local log, only one piece of local number information needs to be read for comparing with the historical number information, the number information of all logs does not need to be acquired, and the occupation of processing resources of the server is reduced.
In another embodiment, the history number information included in the log query request may be all numbers of logs acquired by the client from the server. At this time, the number of the log locally generated by the server may be compared with all numbers of the log at the client, and whether the number of the log locally generated by the server is different from the numbers of all log numbers at the client is determined; if so, determining that an unacquired log corresponding to the client exists; otherwise, determining that there is no uncaptured log corresponding to the client.
The advantage of writing all numbers of the logs acquired by the client from the server into the log query request is that the method for numbering the generated logs by the server is not strictly required, and only the numbers between the logs are not repeated, so that the method for judging whether the logs are not acquired can be suitable for more scenes.
And step S106, when the situation that the logs which correspond to the client and are not acquired exist is judged, a judgment result is returned to the client.
In the present embodiment, when the determination result is obtained by executing step S102 and step S104, the result of the determination may be returned only when the determination result is that there is an unacquired log corresponding to the client; the determination result may be returned as long as the determination result is obtained (regardless of whether the determination result is the presence of the unacquired log or the absence of the unacquired log).
When it is determined that the unacquired log corresponding to the client exists, the result returned by the server may be only the result of the unacquired log; the service end can also distinguish the logs corresponding to the client end generated in the service end based on the result so as to return the determined logs which are not obtained to the client end. If the server only returns the result that the log is not acquired, the log corresponding to the client generated in the server can be distinguished when the request which is not acquired and sent by the user is received, so as to determine the log which is not acquired, and the log is returned to the client. When the determined log which is not acquired is returned to the client, only the log which is not acquired can be returned, or the determined log which is not acquired and other logs corresponding to the client can be returned together.
In this step, when it is determined that there is an unacquired log corresponding to the client, an unacquired log corresponding to the client in the server may be further determined.
In an embodiment, the server side numbers the logs according to the generated time sequence in step S104, and then the history number information included in the log query request is the maximum number of the log obtained by the client side from the server side. At this time, if a mode of "only returning a result that an unacquired log exists when it is determined that an unacquired log exists" is adopted, when a log acquisition request for the unacquired log sent by the client is received, the server compares the history number information with the maximum number of the local log, determines the local log with the number greater than the history number information as the unacquired log, and returns the local log to the client.
Similarly, if the method of returning the result of the log not obtained and the log not obtained together is adopted, the log not obtained is directly determined according to the method without waiting for the client to send the log obtaining request, and the log not obtained and the judgment result are returned together. Of course, since returning the non-acquired log already means that there is a non-acquired log, only the non-acquired log may be returned. The content returned may be determined by those skilled in the art according to practical circumstances, and is not particularly limited herein.
In another embodiment, the way in which the server numbers the logs is not limited, that is, the history number information included in the log query request in step S104 is all numbers of the logs acquired by the client from the server. At this time, if the method of "determining that there is an unacquired log, only returning the result of the unacquired log" is adopted, when a log acquisition request for the unacquired log sent by the client is received, the server compares the history number information with the numbers of all locally generated logs, and returns the local log with the number different from the history number information to the client as the unacquired log.
Similarly, if a mode of returning a result that a log is not obtained and a log is not obtained is adopted, the operation mode is the same as that of the previous embodiment except for the mode of determining the log is not obtained, and details are not described here.
As can be seen from the foregoing technical solutions, in the technical solution of the present application, the server configures number information for the generated log, and the client records the number information of the obtained log after obtaining the log from the server. Based on the mechanism for numbering the logs, when a requirement for acquiring a log newly generated by a server exists, the client can send a request containing the number information of the log stored by the client to the server, so that the server can judge whether an unacquired log corresponding to the client exists or not by comparing the number information of the log stored by the client with the number information of the log generated by the server, and return the judged result to the client, and inform an administrator of the existence of the unacquired log.
Further, when it is determined that the server side has the log which is not acquired and corresponds to the client side, the log which is not acquired and corresponds to the client side is determined by comparing the numbers of the logs stored in the server side and the client side respectively and returned to the client side, so that the administrator can check the log which is not acquired and maintain the system according to the information in the log which is not acquired. By the mode, the manager can distinguish the history un-acquired log from the history acquired log, so that the problems of missing the log, repeatedly watching the same log and the like are avoided.
Referring to fig. 2, fig. 2 is a flowchart illustrating a method for client-based log management according to an exemplary embodiment of the present application. As shown in fig. 2, the method is applied to a client; in the method, a log is generated by a server side, and the log generated by the server side is configured with corresponding number information; the method comprises the following steps:
step S202, a log query request is created, wherein the log query request comprises the history number information of the log acquired by the client from the server.
In this embodiment, the content included in the log query request may refer to the description in step S102, which is not described herein again.
Step S204, a log query request is sent to the server, so that the server compares the historical number information with the number information of the log locally generated by the server, and whether an unacquired log corresponding to the client exists is judged.
In this embodiment, the specific content of the history number information and the specific content of the number information of the locally generated log for comparison can refer to the description in step S104, which is not described herein again.
It should be noted that the action of sending the log query request may be actively sent by the administrator through the client, or a certain sending period may be set for the client, the log query request is periodically sent to the server, and a log newly generated by the server is obtained in time.
Step S206, receiving a judgment result returned by the server, wherein the judgment result is generated when the server judges that the unacquired log exists.
In this embodiment, when the server determines that there is no unacquired log, a determination result may also be returned, and at this time, the client receives a determination result that there is no unacquired log returned by the server. Of course, the specific content returned by the server may refer to the description in step S106, and is not described herein again.
It is noted that after receiving the returned result, the client may display different warning information according to the returned result. For example, a corresponding warning flag is lit, or an alert tone is issued to alert the administrator that there is an unacquired log. When the returned result comprises the determined non-acquired log, the non-acquired log can be directly popped. The specific operation mode can be set by those skilled in the art according to practical situations, and is not limited herein.
According to the technical scheme, the client can acquire the newly generated log of the server in real time in a mode of sending the request at regular time. Furthermore, when a returned result is received or the log is not acquired, corresponding prompt information is sent out at the client, so that an administrator can review the log in time and maintain the system better.
For convenience of understanding, the log management method proposed in the present application is described in detail below with reference to application scenarios and examples.
Referring to fig. 3, fig. 3 is an interaction diagram of a log management method according to an exemplary embodiment of the present application, in which a server sorts logs according to a time sequence of log generation to obtain numbers, and the method may include:
step S301, a log query request is created.
In this embodiment, the client includes a step of detecting a local log and acquiring a local maximum log number in the process of creating the log query request. After the maximum number is detected, the maximum number is written into a log query request to serve as the maximum log number of the client.
Step S302, the client sends a log query request to the server.
In this embodiment, the client may be an administrator terminal, and the log query request is sent by the administrator terminal to the server, so that the server queries a local log and determines whether there is an unacquired log. The administrator can set a sending period for the process of sending the log query request according to the self requirement and the environment of the system. For example, if the administrator wants to obtain in time whether there is a message that the log is not obtained, or the current environment of the system is unstable (i.e., the system condition needs to be monitored at any time), the sending period may be set to be short, for example, 2 seconds, 5 seconds, etc.; if the administrator does not take an urgent need to acquire whether or not there is a message whose log is not acquired, or if the environment in which the system is currently located is stable, the transmission cycle may be set to be long, for example, 10 seconds, 15 seconds, or the like.
Step S303, the server reads the client maximum number included in the log query request.
In this step, since the server generally corresponds to a plurality of clients, this step may further include a process of reading the administrator terminal identification. Of course, the administrator identification is correspondingly required to be written into the log query request in the process of creating the log query request in step S301. In a log management system comprising a plurality of clients, subsequent steps are performed for the client corresponding to the administrator identification or the log corresponding to the administrator identification.
Step S304, the server reads the maximum number of the local log.
If the step is executed in a log management system comprising a plurality of clients, the server reads the maximum number of the log which is locally stored and corresponds to the administrator identification.
Step S305, the server compares the maximum number of the client with the maximum number of the local log to obtain whether a result that the log is not acquired exists.
In this embodiment, when it is determined that the maximum number of the client log is smaller than the maximum number of the server local log, it is proved that a log with a number larger than the maximum number of the log stored by the client exists in the log locally generated by the server, and at this time, it is determined that a log which is not acquired exists; otherwise, it is determined that there is no uncaptured log. In this embodiment, the result is returned to the client regardless of whether or not there is an unacquired log.
For example, assume that the numbers of all logs acquired by the client from the server are 1, 2, 3, and 4, and the numbers of all logs generated by the server are 1, 2, 3, 4, 5, and 6. Then, the maximum log number read by the server from the log query request is 4, and the maximum number of the read local log is 6. At this time, the maximum number of the log stored in the client is found to be smaller than the maximum number of the local log (4 is smaller than 6) after the two are compared, and it is determined that the log which is not acquired exists. If the maximum number of the local log is also 4 in this example, it is determined that there is no uncaptured log.
Step S306, the server side returns the judged result to the client side.
If the step is executed in a log management system comprising a plurality of clients, the server returns a judgment result to the client corresponding to the administrator identification.
In step S307, the client receives the returned determination result.
In this embodiment, an automatic acquisition switch may be provided. The automatic acquisition switch has the effect that when an administrator wants to acquire logs which are not acquired immediately under the condition that the logs which are not acquired exist, as long as the automatic acquisition switch is turned on, the client terminal can actively initiate log acquisition requests to the server terminal when receiving a return result that the logs which are not acquired exist, and the administrator does not need to manually initiate the requests. On the contrary, when the automatic acquisition switch is turned off, even if the client receives a return result that the log is not acquired, the client does not actively initiate the log acquisition request and needs an administrator to manually initiate the log acquisition request.
In step S308, the client determines whether the returned determination result is that there is an unacquired log.
In this embodiment, when it is determined that the returned result is that there is an unacquired log, a log acquisition request is further created to acquire the unacquired log existing in the server (i.e., step S309 is performed); and when the returned result is determined that the log which is not acquired does not exist, ending the interaction.
In addition, when the returned result is determined that the log which is not acquired exists, a corresponding warning mark can be lightened on a specific interface (such as a WEB interface) of the client so as to inform an administrator of the existence of the log which is not acquired; of course, upon determining that there is no unrecognized log, another warning flag may be lit to inform the administrator that there is no unrecognized log.
In this embodiment, when it is determined that the received determination result is that the unacquired log exists, the client actively sends a log acquisition request to the server to acquire the unacquired log. The reason why the client needs to initiate the acquisition request actively, rather than the server determining the unacquired log actively in the first interaction and returning the unacquired log and the determination result together, is that in actual operation, when the client receives a message that there is an unacquired log, an administrator does not necessarily want to view the unacquired log immediately (for example, the client is busy at present and does not have time to view a new log). At this time, the server actively determines that the log is not acquired and returns the determined log to the client, which easily causes an excessive load on the server. In other words, when the administrator knows that there is a message of not obtaining the log but does not want to view the not-obtained log immediately, the return-together method is likely to cause unnecessary burden to the server.
In step S309, a log acquisition request is created.
Step S310, the client sends a log acquisition request to the server.
In step S311, the server reads the numbers of all locally stored logs.
If the step is executed in a log management system comprising a plurality of clients, the numbers of all logs stored in the server and corresponding to the administrator identification need to be read so as to judge whether the logs corresponding to the numbers are the logs which are not acquired.
In step S312, the server compares the maximum number of the client log with the numbers of all local logs to determine that no log is acquired.
In this embodiment, the maximum number of the client log used for comparison may be a number read from the log query request in the first interaction; if the maximum number read in the first interaction is deleted, the maximum number may also be read from the log obtaining request, and of course, the maximum number needs to be written into the log obtaining request when the log obtaining request is created. Specifically, the method may be performed in different manners according to actual situations by those skilled in the art, and is not limited herein.
In this step, the log whose number is greater than the maximum number of the client log may be determined as an unacquired log, and the log whose number is not greater than the maximum number of the client log may be determined as an acquired log. The mode of determining that the log is not acquired can be that the determined log is marked with the log which is not acquired; the remaining logs are marked as acquired. Of course, in order to facilitate the administrator to understand the meaning of the flag, the unread log may be marked as an unread log, and the rest of the logs may be marked as read logs.
For example, in step S305, when the numbers of all logs generated by the server are 1, 2, 3, 4, 5, and 6, the logs corresponding to the numbers 5 and 6 are logs with numbers greater than the maximum number of the log of the client, at this time, the logs corresponding to the numbers 5 and 6 are determined as unacquired logs, and the logs with the numbers 1, 2, 3, and 4 are determined as logs other than the unacquired logs.
In step S313, the server returns the determined unacquired log to the client.
If the step is executed in a log management system comprising a plurality of clients, the unacquired log is returned to the client corresponding to the administrator identifier.
In this embodiment, the server may return only the unacquired log to the client, or may return the unacquired log together with other logs. However, in practical applications, in order to avoid distinguishing a received new log from an already-acquired log when the client receives an unacquired log, the server usually returns all determined logs (i.e. an acquired log and an unacquired log, or a read log and an unread log). When the client receives all the logs returned by the server, all the logs which are originally stored are emptied, and all the received logs are stored in the storage space. Therefore, the client can be prevented from distinguishing the new acquisition log from the historical acquisition log. In addition, most steps are centralized to a server side, so that the execution steps of the method are convenient to manage.
In step S314, the client receives the determined unacquired log.
In this embodiment, when receiving an unacquired log, the client may directly pop up the acquired unacquired log; the uncaptured log may also be displayed in a functional bar (e.g., a functional bar of a WEB page) at the top of the display page in the form of a new log message, and only when the administrator clicks the new log message, the corresponding uncaptured log is popped up for the administrator to review.
Specifically, a specific auto-eject switch may be provided on the client. When the switch is turned on, as long as the unacquired log returned by the server is received, the acquired log is popped up immediately; when the switch is closed, the corresponding log information is popped up only when the administrator actively clicks the new log message.
According to the technical scheme, the maximum number of the log stored by the client is compared with the maximum number of the log generated by the server, so that whether the log which is not acquired and corresponds to the client exists or not is determined. When the logs which are not obtained exist, the client further obtains the determined logs which are not obtained from the server, so that an administrator can timely obtain the logs newly generated by the server and perform corresponding maintenance work according to the obtained logs.
The method has the advantages that in the stage of determining whether the logs which are not acquired exist, the number information of all the logs does not need to be acquired, and only one maximum number of each of the client and the server needs to be acquired, so that whether the logs which are not acquired and correspond to the client exist can be determined; even in the stage of determining that the log is not acquired, the log can be determined that the log is not acquired without acquiring the numbers of all logs of the client, so that the occupation of processing resources of the server is reduced, and the performance of the server is improved.
Referring to fig. 4, fig. 4 is an interaction diagram of another log management method according to an exemplary embodiment of the present application, in which a log generated by a server is configured with corresponding number information, and the method may include:
step S401, a log query request is created.
In this embodiment, the process of creating the log query request by the client includes the steps of detecting a local log and acquiring all local log numbers. After detecting the numbers of all logs, writing the numbers into the log query request as the log number information of the client.
Step S402, the client sends a log query request to the server.
In this embodiment, similar to step S302, the client may be an administrator terminal, and may also set a sending period for the process of sending the log query request, which may specifically refer to step S302 and is not described herein again.
In step S403, the server reads the numbers of all logs of the client included in the log query request.
In this embodiment, for the case that the server usually corresponds to multiple clients, reference may be made to the content of the previous embodiment, which is not described in detail in this embodiment.
Step S404, the server reads the numbers of all local logs.
Step S405, the server judges whether a log with a number different from all log numbers of the client exists locally or not so as to obtain whether a result that the log is not acquired exists or not.
In this embodiment, when the server determines that the local existence number is different from the logs of all the log numbers of the client, it determines that the log which is not acquired exists; otherwise, it is determined that there is no uncaptured log. In this embodiment, the result is returned to the client regardless of whether or not there is an unacquired log.
Along with the example in the previous embodiment, that is, assuming that the numbers of all logs acquired by the client from the server are 1, 2, 3 and 4, the numbers of all logs generated by the server are 1, 2, 3, 4, 5 and 6. Then, the server reads all the numbers of the logs from the log query request as 1, 2, 3, and 4, and reads all the numbers of the local logs as 1, 2, 3, 4, 5, and 6. It is to be noted that, in the server, the numbers 5 and 6 are different from the numbers of all logs of the client, and it is determined that there is an unacquired log corresponding to the client. Of course, if the numbers of the logs stored by the server are 1, 2, 3, and 4, the server does not have the numbers different from all the logs of the client, that is, it is determined that there is no unacquired log corresponding to the client.
In step S406, the server returns the determined result to the client.
In step S407, the client receives the returned determination result.
In step S408, the client determines whether the returned determination result is that there is an unacquired log.
In this embodiment, when it is determined that the returned result is that there is an unacquired log, a log acquisition request is further created to acquire an unacquired log existing at the server (i.e., step S409 is executed); and when the returned result is determined that the log which is not acquired does not exist, ending the interaction.
In addition, when the returned result is determined that the log which is not acquired exists, a corresponding warning mark can be lightened on a specific interface (such as a WEB interface) of the client so as to inform an administrator of the existence of the log which is not acquired; of course, when it is determined that there is no unrecognized log, another warning flag may be lit to inform the administrator that there is no unrecognized log.
In step S409, a log acquisition request is created.
In this embodiment, step S309 may be referred to in a process that the client creates the log obtaining request to actively request the server to obtain the unacquired log, which is not described herein again.
Step S410, the client sends a log obtaining request to the server.
In step S411, the server compares the numbers of all the logs of the client with the numbers of all the logs of the local server to determine that no log is acquired.
In this embodiment, since the numbers of all the logs of the client and the numbers of all the logs of the server have been read in the first interaction (i.e., in the process of determining whether there is an unacquired log), the numbers do not need to be read again. And directly comparing the numbers of all local logs read in the first interaction with the numbers of all logs of the client. And determining the logs with the numbers different from the numbers of all logs of the client in the server as the logs which are not acquired.
In the step S405, when the numbers of all logs generated by the server are 1, 2, 3, 4, 5, and 6, and the logs corresponding to the numbers 5 and 6 are the logs with the numbers different from all the log numbers of the client in the server, the logs corresponding to the numbers 5 and 6 are determined as the logs that have not been acquired.
Of course, when all the log numbers of the client read in the first interaction have been deleted, the operation manner in the step S312 when the maximum number is deleted may be referred to, which is not described herein again. It can be understood that, in the case that the numbers of all local logs read for the first time are deleted, the comparison is performed only once between the steps of performing the comparison. Specifically, whether to delete the read data after the first interaction is finished may be determined by one skilled in the art according to practical situations, and is not limited herein.
How to distinguish the unacquired log from other logs accordingly may refer to the execution manner in step S312, which is not described herein again.
Step S412, the server returns the determined unacquired log to the client.
In this step, the content of step S313 may be referred to for the specific content to be returned, which is not described herein again.
In step S413, the client receives the determined unacquired log.
According to the technical scheme, the numbers of all logs stored by the client are compared with the numbers of all logs generated by the server, so that whether the logs which are not acquired and correspond to the client exist is determined. When the logs which are not obtained exist, the client further obtains the determined logs which are not obtained from the server, so that an administrator can timely obtain the logs newly generated by the server and perform corresponding maintenance work according to the obtained logs.
The method has the advantages that no strict requirement is imposed on the method of configuring the numbers for the generated logs by the server, and the numbers between the logs are not repeated, so that the log management method can be suitable for more scenes.
Fig. 5 is a schematic block diagram illustrating a server-based electronic device according to an exemplary embodiment of the present application. Referring to fig. 5, at the hardware level, the electronic device includes a processor 502, an internal bus 504, a network interface 506, a memory 508 and a non-volatile memory 510, but may also include hardware required for other services. The processor 502 reads a corresponding computer program from the non-volatile memory 510 into the memory 508 and then runs, forming a log management apparatus on a logical level. Of course, besides the software implementation, the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Referring to fig. 6, in a software implementation, the log management apparatus may include:
a receiving unit 601, configured to receive a log query request sent by a client, where the log query request includes history number information of a log acquired by the client from the server;
a comparing unit 602, configured to compare the historical number information with number information of a locally generated log, so as to determine whether an unacquired log corresponding to the client exists;
a returning unit 603 that returns a determination result to the client when it is determined that the unacquired log exists.
Optionally, the log query request further includes an administrator identifier corresponding to the client;
the comparing unit 602 is further configured to obtain history number information corresponding to the administrator identifier, and compare the obtained history number information with number information of a locally generated log.
Optionally, the number information includes numbers obtained by sequencing according to a time sequence generated by the log; the historical number information is the maximum number of the log acquired by the client from the server;
the comparing unit 602 is further configured to determine whether the history number information is smaller than a maximum number of a locally generated log; if so, determining that an unobtainable log corresponding to the client exists; otherwise, determining that there is no uncaptured log corresponding to the client.
Optionally, the method further includes:
a determining unit 604 configured to, when receiving a log acquisition request for the unacquired log sent by the client, take a local log having a number greater than the history number information as an unacquired log;
the returning unit 603 is further configured to return, to the client, other logs that are different from the unacquired log in the unacquired log and/or the local log.
Optionally, the historical number information is numbers of all logs acquired by the client from the server;
the comparing unit 602 is further configured to determine whether the number of the locally generated log is different from the number of the history number information; if so, determining that an unobtainable log corresponding to the client exists; otherwise, determining that there is no uncaptured log corresponding to the client.
Optionally, the method further includes:
the determining unit 604 is further configured to, when receiving a log obtaining request sent by the client for the unacquired log, take a local log having a number different from the history number information as an unacquired log;
the returning unit 603 is further configured to return, to the client, other logs that are different from the unacquired log in the unacquired log and/or the local log.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
Fig. 7 is a schematic block diagram illustrating a client-based electronic device in an exemplary embodiment of the present application. Referring to fig. 7, at the hardware level, the electronic device includes a processor 702, an internal bus 704, a network interface 706, a memory 708, and a non-volatile storage 710, but may also include hardware required for other services. The processor 702 reads a corresponding computer program from the non-volatile memory 710 into the memory 708 and then runs the computer program, thereby forming a log management device on a logical level. Of course, besides the software implementation, the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Referring to fig. 8, in a software implementation, the log management apparatus may include:
a creating unit 801 that creates a log query request, where the log query request includes history number information of a log obtained by the client from the server;
a sending unit 802, configured to send a log query request to the server, so that the server compares the historical number information with number information of a log locally generated by the server, to determine whether an unacquired log corresponding to the client exists;
the receiving unit 803 receives a determination result returned by the server, where the determination result is generated when the server determines that the unacquired log exists.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and 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 modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
In an exemplary embodiment, there is also provided a non-transitory computer readable storage medium, e.g. a memory, comprising instructions executable by a processor of a log management device to implement a method as in any of the above embodiments, such as the method may comprise: receiving a log query request sent by a client, wherein the log query request comprises history number information of a log acquired by the client from a server; comparing the historical number information with number information of a locally generated log to judge whether an unacquired log corresponding to the client exists or not; and when the log which is not acquired is judged to exist, returning a judgment result to the client.
The non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc., which is not limited in this application.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (10)

1. The log management method is characterized by being applied to a server side, wherein logs generated by the server side are configured with corresponding number information; the method comprises the following steps:
receiving a log query request sent by a client, wherein the log query request comprises history number information of a log acquired by the client from a server;
comparing the historical number information with number information of a locally generated log to judge whether an unacquired log corresponding to the client exists or not;
and when the fact that the logs which correspond to the client and are not obtained exist is judged, returning a judgment result to the client.
2. The method according to claim 1, wherein the log query request further includes an administrator identifier corresponding to the client;
the comparing the historical number information with the number information of the locally generated log comprises: and acquiring historical number information corresponding to the administrator identification, and comparing the acquired historical number information with the number information of the locally generated log.
3. The method of claim 1, wherein the number information includes numbers sorted in chronological order of log generation; the historical number information is the maximum number of the log acquired by the client from the server; the comparing the historical number information with the number information of the locally generated log comprises:
judging whether the historical number information is smaller than the maximum number of the locally generated log or not;
if so, determining that an unobtainable log corresponding to the client exists; otherwise, determining that there is no uncaptured log corresponding to the client.
4. The method of claim 3, further comprising:
when a log acquisition request aiming at the unacquired log sent by the client is received, taking the local log with the number larger than the historical number information as the unacquired log;
and returning other logs which are different from the non-acquired logs in the non-acquired logs and/or the local logs to the client.
5. The method according to claim 1, wherein the history number information is the numbers of all logs acquired by the client from the server; comparing the historical number information with the number information of the locally generated log, including:
judging whether the number of the locally generated log is different from the number of the historical number information or not;
if so, determining that an unobtainable log corresponding to the client exists; otherwise, determining that there is no uncaptured log corresponding to the client.
6. The method of claim 5, further comprising:
when a log acquisition request for the unacquired log sent by the client is received, taking a local log with a number different from the historical number information as an unacquired log;
and returning other logs which are different from the non-acquired logs in the non-acquired logs and/or the local logs to the client.
7. A log management method is characterized by being applied to a client; the log is generated by a server side, and the log generated by the server side is configured with corresponding number information; the method comprises the following steps:
creating a log query request, wherein the log query request comprises history number information of a log acquired by the client from the server;
sending a log query request to the server, so that the server compares the historical number information with the number information of the log locally generated by the server, and judges whether an unacquired log corresponding to the client exists or not;
and receiving a judgment result returned by the server, wherein the judgment result is generated when the server judges that the unacquired log exists.
8. The log management device is applied to a server side, and logs generated by the server side are configured with corresponding number information; the device comprises:
the system comprises a receiving unit, a log query unit and a log processing unit, wherein the log query unit receives a log query request sent by a client, and the log query request comprises history number information of a log acquired by the client from a server;
the comparison unit is used for comparing the historical number information with the number information of the locally generated log so as to judge whether the log which is not acquired and corresponds to the client exists or not;
and the returning unit returns a judgment result to the client when judging that the unacquired log exists.
9. An electronic device, comprising:
a processor;
a memory for storing processor executable tasks;
wherein the processor implements the method of any one of claims 1-7 by executing the executable instructions.
10. A computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method according to any one of claims 1-7.
CN201911205624.6A 2019-11-29 2019-11-29 Log management method and device, electronic equipment and storage medium Active CN110888790B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911205624.6A CN110888790B (en) 2019-11-29 2019-11-29 Log management method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911205624.6A CN110888790B (en) 2019-11-29 2019-11-29 Log management method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN110888790A true CN110888790A (en) 2020-03-17
CN110888790B CN110888790B (en) 2024-02-27

Family

ID=69749621

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911205624.6A Active CN110888790B (en) 2019-11-29 2019-11-29 Log management method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN110888790B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111459756A (en) * 2020-03-30 2020-07-28 深圳市金蝶天燕云计算股份有限公司 Log processing method and related equipment
CN113268549A (en) * 2021-04-08 2021-08-17 北京中云宽频通讯技术有限公司 CMDB-based network private line management method, system, computer equipment and storage medium

Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030074244A1 (en) * 2001-04-11 2003-04-17 Braxton Charles R. Distributed energy technology assurance
AU2001295260B2 (en) * 2000-10-09 2004-09-23 A & Mt Projects Pty Limited Wireless transactions
CN1681248A (en) * 2004-04-06 2005-10-12 三星电子株式会社 Method and system for transmitting data for data synchronization between server and client
US20080301200A1 (en) * 2007-06-01 2008-12-04 Microsoft Corporation Log file amnesia detection
CN101510893A (en) * 2008-12-25 2009-08-19 北京大学 Method, device and transmission system for sending, transferring and receiving message document
CN101826993A (en) * 2010-02-04 2010-09-08 蓝盾信息安全技术股份有限公司 Method, system and device for monitoring security event
CN102567140A (en) * 2010-12-03 2012-07-11 微软公司 Bile system backup using change journal
US20150350126A1 (en) * 2014-05-30 2015-12-03 Huawei Technologies Co., Ltd. Method and device for using log information
CN105141448A (en) * 2015-07-28 2015-12-09 杭州华为数字技术有限公司 Method and device for collecting log
CN106100913A (en) * 2016-08-25 2016-11-09 北京票之家科技有限公司 Error message alignment system and method
CN106462449A (en) * 2014-06-26 2017-02-22 亚马逊科技公司 Multi-database log with multi-item transaction support
CN106447826A (en) * 2016-09-29 2017-02-22 北京宙心科技有限公司 Unmanned aerial vehicle fault diagnosis method and unmanned aerial vehicle fault diagnosis system
CN106713041A (en) * 2016-12-29 2017-05-24 杭州迪普科技股份有限公司 Session log transmitting method and device
CN106789353A (en) * 2017-02-06 2017-05-31 百度在线网络技术（北京）有限公司 The method and system of orientation problem between client and service end
CN106817387A (en) * 2015-11-28 2017-06-09 成都华为技术有限公司 A kind of method of data synchronization, device and system
WO2017097108A1 (en) * 2015-12-11 2017-06-15 广州市动景计算机科技有限公司 Log information processing method, apparatus, and system
CN106973050A (en) * 2017-03-23 2017-07-21 山东中创软件商用中间件股份有限公司 A kind of method and device of inter-network lock information sharing
CN107148617A (en) * 2014-09-19 2017-09-08 亚马逊科技公司 Automatically configuring for storage group is coordinated in daily record
CN107644017A (en) * 2016-07-20 2018-01-30 平安科技（深圳）有限公司 The querying method and device of journal file
CN108416040A (en) * 2018-03-14 2018-08-17 上海达梦数据库有限公司 A kind of database recovering method, device, terminal device and storage medium
CN109241185A (en) * 2018-08-27 2019-01-18 武汉达梦数据库有限公司 A kind of method and data synchronization unit that data are synchronous
CN109241014A (en) * 2018-07-04 2019-01-18 阿里巴巴集团控股有限公司 Data processing method, device and server
CN110096419A (en) * 2019-04-22 2019-08-06 厦门网宿有限公司 Acquisition methods, interface log management server and the service server of interface log
CN110232290A (en) * 2018-03-05 2019-09-13 中兴通讯股份有限公司 Log desensitization method, server and storage medium
CN110232048A (en) * 2019-06-12 2019-09-13 腾讯科技(成都)有限公司 Acquisition methods, device and the storage medium of journal file
CN110505039A (en) * 2019-09-26 2019-11-26 北京达佳互联信息技术有限公司 A kind of data transfer control method, device, equipment and medium
SG11201910212WA (en) * 2017-06-06 2019-11-28 Ab Initio Technology Llc Integrated system for rule editing, simulation, version control, and business process management

Patent Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2001295260B2 (en) * 2000-10-09 2004-09-23 A & Mt Projects Pty Limited Wireless transactions
US20030074244A1 (en) * 2001-04-11 2003-04-17 Braxton Charles R. Distributed energy technology assurance
CN1681248A (en) * 2004-04-06 2005-10-12 三星电子株式会社 Method and system for transmitting data for data synchronization between server and client
US20080301200A1 (en) * 2007-06-01 2008-12-04 Microsoft Corporation Log file amnesia detection
CN101510893A (en) * 2008-12-25 2009-08-19 北京大学 Method, device and transmission system for sending, transferring and receiving message document
CN101826993A (en) * 2010-02-04 2010-09-08 蓝盾信息安全技术股份有限公司 Method, system and device for monitoring security event
CN102567140A (en) * 2010-12-03 2012-07-11 微软公司 Bile system backup using change journal
US20150350126A1 (en) * 2014-05-30 2015-12-03 Huawei Technologies Co., Ltd. Method and device for using log information
CN106462449A (en) * 2014-06-26 2017-02-22 亚马逊科技公司 Multi-database log with multi-item transaction support
CN107148617A (en) * 2014-09-19 2017-09-08 亚马逊科技公司 Automatically configuring for storage group is coordinated in daily record
CN105141448A (en) * 2015-07-28 2015-12-09 杭州华为数字技术有限公司 Method and device for collecting log
CN106817387A (en) * 2015-11-28 2017-06-09 成都华为技术有限公司 A kind of method of data synchronization, device and system
WO2017097108A1 (en) * 2015-12-11 2017-06-15 广州市动景计算机科技有限公司 Log information processing method, apparatus, and system
CN107644017A (en) * 2016-07-20 2018-01-30 平安科技（深圳）有限公司 The querying method and device of journal file
CN106100913A (en) * 2016-08-25 2016-11-09 北京票之家科技有限公司 Error message alignment system and method
CN106447826A (en) * 2016-09-29 2017-02-22 北京宙心科技有限公司 Unmanned aerial vehicle fault diagnosis method and unmanned aerial vehicle fault diagnosis system
CN106713041A (en) * 2016-12-29 2017-05-24 杭州迪普科技股份有限公司 Session log transmitting method and device
CN106789353A (en) * 2017-02-06 2017-05-31 百度在线网络技术（北京）有限公司 The method and system of orientation problem between client and service end
CN106973050A (en) * 2017-03-23 2017-07-21 山东中创软件商用中间件股份有限公司 A kind of method and device of inter-network lock information sharing
SG11201910212WA (en) * 2017-06-06 2019-11-28 Ab Initio Technology Llc Integrated system for rule editing, simulation, version control, and business process management
CN110232290A (en) * 2018-03-05 2019-09-13 中兴通讯股份有限公司 Log desensitization method, server and storage medium
CN108416040A (en) * 2018-03-14 2018-08-17 上海达梦数据库有限公司 A kind of database recovering method, device, terminal device and storage medium
CN109241014A (en) * 2018-07-04 2019-01-18 阿里巴巴集团控股有限公司 Data processing method, device and server
CN109241185A (en) * 2018-08-27 2019-01-18 武汉达梦数据库有限公司 A kind of method and data synchronization unit that data are synchronous
CN110096419A (en) * 2019-04-22 2019-08-06 厦门网宿有限公司 Acquisition methods, interface log management server and the service server of interface log
CN110232048A (en) * 2019-06-12 2019-09-13 腾讯科技(成都)有限公司 Acquisition methods, device and the storage medium of journal file
CN110505039A (en) * 2019-09-26 2019-11-26 北京达佳互联信息技术有限公司 A kind of data transfer control method, device, equipment and medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
文勇军;黄浩;樊志良;唐立军;: "分布式日志系统REST安全接口设计", 网络安全技术与应用, no. 04 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111459756A (en) * 2020-03-30 2020-07-28 深圳市金蝶天燕云计算股份有限公司 Log processing method and related equipment
CN113268549A (en) * 2021-04-08 2021-08-17 北京中云宽频通讯技术有限公司 CMDB-based network private line management method, system, computer equipment and storage medium

Also Published As

Publication number Publication date
CN110888790B (en) 2024-02-27

Similar Documents

Publication Publication Date Title
CN111555963B (en) Message pushing method and device, electronic equipment and storage medium
US8001150B2 (en) Device management method using nodes having additional attribute and device management client thereof
CN110232010A (en) A kind of alarm method, alarm server and monitoring server
CN109361525B (en) Method, device, control terminal and medium for restarting distributed deployment of multiple services
CN106844055B (en) Task execution method and device
CN110502318A (en) Event-handling method, event processing server, storage medium and device
CN110471749B (en) Task processing method, device, computer readable storage medium and computer equipment
CN107577578B (en) Method, device and equipment for counting delay of NFS operation word and storage medium
CN110704872B (en) Data query method and device, electronic equipment and computer readable storage medium
CN110888790A (en) Log management method and device, electronic equipment and storage medium
CN111538563A (en) Event analysis method and device for Kubernetes
CN103401764A (en) Method and device for sending mails
CN113468025A (en) Data warning method, system, device and storage medium
CN112511580A (en) Message pushing method, device, storage medium and equipment
CN110543512A (en) Information synchronization method, device and system
CN108366098B (en) Data interaction method and device for network nodes
CN114996085A (en) Prometheus-based real-time service monitoring method and system
CN114363334A (en) Network configuration method, device and equipment for cloud system and cloud desktop virtual machine
CN111309743A (en) Report pushing method and device
CN108241616B (en) Message pushing method and device
US10394771B2 (en) Use of search templates to identify slow information server search patterns
CN111026606A (en) Alarm method and device based on hystrix fuse monitoring and computer equipment
CN113268401B (en) Log information output method and device and computer readable storage medium
CN115329005A (en) Multi-cluster cooperation method, system, device and computer readable storage medium
CN111343101B (en) Server current limiting method, device, electronic equipment and readable 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
GR01 Patent grant
GR01 Patent grant