CN110888790B - Log management method and device, electronic equipment and storage medium - Google Patents
Log management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN110888790B CN110888790B CN201911205624.6A CN201911205624A CN110888790B CN 110888790 B CN110888790 B CN 110888790B CN 201911205624 A CN201911205624 A CN 201911205624A CN 110888790 B CN110888790 B CN 110888790B
- Authority
- CN
- China
- Prior art keywords
- log
- client
- number information
- server
- acquired
- 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.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 37
- 238000000034 method Methods 0.000 claims abstract description 57
- 230000003993 interaction Effects 0.000 description 13
- 230000008569 process Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 5
- 238000012552 review Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000013500 data storage Methods 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
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 provides a log management method and device, electronic equipment and a storage medium; the method is applied to a server, and a log generated by the server is configured with corresponding numbering 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 the server; comparing the history number information with the number information of the locally generated log to determine whether an unoccupied log corresponding to the client exists; and when judging that the unobtained log corresponding to the client exists, returning a judging result to the client. According to the method and the system, the number information of the log stored by the client is compared with the number information of the log generated by the server, whether the log which is not acquired exists is judged and whether the log which is not acquired is judged, so that an administrator can acquire the log which is not acquired in time, and the system is maintained according to the log information.
Description
Technical Field
The present invention 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
During system operation, journaling is a very critical file. The log not only can help the user of the system to fully know the operating environment of the system, but also can enable the user to know the events occurring before and after the system fails, so that the user can process the system according to the condition of the system. In addition, in case of emergency such as attack on the system, emergency logs different from other logs are generated to inform the user of the message of the attack and the specific condition 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 learn whether a log that has not been acquired exists, so that the administrator can timely acquire the log that has not been acquired, and maintain a system according to the 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 and 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 the server;
comparing the history number information with the number information of the locally generated log to determine whether an unoccupied log corresponding to the client exists;
and when the existence of the unobtainable log is judged, returning a judging 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, and the log generated by the server 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 side so that the server side compares the history number information with the number information of the log locally generated by the server side to judge whether an unoccupied log corresponding to the client side exists or not;
and receiving a judging result returned by the server, wherein the judging result is generated by the server when judging that the unoccupied log exists.
According to a third aspect of the present application, a log management device is provided, and is applied to a server, where a log generated by the server is configured with corresponding number information; the device comprises:
the receiving unit is used for 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;
the comparison unit compares the history number information with the number information of the locally generated log to judge whether the unoccupied log corresponding to the client exists or not;
and a return unit for returning a determination result to the client when it is determined that the non-acquired log exists.
According to a fourth aspect of the present application, a log management device is provided, which is applied to a client; the log is generated by a server, and the log generated by the server is configured with corresponding number information; the method comprises the following steps:
the creating unit creates a log query request, wherein the log query request comprises history number information of a log acquired by the client from the server;
the sending unit is used for sending a log query request to the server side so that the server side can compare the history number information with the number information of the log locally generated by the server side to judge whether the log which corresponds to the client side and is not acquired exists;
And the receiving unit is used for receiving a judging result returned by the server, wherein the judging result is generated by the server when the server judges that the unobtained 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 is configured to implement the method according to 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 perform the steps of the method according to any of the embodiments described above.
In the technical scheme of the application, the server configures the number information for the generated log, and the client records the number information of the acquired log after acquiring the log from the server. Based on the above mechanism for numbering logs, when there is a need to acquire a new log generated by the server, a request containing the number information of the log stored by the client may be sent to the server by the client, so that the server may determine whether there is an unoccupied log corresponding to the client 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 determined result to the client, and timely notify an administrator that there is an unoccupied log.
Further, when the non-acquired logs corresponding to the client exist, the non-acquired logs are determined in a mode of comparing numbers, so that the acquired logs and the non-acquired logs are distinguished, an administrator can manage the acquired logs and the non-acquired logs respectively, and the situations that the working efficiency is low, the logs are missed to read and the like caused by incapability of distinguishing the acquired logs and the non-acquired logs are avoided.
Drawings
Fig. 1 is a flowchart of a server-based log management method according to an exemplary embodiment of the present application.
FIG. 2 is a flow chart illustrating a client-based log management method according to an exemplary embodiment of the present application.
Fig. 3 is an interaction diagram of a log management method according to an exemplary embodiment of the present application.
FIG. 4 is an interaction diagram of 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 of a server-based log management device 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 device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present 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 or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
The log plays an extremely important role in the running process of the system, and can help an administrator to know the running condition of the system so as to maintain the system according to the information of log reaction in real time. In addition, in the case that the system is under external attack, the log system can also generate an emergency log immediately to inform an administrator of the information of the system under attack, so that the administrator can process the condition of the system under attack as soon as possible.
In order to facilitate an administrator to review the log in time, the related art places the log message in a function column on the top of the WEB page, so that the administrator can open the log display page for review by clicking the log message when he wants to review the log.
However, in the related art, the client cannot timely learn whether a new log which is not acquired exists at the server, and cannot distinguish a history non-acquired log from a history acquired log in the acquired log after acquiring the new log.
In order to solve the technical problems, the application provides a log management method. Referring to fig. 1, fig. 1 is a flowchart illustrating a server-based log management method 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, a log query request sent by a client is received, wherein the log query request comprises history number information of a log acquired from the server by the client.
In the present embodiment, in most cases, one server for log management may correspond to a plurality of clients. Thus, to distinguish between multiple clients, each client is configured with a respective administrator identification. In this case, the server may configure each client with a block of storage space to store logs corresponding to the respective clients, respectively.
In this log management system, the log query request sent by the client includes an administrator identifier corresponding to the client. When a server receives a log query request, firstly reading an administrator identifier in the received log query request to determine a client for sending the log query request; and obtaining the serial number information of the locally generated log from the storage space configured to the client in the server, and comparing the serial number information with the history serial number information corresponding to the administrator identifier obtained from the log query request to determine whether the unoccupied log corresponding to the client exists in the server.
In this step, the client may detect the number of the log that has been obtained locally from the server, and write the detected number into a certain field of the log query request when the log query request is created, so that the server reads the field to obtain the history number information when receiving the log query request. Of course, how the client writes the history number information to the log query request may be performed by those skilled in the art in different manners according to actual situations, which is not specifically limited herein.
In addition, in order to be able to timely obtain whether there is a message that does not acquire the log, the client may periodically send a log query request to the server. Of course, the timing operation manner may be determined by those skilled in the art according to actual circumstances, and is not limited herein. The timing time can be set by an administrator according to actual requirements and conditions of the system.
Step S104, comparing the history number information with the number information of the locally generated log to judge whether the unoccupied log corresponding to the client exists.
In the embodiment of the present application, the configuration number information of the log generated by the server may have multiple configuration methods, and for different configuration methods, the history number information of the log obtained from the server included in the log query request may also have multiple situations.
In an embodiment, the server sorts the generated logs according to the generated time sequence to further obtain the serial numbers of the logs. In this case, the history number information included in the log query request may be the maximum number of the log acquired from the server by the client. At this time, it may be determined whether there is a log that has not been acquired by the client by comparing the maximum number with the maximum number of the log generated by the server. When the maximum number is smaller than the maximum number of the log generated by the server, determining that the unoccupied log corresponding to the client exists; otherwise, it is determined that there is no unobtained log corresponding to the client.
The advantage of numbering the logs by the generated chronological order is that the client only has to write one log number when generating the log query request. And secondly, when the server compares the historical number information with the number information of the local log, only one local number information is required to be read for comparison with the historical number information, and the number information of all logs is not required to be acquired, so that 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 the log obtained by the client from the server. At this time, the serial numbers of the logs locally generated by the server side can be compared with all serial numbers of the logs of the client side, and whether the serial numbers of the logs locally generated by the server side are different from all serial numbers of the logs in the client side or not is judged; if yes, determining that the unoccupied log corresponding to the client exists; otherwise, it is determined that there is no unobtained log corresponding to the client.
The method for writing all numbers of the logs acquired by the client from the server into the log query request has the advantages that the method for numbering the generated logs by the server has no strict requirement, and only the logs are required to be numbered repeatedly, so that the method for judging whether the logs which are not acquired exist can be suitable for more scenes.
And step S106, when judging that the unobtained log corresponding to the client exists, returning a judging result 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 unobtained log corresponding to the client; the determination result may be returned as long as the determination result is obtained (whether the determination result is that there is an unoccupied log or that there is no unoccupied log).
When it is determined that there is an unoccupied log corresponding to the client, the server may return only a result that there is an unoccupied log; the server may further distinguish the logs corresponding to the client generated in the server based on the result, so as to return the determined non-acquired logs to the client. If the server side only returns the result of the existence of the unoccupied log, the log corresponding to the client side generated in the server side can be distinguished when the unoccupied request sent by the user is received, so that the unoccupied log is determined, and the unoccupied log is returned to the client side. When the determined non-acquired log is returned to the client, only the non-acquired log may be returned, or the determined non-acquired log and other logs corresponding to the client may be returned together.
In this step, when it is determined that there is an unobtained log corresponding to the client, it may be further determined that there is an unobtained log corresponding to the client in the server.
In an embodiment, the server side adopts the method of numbering the logs through 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 logs obtained from the server side by the client side. At this time, if the mode of "determining that there is an unoccupied log, only a result of the unoccupied log is returned" is adopted, when a log acquisition request for the unoccupied 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 unoccupied log, and returns the unoccupied log to the client.
Similarly, if a mode of returning the result of the non-acquired log and the non-acquired log together is adopted, the non-acquired log is directly determined according to the method without waiting for the client to send a log acquisition request, and the non-acquired log 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 contents to be returned may be determined by those skilled in the art according to actual circumstances, and are not particularly limited herein.
In another embodiment, the manner in which the server side numbers the log is not limited, that is, the history number information included in the log query request in step S104 is all the numbers of the log obtained by the client side from the server side. At this time, if the mode of "when it is determined that there is an unoccupied log, only the result of the unoccupied log is returned" is adopted, then when a log acquisition request for the unoccupied 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 as the unoccupied log to the client.
Similarly, if a mode of returning the result of the existence of the unoccupied log and the unoccupied log is adopted, the operation mode is the same as that of the previous embodiment except for the mode of determining the unoccupied log, and will not be described herein.
According to the technical scheme, the server configures the number information for the generated log, and the client records the number information of the acquired log after acquiring the log from the server. Based on the above mechanism for numbering logs, when there is a need to acquire a new log generated by the server, a request containing the number information of the log stored by the client may be sent to the server by the client, so that the server may determine whether there is an unoccupied log corresponding to the client 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 determined result to the client, and timely notify an administrator that there is an unoccupied log.
Further, when it is determined that the server side has the non-acquired log corresponding to the client side, the number of the logs stored by the server side and the client side respectively is compared to determine the non-acquired log corresponding to the client side and the non-acquired log is returned to the client side, so that an administrator can check the non-acquired log, and the system is maintained according to information in the non-acquired log. By the method, the manager can distinguish the history unoccupied log from the history acquired log, so that the problems of missing the log, repeated watching of the same log and the like are avoided.
Referring to fig. 2, fig. 2 is a flowchart illustrating a client-based log management method 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, and the log generated by the server 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 history number information of a log acquired from the server by the client.
In this embodiment, the content included in the log query request may refer to the description in step S102, which is not described herein.
Step S204, a log query request is sent to the server side, so that the server side compares the history number information with the number information of the log locally generated by the server side to judge whether the unoccupied log corresponding to the client side exists.
In this embodiment, the specific content of the history number information and the specific content of the number information of the log for comparison generated locally may refer to the description in step S104, and will not be described herein.
It is noted that the action of sending the log query request can be actively sent by the administrator through the client, or a certain sending period can be set for the client, the log query request is periodically sent to the server, and the newly generated log of the server is timely obtained.
Step S206, receiving a determination result returned by the server, where the determination result is generated by the server when it is determined that the unobtained log exists.
In this embodiment, when the server determines that the non-acquired log does not exist, the determination result may also be returned, and at this time, the client receives the determination result returned by the server that the non-acquired log does not exist. Of course, the specific content returned by the server may refer to the description in step S106, which is not described herein.
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 up, or a warning tone is sounded to alert an administrator that there is an unobtainable log. When the returned result includes the determined non-acquired log, the non-acquired log may also be directly popped up. The specific manner of operation may be set by those skilled in the art according to the actual circumstances 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. Further, when a returned result is received or the log is not acquired, corresponding prompt information is sent out at the client side, so that an administrator can review the log in time, and the system is maintained better.
For easy 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, where a server orders logs according to a time sequence of log generation to obtain numbers, and the method may include:
in 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 a process of creating a log query request. After the maximum number is detected, the maximum number is written into a log query request as a client maximum log number.
In 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 to the server by the administrator terminal, so that the server queries the local log, and determines whether there is an unobtained log. The administrator can set the 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 of not obtaining the log, or the environment where the system is currently located is unstable (i.e. the system condition needs to be monitored at all times), the sending period may be set to be shorter, for example, 2 seconds, 5 seconds, etc.; if the administrator does not get a message about whether or not there is an unobtainable log, or if the environment in which the system is currently located is stable, the transmission period may be set longer, for example, 10 seconds, 15 seconds, or the like.
In step S303, the server reads the client maximum number included in the log query request.
In this step, since the server side generally corresponds to a plurality of client sides, this step may further include a process of reading the identity of the administrator terminal. Of course, the corresponding administrator identification needs 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, the subsequent steps are performed for the corresponding client of the administrator identity or the corresponding log of the administrator identity.
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 locally stored log corresponding to the administrator identifier.
In step S305, the server compares the maximum number of the client with the maximum number of the local log to obtain whether there is a result of not obtaining the log.
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 the log with the number greater than the maximum number of the log stored in the client exists in the locally generated log of the server, and at this time, it is determined that there is an unobtained log; otherwise, it is determined that there is no unobtained log. In this embodiment, the results are returned to the client regardless of whether there is an unobtained log.
For example, assume that the client obtains 1, 2, 3, and 4 numbers of all logs from the server, and the server generates 1, 2, 3, 4, 5, and 6 numbers of all logs. Then, the maximum log number read from the log query request by the server is 4, and the maximum number of the read local log is 6. At this time, when the two are compared, if 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), it is determined that the unobtained log exists. If the maximum number of the local log is also 4 in this example, it is determined that there is no unobtainable log.
In step S306, the server returns the result of the determination to the client.
If the step is executed in the log management system comprising a plurality of clients, the server side returns a judging result to the client side corresponding to the administrator identifier.
In step S307, the client receives the returned determination result.
In the present embodiment, an automatic acquisition switch may be provided. The automatic acquisition switch has the function that when an administrator wants to acquire the logs which are not acquired immediately under the condition that the logs are not acquired, the client side initiatively initiates a log acquisition request to the server side when receiving a return result of the logs which are not acquired as long as the automatic acquisition switch is turned on, and the administrator does not need to manually initiate the request. On the contrary, when the automatic acquisition switch is turned off, even if the client receives a return result of the non-acquired log, the log acquisition request cannot be actively initiated, and an administrator is required to manually initiate the log acquisition request.
In step S308, the client determines whether the returned determination result is that there is an unobtained log.
In this embodiment, when it is determined that the returned result is that there is an unoccupied log, a log obtaining request is further created to obtain an unoccupied log existing at the server (i.e., step S309 is performed); and ending the interaction when the returned result is that the unobtained log does not exist.
In addition, when the returned result is that the unoccupied log 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 that the unoccupied log exists; of course, upon determining that there is no unoccupied log, another warning flag may be illuminated to inform the administrator that there is no unoccupied log.
In this embodiment, when it is determined that the received determination result is that there is an unoccupied log, the client actively sends a log acquisition request to the server to acquire the unoccupied log. The requirement that the client actively initiate the acquisition request instead of the server actively determining the non-acquired log in the first interaction and returning the non-acquired log together with the determination result is that in actual operation, when the client receives a message that there is a non-acquired log, the administrator does not necessarily want to view the non-acquired log immediately (for example, it is currently busy, and has no time to look at a new log). At this time, the server actively determines the unoccupied log and returns the determined unoccupied log to the client, which easily causes an excessive burden on the server. In other words, when the administrator knows that there is a message of the non-acquired log but does not want to view the non-acquired log immediately, the return together is likely to cause unnecessary burden on the server side.
Step S309, a log acquisition request is created.
In step S310, the client sends a log acquisition request to the server.
In step S311, the server reads the numbers of all the locally stored logs.
If this step is performed in a log management system including a plurality of clients, it is necessary to read numbers of all logs corresponding to the administrator id stored in the server, so as to determine whether the logs corresponding to the numbers are unobtained logs.
In step S312, the server compares the maximum number of the client log with the numbers of all local logs to determine that the log is not acquired.
In this embodiment, the maximum number of the client log used for comparison may be the 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 corresponding maximum number needs to be written into the log obtaining request when the log obtaining request is created. In particular, the skilled person can use different operation modes according to the actual situation, and the present invention is not limited in particular.
In this step, the log with the number greater than the maximum number of the client log is determined as the non-acquired log, and the log with the number not greater than the maximum number of the client log may be determined as the acquired log. The method for determining the unoccupied log may be to make an unoccupied mark for the determined log; the remaining logs are marked as acquired. Of course, to facilitate the administrator's understanding of the meaning of the marks, the unread logs may be marked as unread logs, and the remaining logs may be marked as read logs.
In the example of the adapting step S305, when all the logs generated by the server are numbered 1, 2, 3, 4, 5, and 6, the logs corresponding to the numbers 5 and 6 are the logs with the number greater than the maximum number of the client logs, at this time, the logs corresponding to the numbers 5 and 6 are determined to be the non-acquired logs, and the logs with the numbers 1, 2, 3, and 4 are determined to be other logs than the non-acquired logs.
In step S313, the server returns the determined unobtained log to the client.
If the step is executed in the log management system comprising a plurality of clients, the corresponding client is identified to the administrator and the unobtained log is returned.
In this embodiment, the server may only return the unoccupied log to the client, or may return the unoccupied log and other logs together. However, in practical applications, in order to avoid that when the client receives the log that is not acquired, the client distinguishes the received new log from the log that has already been acquired, the server side generally returns the determined logs (i.e. the acquired log and the non-acquired log, or the read log and the non-read log) to the client. When the client receives all 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 newly acquired log from the historical acquired log. In addition, most steps are concentrated to the server side, so that the execution steps of the method are convenient to manage.
In step S314, the client receives the determined unobtained log.
In this embodiment, when receiving the unoccupied log, the client may directly pop up the unoccupied log obtained; the unobtained log may also be displayed in the form of a new log message in a function column (e.g., a function column of a WEB page) at the top of the display page, and the corresponding unobtained log may be popped up for review by the administrator only when the administrator clicks on the new log message.
Specifically, a specific auto-eject switch may be provided on the client. When the switch is turned on, the acquired log is popped up immediately as long as the unoccupied log returned by the server is received; when the switch is closed, the corresponding log information is popped up only when the administrator actively clicks on 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 as to determine whether the unoccupied log corresponding to the client exists. When the non-acquired logs exist, the client further acquires the determined non-acquired logs from the server, so that an administrator can acquire the newly generated logs from the server in time and perform corresponding maintenance work according to the acquired logs.
The method has the advantages that in the stage of determining whether the unoccupied logs exist, no serial number information of all logs is required to be acquired, and whether the unoccupied logs corresponding to the client exist can be determined only by acquiring the maximum serial numbers of the client and the server; even in the stage of determining the non-acquired logs, the number of all logs of the client is not required to be acquired, the non-acquired logs can be determined, the occupation of processing resources of the server is reduced, and the performance of the server is further 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, where a log generated by a server is configured with corresponding number information, the method may include:
in 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 the local log and obtaining all local log numbers. After the numbers of all logs are detected, the numbers are written into a log inquiry request to be used as log number information of the client.
In 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, or may set a transmission period for the process of transmitting the log query request, and specific reference may be made to step S302, which is not described herein.
In step S403, the server reads the numbers of all the logs of the client included in the log query request.
In this embodiment, for the case that the server generally corresponds to a plurality of clients, reference may be made to the content of the previous embodiment, which is not described in detail in this embodiment.
In step S404, the server reads the numbers of all local logs.
In step S405, the server determines whether there are logs with numbers different from all log numbers of the client locally, so as to obtain a result of whether there are non-obtained logs.
In this embodiment, when the server determines that there are logs with numbers different from all log numbers of the client locally, it determines that there are unobtained logs; otherwise, it is determined that there is no unobtained log. In this embodiment, the results are returned to the client regardless of whether there is a determination of an unobtained log.
Along with the example in the above embodiment, that is, assume that the numbers of all logs acquired from the server by the client are 1, 2, 3, 4, and the numbers of all logs generated by the server are 1, 2, 3, 4, 5, and 6. Then, the numbers of all logs read from the log query request by the server are 1, 2, 3 and 4, and all numbers of the read local logs are 1, 2, 3, 4, 5 and 6. It can be seen that the numbers 5 and 6 in the server are different from the numbers of all logs of the client, and it is determined that there is an unobtained log corresponding to the client. Of course, if the numbers of the logs saved by the server are 1, 2, 3, and 4, the server does not have numbers different from all the logs of the client, that is, it is determined that there is no unobtained log corresponding to the client.
In step S406, the server returns the result of the determination 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 unobtained log.
In this embodiment, when it is determined that the returned result is that there is an unoccupied log, a log obtaining request is further created to obtain an unoccupied log existing at the server (i.e., step S409 is performed); and ending the interaction when the returned result is that the unobtained log does not exist.
In addition, when the returned result is that the unoccupied log 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 that the unoccupied log exists; of course, upon determining that there is no unoccupied log, another warning flag may also be illuminated to inform the administrator that there is no unoccupied log.
In step S409, a log acquisition request is created.
In this embodiment, the process of creating the log obtaining request by the client to actively request to obtain the unobtainable log from the server may refer to step S309, which is not described herein.
In step S410, the client sends a log acquisition request to the server.
In step S411, the server compares the numbers of all logs of the client with the numbers of all logs locally to determine that no log is obtained.
In this embodiment, since the numbers of all logs of the client and the numbers of all logs of the server local have been read in the first interaction (i.e. in the process of judging whether there is an unobtainable log), it is not necessary to 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 numbers different from the numbers of all the logs of the client in the server as non-acquired logs.
In the example of the adapting step S405, when all the logs generated by the server are numbered 1, 2, 3, 4, 5, and 6, the logs corresponding to the numbers 5 and 6 are the logs with numbers different from the numbers of all the logs of the client in the server, and the logs corresponding to the numbers 5 and 6 are determined as the non-acquired logs.
Of course, in the case that all log numbers of the clients read in the first interaction have been deleted, reference may be made to the operation manner in the case that the maximum number is deleted in step S312, which is not described herein. It will be appreciated that in the case where the numbers of all logs locally read for the first time are deleted, only one time need be read before the step of performing the comparison. Specifically, whether to delete the read data after the first interaction is completed may be determined by those skilled in the art according to the actual situation, and is not limited herein.
Accordingly, how to distinguish the unobtained log from other logs may refer to the execution mode in step S312, and will not be described herein.
In step S412, the server returns the determined unobtained log to the client.
In this step, the specific content of the return may refer to the content of step S313, and will not be described herein.
In step S413, the client receives the determined non-acquired 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 as to determine whether the unoccupied logs corresponding to the client exist. When the non-acquired logs exist, the client further acquires the determined non-acquired logs from the server, so that an administrator can acquire the newly generated logs from the server in time and perform corresponding maintenance work according to the acquired logs.
The method has the advantages that the method for configuring the numbers to the generated logs by the server has no strict requirement, and only the numbers among 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 nonvolatile memory 510, and may include hardware required by other services. The processor 502 reads the corresponding computer program from the nonvolatile memory 510 into the memory 508 and then runs, forming a log management device on a logical level. Of course, other implementations, such as logic devices or combinations of hardware and software, are not excluded from the present application, that is, the execution subject of the following processing flows is not limited to each logic unit, but may be hardware or logic devices.
Referring to fig. 6, in a software implementation, the log management device 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 obtained by the client from the server;
a comparison unit 602, configured to compare the history number information with the number information of the locally generated log, so as to determine whether there is an unobtained log corresponding to the client;
and a return unit 603 for returning a determination result to the client when it is determined that the non-acquired 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 sorting according to the time sequence of log generation; the history number information is the maximum number of the log obtained by the client from the server;
the comparison 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 unobtained log corresponding to the client exists; otherwise, it is determined that there is no unobtained log corresponding to the client.
Optionally, the method further comprises:
a determining unit 604, configured to, when receiving a log acquisition request for the unoccupied log sent by the client, take a local log with a number greater than the history number information as an unoccupied log;
the returning unit 603 is further configured to return the unoccupied log and/or other logs different from the unoccupied log in the local log to the client.
Optionally, the history number information is the numbers of all logs obtained by the client from the server;
the comparison unit 602 is further configured to determine whether a number different from the history number information exists in the numbers of the locally generated logs; if so, determining that an unobtained log corresponding to the client exists; otherwise, it is determined that there is no unobtained log corresponding to the client.
Optionally, the method further comprises:
the determining unit 604 is further configured to, when receiving a log acquisition request for the unoccupied log sent by the client, take a local log with a number different from the history number information as an unoccupied log;
the returning unit 603 is further configured to return the unoccupied log and/or other logs different from the unoccupied log in the local log to the client.
The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.
Fig. 7 is a schematic block diagram illustrating a client-based electronic device according to an exemplary embodiment of the present application. Referring to fig. 7, at a hardware level, the electronic device includes a processor 702, an internal bus 704, a network interface 706, a memory 708, and a nonvolatile memory 710, although other hardware may be included as needed for other services. The processor 702 reads the corresponding computer program from the nonvolatile memory 710 into the memory 708 and then runs, forming a log management device at a logic level. Of course, other implementations, such as logic devices or combinations of hardware and software, are not excluded from the present application, that is, the execution subject of the following processing flows is not limited to each logic unit, but may be hardware or logic devices.
Referring to fig. 8, in a software implementation, the log management device may include:
a creating unit 801, configured to create 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 history number information with the number information of the log locally generated by the server, so as to determine whether there is an unobtained log corresponding to the client;
and a receiving unit 803 for receiving a determination result returned by the server, where the determination result is generated by the server when it is determined that the non-acquired log exists.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, e.g., a memory, comprising instructions executable by a processor of a log management device to implement a method as described in any of the above embodiments, e.g., 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 the server; comparing the history number information with the number information of the locally generated log to determine whether an unoccupied log corresponding to the client exists; and when the existence of the unobtainable log is judged, returning a judging result to the client.
Wherein the non-transitory computer readable storage medium may be a ROM, random-access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc., which is not limited in this application.
The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.
Claims (9)
1. The log management method is characterized by being applied to a server, wherein 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 the server;
comparing the history number information with the number information of the locally generated log to determine whether an unoccupied log corresponding to the client exists;
when judging that the unobtained log corresponding to the client exists, returning a judging result to the client;
the log inquiry request also comprises an administrator identifier corresponding to the client;
the comparing the history number information with the number information of the locally generated log comprises: and acquiring the history number information corresponding to the administrator identifier, and comparing the acquired history number information with the number information of the locally generated log.
2. The method of claim 1, wherein the numbering information comprises numbers ordered in chronological order of log generation; the history number information is the maximum number of the log obtained by the client from the server; the comparing the history number information with the number information of the locally generated log comprises:
Judging whether the history number information is smaller than the maximum number of a locally generated log;
if so, determining that an unobtained log corresponding to the client exists; otherwise, it is determined that there is no unobtained log corresponding to the client.
3. The method as recited in claim 2, further comprising:
when a log acquisition request for the unoccupied log sent by the client is received, taking the local log with the number larger than the history number information as the unoccupied log;
and returning the non-acquired log and/or other logs different from the non-acquired log in the local log to the client.
4. The method according to claim 1, wherein the history number information is a number of all logs obtained by the client from the server; comparing the history 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 history number information;
if so, determining that an unobtained log corresponding to the client exists; otherwise, it is determined that there is no unobtained log corresponding to the client.
5. The method as recited in claim 4, further comprising:
when a log acquisition request for the unoccupied log sent by the client is received, taking the local log with the number different from the history number information as the unoccupied log;
and returning other logs which are different from the non-acquired log in the non-acquired log and/or the local log to the client.
6. The log management method is characterized by being applied to a client; the log is generated by a server, and the log generated by the server 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 side so that the server side compares the history number information with the number information of the log locally generated by the server side to judge whether an unoccupied log corresponding to the client side exists or not;
receiving a judging result returned by the server, wherein the judging result is generated by the server when judging that the unoccupied log exists;
The log inquiry request also comprises an administrator identifier corresponding to the client;
the sending a log query request to the server so that the server compares the history number information with the number information of the log locally generated by the server, including: the server side obtains the history number information corresponding to the administrator identification, and compares the obtained history number information with the number information of the locally generated log.
7. The log management device is characterized by being applied to a server, wherein a log generated by the server is configured with corresponding number information; the device comprises:
the receiving unit is used for 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;
the comparison unit compares the history number information with the number information of the locally generated log to judge whether the unoccupied log corresponding to the client exists or not;
a return unit that returns a determination result to the client when it is determined that the non-acquired log exists;
the log inquiry request also comprises an administrator identifier corresponding to the client;
The comparison unit is further used for obtaining the history number information corresponding to the administrator identification, and comparing the obtained history number information with the number information of the locally generated log.
8. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement the method of any of claims 1-6 by executing the executable instructions.
9. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any of claims 1-6.
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 CN110888790A (en) | 2020-03-17 |
| CN110888790B true 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) |
Families Citing this family (2)
| 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 (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
| 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 |
| CN106447826A (en) * | 2016-09-29 | 2017-02-22 | 北京宙心科技有限公司 | Unmanned aerial vehicle fault diagnosis method and unmanned aerial vehicle fault diagnosis system |
| CN106462449A (en) * | 2014-06-26 | 2017-02-22 | 亚马逊科技公司 | Multi-database log with multi-item transaction support |
| 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 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030074244A1 (en) * | 2001-04-11 | 2003-04-17 | Braxton Charles R. | Distributed energy technology assurance |
| US8001075B2 (en) * | 2007-06-01 | 2011-08-16 | Microsoft Corporation | Log file amnesia detection |
| CN103997454B (en) * | 2014-05-30 | 2017-11-21 | 华为技术有限公司 | The application method and equipment of a kind of log information |
| US10782960B2 (en) * | 2017-06-06 | 2020-09-22 | Ab Initio Technology Llc | User interface that integrates plural client portals in plural user interface portions through sharing of one or more log records |
-
2019
- 2019-11-29 CN CN201911205624.6A patent/CN110888790B/en active Active
Patent Citations (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
| 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 |
| 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)
| Title |
|---|
| 分布式日志系统REST安全接口设计;文勇军;黄浩;樊志良;唐立军;;网络安全技术与应用(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110888790A (en) | 2020-03-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| 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 | |
| CN110888790B (en) | Log management method and device, electronic equipment and storage medium | |
| CN109361525B (en) | Method, device, control terminal and medium for restarting distributed deployment of multiple services | |
| CN110704872B (en) | Data query method and device, electronic equipment and computer readable storage medium | |
| CN110543512A (en) | Information synchronization method, device and system | |
| CN103490978A (en) | Terminal, server and message monitoring method | |
| CN113468025A (en) | Data warning method, system, device and storage medium | |
| CN115002148A (en) | Internet of things cloud side communication method and system | |
| CN110717130B (en) | Dotting method, dotting device, dotting terminal and storage medium | |
| CN109978114A (en) | Data processing method, device, server and storage medium | |
| CN106452905A (en) | Message processing method and device | |
| CN114466321B (en) | Message sending method and device, electronic equipment and storage medium | |
| CN108880994B (en) | Method and device for retransmitting mails | |
| CN114092211A (en) | Processing method of accounting data, electronic device and readable storage medium | |
| CN114221988A (en) | Content distribution network hotspot analysis method and system | |
| CN112612848A (en) | Method, device and system for real-time data synchronization, electronic equipment and storage medium | |
| CN110674757A (en) | Deployment control method, system and computer readable storage medium | |
| CN110418020B (en) | List state information processing method and device, electronic terminal and storage medium | |
| JP6921908B2 (en) | Automatic call device and automatic call method | |
| CN114629942B (en) | Fraud early warning task generation method, device, equipment and medium | |
| CN114416109B (en) | Program deployment method and device, computer device, and storage medium | |
| CN114500454B (en) | Method and device for detecting geographic position change of electronic equipment | |
| CN107222522B (en) | Mobile storage method | |
| CN117097692A (en) | Session storage system |
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 |