CN117118824B - Log data collection method and device - Google Patents
Log data collection method and device Download PDFInfo
- Publication number
- CN117118824B CN117118824B CN202311364099.9A CN202311364099A CN117118824B CN 117118824 B CN117118824 B CN 117118824B CN 202311364099 A CN202311364099 A CN 202311364099A CN 117118824 B CN117118824 B CN 117118824B
- Authority
- CN
- China
- Prior art keywords
- data
- log data
- log
- indicating
- event
- 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
- 238000000034 method Methods 0.000 title claims abstract description 103
- 238000013480 data collection Methods 0.000 title claims description 14
- 230000008569 process Effects 0.000 claims abstract description 67
- 238000012163 sequencing technique Methods 0.000 claims abstract description 22
- 238000004891 communication Methods 0.000 claims description 65
- 238000004590 computer program Methods 0.000 claims description 7
- 230000005540 biological transmission Effects 0.000 claims description 6
- 230000006399 behavior Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004888 barrier function Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a log data collecting method and device, wherein a client device generates log data aiming at an occurring operation event, the log data comprises content indicating data for indicating the content of the operation event and sequencing prompt data for indicating the sequencing of the log data, the sequencing prompt data comprises unique identification data which is randomly generated and is used for indicating process identification data of a process where the operation event is located and event sequence identification data which is used for indicating the sequence of the event where the operation event is located in the process, then the log data is stored locally, and when a preset sending condition is met, a data packet formed by a plurality of log data is sent to a server device, so that the server device sequences the log data according to the sequencing prompt data of the log data in the data packet, the sequenced log data is sequentially stored in a message queue, and the uniqueness and the sequence of the log data in the log data process are ensured through the sequencing prompt data.
Description
Technical Field
The present disclosure relates to the field of network technologies, and in particular, to a method and an apparatus for collecting log data.
Background
With the continuous development of network technology, each network system platform has its own users, and because of the characteristics of each system platform, it is able to adapt to specific technical requirements, so in a large system, different platforms may be required to implement functions of various characteristics, and in order to implement corresponding functions, it may be required to collect and analyze logs generated in the network.
At present, the terminal equipment is used for carrying out big data analysis or user behavior analysis of a single user on each operation and passive triggering action of the user, and the sequence of each log needs to be ensured, so that how to ensure the sequence of log data collection in the process of log data collection becomes the technical problem to be solved currently.
Disclosure of Invention
An objective of the embodiments of the present application is to provide a method and an apparatus for collecting log data, so as to solve the above technical problems.
In one aspect, there is provided a log data collection applied to a client device, the method comprising:
the client device generates log data for the generated operation event; the log data includes content indication data for indicating the content of the operation event, and ordering prompt data for indicating the ordering of the log data; the sequencing prompt data comprises unique identification data which is randomly generated, process identification data which is used for indicating a process where the operation event is located, and event sequence identification data which is used for indicating the sequence of the event where the operation event is located in the process;
and storing the log data locally, and when a preset sending condition is met, sending a data packet formed by a plurality of log data to a server side device so that the server side device can sort the log data according to the sorting prompt data of the log data in the data packet, and sequentially storing the sorted log data into a message queue so that a consumer of the server side device can sequentially take out the log data from the message queue for consumption.
In one embodiment, the sequencing batch may further include time data for indicating when the operation event occurred.
In one embodiment, the storing the log data locally includes:
and storing the log data into a temporary list of the memory of the client equipment, and storing the log data into a target file of the hard disk of the client equipment.
In one embodiment, the storing the log data in the target file of the hard disk of the client device includes:
encrypting the log data;
and storing the encrypted log data into a target file of a hard disk of the client device.
In one embodiment, after the data packet formed by the plurality of pieces of log data is sent to the server device, the method includes:
and deleting the log data forming the data packet in the memory of the client equipment when the data packet formed by a plurality of pieces of log data is successfully received, and deleting the data corresponding to the log data in the hard disk of the client equipment.
In one embodiment, the sending the data packet formed by the plurality of pieces of log data to the server device includes:
acquiring a current cached target communication mode;
and transmitting a data packet formed by a plurality of pieces of log data to a server device based on the target communication mode.
In one embodiment, before the obtaining the currently cached target communication mode, the method includes:
periodically updating at least one of a CDN domain name, an IP address, communication port information and communication protocol information which are configured locally at present;
determining a current to-be-selected communication mode according to the currently configured CDN domain name, the IP address, the communication port information and the communication protocol information;
determining an effective communication mode from the to-be-communicated communication modes based on a Keepalive technology;
and selecting a target communication mode from the effective communication modes for caching.
On the other hand, a log data collection method is provided and applied to a server device, and the method comprises the following steps:
the server side equipment receives a data packet sent by the client side equipment; the data packet comprises a plurality of pieces of log data, and each piece of log data comprises content indication data for indicating the content of the operation event and sequencing prompt data for indicating sequencing the log data; the sequencing prompt data comprises unique identification data which is randomly generated, process identification data which is used for indicating a process where the operation event is located, and event sequence identification data which is used for indicating the sequence of the event where the operation event is located in the process;
and sequencing the log data according to the sequencing prompt data of the log data in the data packet, and sequentially storing the sequenced log data into a message queue so that a consumer of the server equipment can sequentially take out the log data from the message queue for consumption.
In one embodiment, the sorting the log data according to the sorting prompt data of the log data in the data packet, and sequentially storing the sorted log data into a message queue includes:
determining a device identifier of the client device that sent the data packet;
sorting the log data according to the sorting prompt data of the log data in the data packet;
and associating the sorted log data with the equipment identifier and storing the log data into a message queue.
In another aspect, there is provided an apparatus comprising a processor and a memory, the memory having stored therein a computer program, the processor executing the computer program to implement any of the methods described above.
According to the log data collection method and device, the client device generates log data aiming at the generated operation event, the log data comprises content indication data for indicating the content of the operation event and sequencing prompt data for indicating the sequencing of the log data, wherein the sequencing prompt data comprises unique identification data which are randomly generated and used for indicating the process identification data of the process where the operation event is located and event sequence identification data which are used for indicating the sequence of the event where the operation event is located in the process, then the log data are stored locally, and when the preset sending condition is met, a data packet composed of a plurality of log data is sent to the server device, so that the server device sequences the log data according to the sequencing prompt data of the log data in the data packet, and sequentially stores the sequenced log data into a message queue, so that a consumer of the server device sequentially takes out the log data from the message queue to consume, and the uniqueness and the sequence of the log data in the log data process are ensured through the sequencing prompt data.
Drawings
Fig. 1 is a flowchart of a log data collection method applied to a client device side according to an embodiment of the present application;
fig. 2 is a flow chart of a log data collection method applied to a server device side according to a second embodiment of the present application;
fig. 3 is a schematic structural diagram of an apparatus according to a third embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
Example 1
At present, a terminal device needs to analyze big data by each operation and passive triggering action of a user or analyze user behaviors of a single user, and the sequence of each log needs to be ensured, but the prior art cannot ensure the sequence of log data.
Referring to fig. 1, the log data collection method in the embodiment of the present application may include the following steps:
s11: the client device generates log data for the generated operation event; the log data includes content indication data for indicating the content of the operation event, and ordering prompt data for indicating the ordering of the log data; the ordering prompt data comprises randomly generated unique identification data, process identification data used for indicating a process where the operation event is located, and event sequence identification data used for indicating the sequence of the event where the operation event is located in the process.
S12: and storing the log data locally, and when a preset sending condition is met, sending a data packet formed by a plurality of pieces of log data to the server-side equipment so that the server-side equipment can sort the log data according to sorting prompt data of the log data in the data packet, and sequentially storing the sorted log data into a message queue so that a consumer of the server-side equipment can sequentially take out the log data from the message queue for consumption.
The steps described above are described in detail below.
The operation event in the embodiment of the application refers to an operation event occurring on the client device, and the operation event may be actively initiated by a user or passively triggered by the user.
At present, equipment platforms of various systems exist on the market, for example, IOS, android, windows and the like are available, programming languages are realized in various ways, the implementation complexity of different languages is different, the development cost is extremely high, the integrity of data collected by the server equipment is difficult to ensure because different reliability schemes are needed for different languages,
in the embodiment of the application, the client device may send the log data to the server device by calling the golang interface, and specifically, may provide an interface of C through an export function of cgo to implement cross-platform call.
Each piece of log data includes content indication data for indicating the content of the operation event, and sorting prompt data for indicating sorting of the log data; the ordering prompt data comprises randomly generated unique identification data, process identification data used for indicating a process where the operation event is located, and event sequence identification data used for indicating the sequence of the event where the operation event is located in the process.
Illustratively, the sequencing hint data may also include time data for indicating when the operational event occurred. So that subsequent analysis may be further analyzed based on the time of occurrence of each piece of log data.
The structure of each piece of log data can be as follows:
type Message struct
{
Time time.Time `json:",omitempty"`
RandId string `json:",omitempty"`
ProcessSessionId string `json:",omitempty"`
ProcessEventId int `json:",omitempty"`
ArgList []string `json:",omitempty"`
}
the Time represents Time data, randId represents randomly generated unique identification data, processSessionId represents process identification data of a process where an operation event is located, processEventId represents event sequence identification data of an event sequence where the operation event is located in the process, and ArgList represents content indication data and represents specific operation content.
In the scheme, the unique identification data, the process identification data and the event sequence identification data are added for the log data, which is equivalent to adding the unique index identification and the sequence index identification for the log data, so that the uniqueness and the sequence of each log data can be ensured.
It will be appreciated that whenever an operational event occurs on a client device, corresponding process identification data may be generated from the process to which the operational event belongs.
In a first optional embodiment, the process identity identifier corresponding to each process of the client device may be preset in advance for each process, and it should be noted that the process identities of each process are different from each other, so that it is ensured that the process identities corresponding to different processes are different, and uniqueness of log data is further ensured. When an operation event occurs, the process identity of the process where the operation event is located can be obtained and used as the process identification data in the log data corresponding to the operation event, and then the log data can be analyzed to be generated by calling which process.
In the second alternative embodiment, considering that the processes on the client device are more, the corresponding process identity identifiers are preset for different processes respectively, so that in the present embodiment, the process identifier of the process where the operation event is located can also be generated by a random algorithm. Specifically, when a first thread is called, a first process identifier is generated for the first thread, process identifier data in log data generated by calling the first thread is the first process identifier, when a new second thread is called at a certain moment, a corresponding second process identifier is generated for the second thread, because the first process identifier and the second process identifier are both generated through a random algorithm, the second process identifier can be compared with the first process identifier, if the comparison result is inconsistent, a subsequent step can be performed, and if the comparison result is consistent, a new second process identifier needs to be generated for the second thread until the new second process identifier is inconsistent with the first process identifier, so that the process identifiers corresponding to different processes can be ensured to be different, and the uniqueness of the log data is further ensured.
Similarly, each time an operation event occurs on the client device, corresponding event sequence identification data may also be generated according to an event sequence in which the operation event is located in a process to which the operation event belongs, for example, for each operation event in each process, the corresponding sequence identification data may be determined according to a sequence in which the operation event is logically processed, and when the client device responds to the operation event of a certain thread, that is, when the client device logically processes the operation event, a logic processing entry may be blocked by a memory lock for the thread, so that other operation events in the thread may not be responded to temporarily, and sequence identification data in the thread may be generated according to the sequence in which each operation event is logically processed. In this embodiment of the present application, the event sequence identification data of the operation events in the same process is incremental data, for example, the first operation event processed by logic may have a corresponding sequence identification data of 1, and the second operation event processed by logic may have a corresponding sequence identification data of 2.
Next, a procedure for locally storing log data by the client device will be described.
In the embodiment of the application, the log data may be stored in a temporary list in the memory of the client device and/or in a target file of the hard disk of the client device.
Preferably, the log data may be stored in a temporary list in the memory of the client device, and the log data may be stored in a target file in the hard disk of the client device. The data are stored in the memory and the hard disk respectively, so that the risk of data loss can be better avoided.
When the log data is stored in the target file of the hard disk of the client device, the log data may be encrypted, and the encrypted log data may be stored in the target file of the hard disk of the client device.
In this embodiment of the present application, the log data may be encrypted by using an aectr encryption method, and of course, the log data may also be encrypted by using other encryption methods.
The target file may be a preset file under a fixed directory, and is used for storing log data generated by the client device.
It should be noted that, the log data stored in the hard disk of the client device may not be ordered according to the order, and may be ordered according to the order prompt data when the log data is read from the hard disk of the client device, and when the process is started for the first time, the log data stored in the hard disk of the client device may be sequentially read and stored into the temporary list in the memory of the client device.
In step S12, the client device may periodically send log data to the server device, and may send the log data to the server device when a preset log data sending time point arrives. For example, the client device may perform a transmission task at intervals of a preset time, where the transmission task is specifically: and packaging the log data in the temporary list of the memory of the client device into a data packet and sending the data packet to the server device. The server device may return a receipt hint message to the client device to hint to the client device whether the data packet was successfully received.
In the embodiment of the application, when the client device determines that a data packet formed by a plurality of pieces of log data is successfully received, the log data forming the data packet in the memory of the client device is deleted, and the data corresponding to the log data in the hard disk of the client device is deleted.
The following describes a procedure in which a client device transmits a data packet to a server device.
In this embodiment of the present application, sending a data packet composed of a plurality of pieces of log data to a server device includes:
acquiring a current cached target communication mode;
and transmitting a data packet formed by a plurality of pieces of log data to the server equipment based on the target communication mode.
It should be noted that, the target communication mode may be an optimal communication mode of the previous calculation period buffer.
Before the current cached target communication mode is acquired, the method comprises the following steps:
step one: and periodically updating at least one of the CDN domain name, the IP address, the communication port information and the communication protocol information which are configured locally.
Step two: determining a current to-be-selected communication mode according to the currently configured CDN domain name, the IP address, the communication port information and the communication protocol information;
step three: determining an effective communication mode from to-be-selected communication modes based on a Keepalive technology;
step four: and selecting a target communication mode from the effective communication modes for caching.
It should be noted that, the client device may periodically determine the target communication manner to cache, so that the data packet may be directly sent through the target communication manner when the data packet needs to be sent next time.
Specifically, the client device may update at least one of the CDN domain name, the IP address, the communication port information, and the communication protocol information that are configured at present in the local area periodically, determine, when a target communication manner needs to be determined, a current communication manner to be selected according to the CDN domain name, the IP address, the communication port information, and the communication protocol information that are configured at present, and the client device may detect, through a keep alive heartbeat packet, the communication manner to be selected as an effective communication manner that can be ping-enabled, and then select, as the target communication manner, an effective communication manner with a shortest transmission time to be cached.
The updating of the currently configured CDN domain name may be a timed domain name rotation of the CDN domain name, so that when a large amount of log data is generated on a certain client device, the log data is sent to the client device by different domain names, and thus the data amount of the log data sent by a certain domain name is not large, which causes detection that the firewall cannot be bypassed. The same is true for IP address updates. The updating of the communication port information may be a random selection of the communication port, or a timing rotation of the communication port. Updating the communication protocol information may be a timing rotation of a communication protocol including, but not limited to, tcp protocol, https protocol, and the like.
That is, the client device may detect whether the destination address is a ping address through the keep alive heartbeat packet, where the destination address is an address determined by the IP addresses, CDN domain names, communication port information, and communication protocol information of all the server devices in load balancing, and each time, the fast address is cached by the keep alive device to ensure that a fast tunnel, that is, a destination communication mode, is used when the client device sends the packet next time. In the embodiment of the application, the ip+multi-CDN domain name rotation (time-shifting IP) +multi-port (443, 80, tcp random port …) +multi-protocol (tcp, https …) is adopted to ensure that firewall detection can be bypassed, global data can be successfully transmitted, and an available transmission mode can be ensured for each data transmission.
In this embodiment of the present application, when the client device sends a data packet to the server device, the client device may send its own device identifier to the client device, so that the client device stores the sorted log data and the device identifier in a message queue in association with each other.
Example two
An embodiment of the present application provides a log data collection method, which is applied to a server device, where the server device in the embodiment of the present application may be a server, and referring to fig. 2, the method may include:
s21: the method comprises the steps that a server device receives a data packet sent by a client device; the data packet comprises a plurality of pieces of log data, and each piece of log data comprises content indication data for indicating the content of an operation event and sequencing prompt data for indicating sequencing the log data; the ordering prompt data comprises randomly generated unique identification data, process identification data used for indicating a process where the operation event is located, and event sequence identification data used for indicating the sequence of the event where the operation event is located in the process.
S22: and ordering the log data according to ordering prompt data of the log data in the data packet, and sequentially storing the ordered log data into a message queue for a consumer of the server device to sequentially take out the log data from the message queue for consumption.
In step S22, it may be determined that the device identifier of the client device that sends the data packet, and the log data are ordered according to the ordering prompt data of the log data in the data packet; and associating the sequenced log data with the equipment identifier and storing the log data into a message queue.
The device identifier in the embodiment of the application refers to a unique identity identifier of the client device. Generally, the server device receives data packets sent by various server devices in the network, where the data packets are all generated and sent according to one of the foregoing embodiments, and will not be described herein. Therefore, in order for the server device to acquire which client device the log data is sent by, the client device may send its own device id one to the server device when sending the log data to the server device.
The message queue in the embodiment of the present application may be an Apache Kafka message queue.
After receiving the data packet, the server device may sort the log data according to RandId, processSessionId and processEventId of each log data in the data, obtain a sequential user behavior list, and then write the user behavior list into the Apache Kafka message queue.
When a scene of a certain user behavior needs to be analyzed or rendered, log data which are sequentially stored can be directly taken out of an Apache Kafka message queue and stored in a disk corresponding to each application scene. The single user and the data overall analysis can be stored in different SQL instances, so that the business is ensured not to be affected mutually.
In the embodiment of the application, the problem of the efficiency of the first-layer cache writing of the data is solved through Apache Kafka, the data is completely eaten first, then the data is consumed by the SQL Instance of the next layer, the consumer reads out the log data required by the consumer and stores the log data into a disk, so that the situation that the data loss exists due to the fact that the data quantity is too large can be avoided, the data is beyond expectations only by enlarging the hard disk of the Apache Kafka machine, and the data which can be consumed by the Apache Kafka message is provided in a barrier mode, so that the sequence is guaranteed.
It should be understood that, although the steps in the above-described flowcharts are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described above may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, and the order of execution of the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with at least a part of the sub-steps or stages of other steps or other steps.
It should be noted that, for simplicity of description, the content described in the above embodiment is not repeated in this embodiment.
Example III
Based on the same inventive concept, the embodiment of the present application provides an apparatus, where the apparatus includes a processor 301 and a memory 302, where the memory 302 stores a computer program, and the processor 301 and the memory 302 implement communications through a communication bus, and the processor 301 executes the computer program to implement each step of the method in the first embodiment, where the apparatus is a client device. Of course, the processor 301 may also execute the computer program to implement the steps of the method in the second embodiment, where the device is a server device.
It will be appreciated that the configuration shown in fig. 3 is merely illustrative, and that the terminal device may also include more or fewer components than shown in fig. 3, or have a different configuration than shown in fig. 3.
The processor 301 may be an integrated circuit chip with signal processing capabilities. The processor 301 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; but may also be a Digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. Which may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Memory 302 may include, but is not limited to, random Access Memory (RAM), read Only Memory (ROM), programmable Read Only Memory (PROM), erasable read only memory (EPROM), electrically erasable read only memory (EEPROM), and the like.
The present embodiment also provides a computer readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash memory, a usb disk, an SD card, an MMC card, etc., in which one or more programs for implementing the above steps are stored, and the one or more programs may be executed by the one or more processors 301 to implement the steps of the method in the first embodiment, which is not described herein again.
It should be noted that, the illustrations provided in the present embodiment merely illustrate the basic concept of the present invention by way of illustration, and only the components related to the present invention are shown in the drawings and are not drawn according to the number, shape and size of the components in actual implementation, and the form, number and proportion of the components in actual implementation may be arbitrarily changed, and the layout of the components may be more complex. The structures, proportions, sizes, etc. shown in the drawings attached hereto are for illustration purposes only and are not intended to limit the scope of the invention, which is defined by the claims, but rather by the claims. Also, the terms such as "upper," "lower," "left," "right," "middle," and "a" and the like recited in the present specification are merely for descriptive purposes and are not intended to limit the scope of the invention, but are intended to provide relative positional changes or modifications without materially altering the technical context in which the invention may be practiced.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (6)
1. A method of log data collection, for application to a client device, the method comprising:
the client device generates log data for the generated operation event; the log data includes content indication data for indicating the content of the operation event, and ordering prompt data for indicating the ordering of the log data; the sequencing prompt data comprises unique identification data which is randomly generated, process identification data which is used for indicating a process where the operation event is located, and event sequence identification data which is used for indicating the sequence of the event where the operation event is located in the process;
storing the log data locally, acquiring a current cached target communication mode when a preset sending condition is met, sending a data packet composed of a plurality of pieces of log data to a server device based on the target communication mode, so that the server device can sort the log data according to the sorting prompt data of the log data in the data packet, and sequentially storing the sorted log data into a message queue for a consumer of the server device to sequentially take out the log data from the message queue for consumption;
before the current cached target communication mode is obtained, the method comprises the following steps:
periodically updating at least one of a CDN domain name, an IP address, communication port information and communication protocol information which are configured locally at present;
determining a current to-be-selected communication mode according to the currently configured CDN domain name, the IP address, the communication port information and the communication protocol information;
detecting whether a target address can be subjected to ping communication or not through a keep alive heartbeat packet, and taking the communication mode to be subjected to the communication mode capable of being subjected to the ping communication as an effective communication mode; the target address is an address determined by the IP addresses, CDN domain names, communication port information and communication protocol information of all the server side equipment in the load balancing;
and selecting the effective communication mode with the shortest transmission time as a target communication mode to be cached.
2. The log data collection method of claim 1 wherein the sequencing batch is further comprised of time data indicating when the operational event occurred.
3. The log data collection method of claim 1, wherein the storing the log data locally comprises:
and storing the log data into a temporary list of the memory of the client equipment, and storing the log data into a target file of the hard disk of the client equipment.
4. The method for collecting log data according to claim 3, wherein storing the log data in a target file of a hard disk of the client device comprises:
encrypting the log data;
and storing the encrypted log data into a target file of a hard disk of the client device.
5. The log data collecting method as set forth in claim 3, wherein after said transmitting the data packet composed of a plurality of said log data to the server device, the method comprises:
and deleting the log data forming the data packet in the memory of the client equipment when the data packet formed by a plurality of pieces of log data is successfully received, and deleting the data corresponding to the log data in the hard disk of the client equipment.
6. An apparatus comprising a processor and a memory, the memory having a computer program stored therein, the processor executing the computer program to implement the method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311364099.9A CN117118824B (en) | 2023-10-20 | 2023-10-20 | Log data collection method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311364099.9A CN117118824B (en) | 2023-10-20 | 2023-10-20 | Log data collection method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117118824A CN117118824A (en) | 2023-11-24 |
| CN117118824B true CN117118824B (en) | 2024-02-27 |
Family
ID=88796877
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311364099.9A Active CN117118824B (en) | 2023-10-20 | 2023-10-20 | Log data collection method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117118824B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103036961A (en) * | 2012-12-07 | 2013-04-10 | 蓝盾信息安全技术股份有限公司 | Distributed collection and storage method of journal |
| CN103270499A (en) * | 2011-12-21 | 2013-08-28 | 华为技术有限公司 | Log storage method and system |
| CN105376077A (en) * | 2014-08-06 | 2016-03-02 | 中国移动通信集团黑龙江有限公司 | Network behavior information processing method, log transmitting method, network behavior information processing device and system |
| CN108351827A (en) * | 2015-10-07 | 2018-07-31 | 索利通系统株式会社 | Log information generates equipment and storage medium and log information extracting device and storage medium |
| CN109558305A (en) * | 2017-09-27 | 2019-04-02 | 北京国双科技有限公司 | Daily record data sort method and device |
| CN110249314A (en) * | 2016-12-21 | 2019-09-17 | 斯瑞特斯塔克股份有限公司 | The system and method monitored for OS Events based on cloud and data access |
| CN114036360A (en) * | 2021-10-15 | 2022-02-11 | 网宿科技股份有限公司 | Web crawler intercepting method and device, electronic equipment and readable storage medium |
| CN114138604A (en) * | 2021-12-01 | 2022-03-04 | 浪潮云信息技术股份公司 | Transaction log processing method and system for distributed database |
| CN115914409A (en) * | 2022-11-14 | 2023-04-04 | 中盈优创资讯科技有限公司 | Method and device for realizing efficient transmission and storage of WAF (wireless LAN access point) safety protection log |
| CN116595012A (en) * | 2023-07-17 | 2023-08-15 | 华中科技大学 | Time sequence database log storage method and system based on nonvolatile memory |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2953298B1 (en) * | 2013-01-30 | 2018-03-21 | Nippon Telegraph and Telephone Corporation | Log analysis device, information processing method and program |
-
2023
- 2023-10-20 CN CN202311364099.9A patent/CN117118824B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103270499A (en) * | 2011-12-21 | 2013-08-28 | 华为技术有限公司 | Log storage method and system |
| CN103036961A (en) * | 2012-12-07 | 2013-04-10 | 蓝盾信息安全技术股份有限公司 | Distributed collection and storage method of journal |
| CN105376077A (en) * | 2014-08-06 | 2016-03-02 | 中国移动通信集团黑龙江有限公司 | Network behavior information processing method, log transmitting method, network behavior information processing device and system |
| CN108351827A (en) * | 2015-10-07 | 2018-07-31 | 索利通系统株式会社 | Log information generates equipment and storage medium and log information extracting device and storage medium |
| CN110249314A (en) * | 2016-12-21 | 2019-09-17 | 斯瑞特斯塔克股份有限公司 | The system and method monitored for OS Events based on cloud and data access |
| CN109558305A (en) * | 2017-09-27 | 2019-04-02 | 北京国双科技有限公司 | Daily record data sort method and device |
| CN114036360A (en) * | 2021-10-15 | 2022-02-11 | 网宿科技股份有限公司 | Web crawler intercepting method and device, electronic equipment and readable storage medium |
| CN114138604A (en) * | 2021-12-01 | 2022-03-04 | 浪潮云信息技术股份公司 | Transaction log processing method and system for distributed database |
| CN115914409A (en) * | 2022-11-14 | 2023-04-04 | 中盈优创资讯科技有限公司 | Method and device for realizing efficient transmission and storage of WAF (wireless LAN access point) safety protection log |
| CN116595012A (en) * | 2023-07-17 | 2023-08-15 | 华中科技大学 | Time sequence database log storage method and system based on nonvolatile memory |
Non-Patent Citations (2)
| Title |
|---|
| "Network Protocols for Security Professionals: Probe and identify network-based vulnerabilities and safeguard against network protocol breaches";Yoram Orzach 等;《Packt Publishing》;20221231;全文 * |
| 蜜罐系统中日志服务器的安全性研究及实现;徐兰云;程京;邱飚;;湖南城市学院学报(自然科学版);20081215(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117118824A (en) | 2023-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11855967B2 (en) | Method for identifying application information in network traffic, and apparatus | |
| US10013318B2 (en) | Distributed event correlation system | |
| US10218717B1 (en) | System and method for detecting a malicious activity in a computing environment | |
| CN109981653B (en) | Web vulnerability scanning method | |
| JP2018531527A6 (en) | Method and apparatus for identifying application information in network traffic | |
| CN111885050B (en) | Data storage method and device based on block chain network, related equipment and medium | |
| CN113067810B (en) | Network packet capturing method, device, equipment and medium | |
| CN112104572B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN106789486B (en) | Method and device for detecting shared access, electronic equipment and computer readable storage medium | |
| CN114465741B (en) | Abnormality detection method, abnormality detection device, computer equipment and storage medium | |
| CN112929376A (en) | Flow data processing method and device, computer equipment and storage medium | |
| CN113810381A (en) | Crawler detection method, web application cloud firewall, device and storage medium | |
| CN115023919A (en) | Firewall rule updating method and device, server and storage medium | |
| CN113965406A (en) | Network blocking method, device, electronic device and storage medium | |
| CN117118824B (en) | Log data collection method and device | |
| CN116743619B (en) | Network service testing method, device, equipment and storage medium | |
| CN113098852A (en) | Log processing method and device | |
| CN112257065A (en) | Process event processing method and device | |
| US11595419B2 (en) | Communication monitoring system, communication monitoring apparatus, and communication monitoring method | |
| CN114205150B (en) | Intrusion prevention method and device for container environment, electronic equipment and storage medium | |
| JP3892322B2 (en) | Unauthorized access route analysis system and unauthorized access route analysis method | |
| CN113691631B (en) | Data cleaning method and device and electronic equipment | |
| CN112153011A (en) | Detection method and device for machine scanning, electronic equipment and storage medium | |
| CN111787024B (en) | Method for collecting network attack evidence, electronic device and storage medium | |
| CN117319082B (en) | APT attack detection method and 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 |