CN114090433A - Buried point data reporting control method and device, storage medium and electronic equipment - Google Patents
Buried point data reporting control method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN114090433A CN114090433A CN202111328475.XA CN202111328475A CN114090433A CN 114090433 A CN114090433 A CN 114090433A CN 202111328475 A CN202111328475 A CN 202111328475A CN 114090433 A CN114090433 A CN 114090433A
- Authority
- CN
- China
- Prior art keywords
- buried point
- data
- reporting
- target
- historical
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3624—Software debugging by performing operations on the source code, e.g. via a compiler
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Computer Hardware Design (AREA)
- Mathematical Physics (AREA)
- Testing And Monitoring For Control Systems (AREA)
Abstract
The application discloses a buried point data reporting control method, a buried point data reporting control device, a storage medium and electronic equipment, and relates to the technical field of Internet, wherein the method comprises the following steps: when the monitored target buried point data trigger report, determining a buried point type corresponding to a data acquisition buried point of the target buried point data; obtaining historical data reporting information corresponding to the type of the embedded point from a local database; performing exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point; and when the state identification result is normal, reporting the target buried point data. According to the method and the device, the condition of abnormal reporting of the buried point can be avoided, and the reliability of reporting of the buried point data is improved.
Description
Technical Field
The application relates to the technical field of computers, in particular to a buried point data reporting control method and device, a storage medium and electronic equipment.
Background
Taking an Android system as an example, there is a demand for acquiring data in the system and analyzing performance in various industries at present, and a scheme of acquiring data at a set buried point and reporting the data is generally adopted to obtain data for performance analysis. In the process of reporting the buried points, some buried points are abnormal, so that a large amount of data can be reported in a short period, the pressure of a server end is increased, and the working pressure of a performance analyzer is also increased. Therefore, at present, the problem of low reporting reliability caused by reporting abnormality when the buried point data is reported exists.
Disclosure of Invention
The embodiment of the application provides a scheme, which can avoid the abnormal reporting condition of the buried point and improve the reporting reliability of the buried point data.
The embodiment of the application provides the following technical scheme:
according to an embodiment of the present application, a buried point data reporting control method includes: when the monitored target buried point data trigger report, determining a buried point type corresponding to a data acquisition buried point of the target buried point data; obtaining historical data reporting information corresponding to the type of the embedded point from a local database; performing exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point; and when the state identification result is normal, reporting the target buried point data.
In some embodiments of the present application, the performing abnormality identification based on the historical data report information to obtain a state identification result of the data collection buried point includes: acquiring historical reporting state information from the historical data reporting information, wherein the historical reporting state information is generated when historical buried point data is triggered and reported at the previous time at the current moment, and the type of a data acquisition buried point of the historical buried point data is the buried point type; if the historical reported state information is abnormal, determining that the state identification result of the data acquisition buried point is abnormal; and if the historical reporting state information is normal, acquiring the reporting time of the historical buried point data from the historical data reporting information, and determining the state identification result of the data acquisition buried point according to the reporting time.
In some embodiments of the present application, the determining the state identification result of the data collection buried point according to the reporting time includes: if the difference value between the reporting time and the current time is smaller than a target threshold value, determining that the state identification result of the data acquisition buried point is abnormal; and if the difference value between the reporting time and the current time is larger than the target threshold, determining that the state identification result of the data acquisition buried point is normal.
In some embodiments of the present application, the performing abnormality identification based on the historical data report information to obtain a state identification result of the data collection buried point includes: acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data; performing anomaly identification processing based on the terminal state information, the module state information and historical reported state information in the historical data reported information by adopting a target anomaly analysis model to obtain at least one state information and the confidence coefficient of each state information; and determining a state identification result of the data acquisition buried point according to the at least one state information and the confidence coefficient of each state information.
In some embodiments of the present application, the method further comprises: acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data; performing threshold analysis based on the terminal state information, the module state information and the historical reported state information by adopting a target threshold analysis model to obtain at least one threshold and the confidence of each threshold; determining the target threshold value according to the at least one threshold value and the confidence of each threshold value.
In some embodiments of the present application, the method further comprises: and when the state identification result is abnormal, the target buried point data is subjected to report stopping processing.
In some embodiments of the present application, a cache area and a first interface are established in a log saving process, where the first interface is used for being called by a first performance module in a user program space, and the log saving process includes a target thread; establishing a target kernel thread, a communication thread and a second interface in a kernel space, wherein the target kernel thread carries out cross-thread communication with the target thread through the communication thread, and the second interface is used for being called by a second performance module in a user program space; the processing of stopping reporting the target buried point data includes: when the acquisition buried point is located in the first performance module and the target buried point data is triggered to be reported by the acquisition buried point, calling the first interface based on the first performance module and storing the target buried point data to the cache region; and when the acquisition buried point is positioned in the second performance module and the target buried point data is triggered to be reported by the acquisition buried point, calling the second interface based on the second performance module, and storing the target buried point data to the cache region through cross-thread communication.
According to an embodiment of the present application, a buried point data reporting control device includes: the monitoring module is used for determining the buried point type corresponding to the data acquisition buried point of the target buried point data when the monitored target buried point data is triggered to report; the acquisition module is used for acquiring historical data reporting information corresponding to the embedded point type from a local database; the identification module is used for carrying out exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point; and the control module is used for reporting the target buried point data when the state identification result is normal.
According to another embodiment of the present application, a storage medium has stored thereon a computer program which, when executed by a processor of a computer, causes the computer to perform the method of an embodiment of the present application.
According to another embodiment of the present application, an electronic device may include: a memory storing a computer program; and the processor reads the computer program stored in the memory to execute the method in the embodiment of the application.
In the embodiment of the application, when the triggering report of the target buried point data is monitored, the buried point type corresponding to the data acquisition buried point of the target buried point data is determined; obtaining historical data reporting information corresponding to the type of the embedded point from a local database; performing exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point; and when the state identification result is normal, reporting the target buried point data.
In this way, when the target buried point data is detected to trigger reporting, the buried point type of the data acquisition buried point for acquiring the data is determined, and exception identification processing is performed according to the historical data reporting information corresponding to the buried point type, so that the state identification result of the buried point can be accurately obtained, and further, when the state identification result is normal, the buried point data is reported, so that the abnormal reporting situation of the buried point can be avoided, and the reporting reliability of the buried point data is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 shows a schematic diagram of a system to which embodiments of the present application may be applied.
Fig. 2 shows a flowchart of a buried point data reporting control method according to an embodiment of the present application.
Fig. 3 shows a block diagram of a buried point data reporting control apparatus according to an embodiment of the present application.
FIG. 4 shows a block diagram of an electronic device according to an embodiment of the application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description that follows, specific embodiments of the present application will be described with reference to steps and symbols executed by one or more computers, unless otherwise indicated. Accordingly, these steps and operations will be referred to, several times, as being performed by a computer, the computer performing operations involving a processing unit of the computer in electronic signals representing data in a structured form. This operation transforms the data or maintains it at locations in the computer's memory system, which may be reconfigured or otherwise altered in a manner well known to those skilled in the art. The data maintains a data structure that is a physical location of the memory that has particular characteristics defined by the data format. However, the principles of the present application are described in the foregoing text and are not meant to be limiting, as those of ordinary skill in the art will appreciate that various steps and operations described below may be implemented in hardware.
FIG. 1 shows a schematic diagram of a system 100 to which embodiments of the present application may be applied. As shown in fig. 1, the system 100 may include a server 101, a terminal 102. The terminal 102 may be any computer device, such as a computer, a mobile phone, a smart watch, a home appliance, and the like. The server 101 may be a server cluster or a cloud service, etc.
In one implementation of this example, the terminal 102 may: when the monitored target buried point data trigger report, determining a buried point type corresponding to a data acquisition buried point of the target buried point data; obtaining historical data reporting information corresponding to the type of the embedded point from a local database; performing exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point; and when the state identification result is normal, reporting the target buried point data. Wherein the buried point data may be reported to the server 101.
Fig. 2 schematically shows a flowchart of a buried point data reporting control method according to an embodiment of the present application. The execution main body of the buried point data reporting control method may be any device, such as the first terminal 102 shown in fig. 1.
As shown in fig. 2, the buried point data reporting control method may include steps S210 to S240.
Step S210, when triggering reporting of target buried point data is monitored, determining a buried point type corresponding to a data acquisition buried point of the target buried point data;
step S220, obtaining historical data reporting information corresponding to the type of the buried point from a local database;
step S230, performing exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point;
and step S240, when the state identification result is normal, reporting the target buried point data.
The acquisition buried point is an acquisition code buried point of data in acquisition equipment, and the target buried point data is data in the acquisition equipment acquired by the acquisition buried point. The reporting of the target buried point data can be triggered by the acquisition buried point itself, or can be caused by repeated processing of the buried point data acquired by the acquisition buried point by the buried point data processing logic in the equipment.
When monitored that target buried point data trigger reporting, determining a buried point type corresponding to a data acquisition buried point of the target buried point data, wherein the buried point type is the type of the acquisition buried point. In one embodiment, the type of the buried point corresponds to a terminal performance module in the device, for example, a kernel module, and at this time, the type of a certain collection buried point may be a kernel type. The kernel type may correspond to a plurality of (e.g., at least two) collection burial points, for example, the kernel module may include a Mem submodule, a CPU submodule, an I0 submodule, and the like, and each submodule may correspond to one collection burial point.
Data abstract information (such as acquisition position information, buried point mark information and the like) can be extracted from the target data buried points, then the data acquisition buried points of the target buried point data can be determined by inquiring the information configuration table based on the data abstract information, and further the buried point types of the data acquisition buried points of the target buried point data can be determined from the inquiring information configuration table.
The local database can collect local data reporting records, and the data reporting records are subjected to type management based on the buried point type. Based on the determined type of the embedded point, historical data reporting information corresponding to the determined type of the embedded point can be obtained from a database, and the historical data reporting information is data reporting history records of all the embedded points of the type of the embedded point.
The historical data reporting information can reflect the reporting rule of the data acquisition buried point of the type, and then the abnormal identification processing is carried out based on the historical data reporting information, so that the state identification result of the data acquisition buried point can be accurately obtained, wherein the state identification result is the identification result of whether the data acquisition buried point is in a normal reporting state or not.
Furthermore, when the state identification result is normal, the buried point data is reported, so that the condition that the buried point reports abnormally can be avoided.
In this way, based on steps S210 to S240, when it is detected that the target buried point data triggers reporting, the buried point type of the data collection buried point for collecting the data is determined, and abnormality recognition processing is performed according to the historical data reporting information corresponding to the buried point type, so that the state recognition result of the buried point can be accurately obtained.
The following describes specific processes of each step performed when the buried point data reporting control is performed.
In step S210, when it is monitored that the target buried point data triggers reporting, a buried point type corresponding to the data acquisition buried point of the target buried point data is determined.
The acquisition buried point is an acquisition code buried point of data in acquisition equipment, and the target buried point data is data in the acquisition equipment acquired by the acquisition buried point. The reporting of the target buried point data can be triggered by the acquisition buried point itself, or can be caused by repeated processing of the buried point data acquired by the acquisition buried point by the buried point data processing logic in the equipment.
When monitored that target buried point data trigger reporting, determining a buried point type corresponding to a data acquisition buried point of the target buried point data, wherein the buried point type is the type of the acquisition buried point. In one embodiment, the type of the buried point corresponds to a performance module in the device, such as a kernel module, where a certain collection buried point may be a kernel type, where a plurality of (e.g., at least two) collection buried points may be corresponding to the kernel type.
Data abstract information (such as acquisition position information, buried point mark information and the like) can be extracted from the target data buried points, then the data acquisition buried points of the target buried point data can be determined by inquiring the information configuration table based on the data abstract information, and further the buried point types of the data acquisition buried points of the target buried point data can be determined from the inquiring information configuration table.
In step S220, obtaining historical data reporting information corresponding to the type of the embedded point from a local database;
the local database can collect local data reporting records, and the data reporting records are subjected to type management based on the buried point type. Based on the determined type of the embedded point, historical data reporting information corresponding to the determined type of the embedded point can be obtained from a database, and the historical data reporting information is data reporting history records of all the embedded points of the type of the embedded point.
The method can record information such as reporting time of data burying data and the like when triggering data reporting locally every time, and form historical data reporting records.
In step S230, performing anomaly identification processing based on the historical data reporting information to obtain a state identification result of the data collection buried point;
the historical data reporting information can reflect the reporting rule of the data acquisition buried point of the type, and then the abnormal identification processing is carried out based on the historical data reporting information, so that the state identification result of the data acquisition buried point can be accurately obtained, wherein the state identification result is the identification result of whether the data acquisition buried point is in a normal reporting state or not.
In one embodiment, the step S230 of performing anomaly identification based on the historical data reporting information to obtain a state identification result of the data collection buried point includes:
acquiring historical reporting state information from the historical data reporting information, wherein the historical reporting state information is generated when historical buried point data is triggered and reported at the previous time at the current moment, and the type of a data acquisition buried point of the historical buried point data is the buried point type; if the historical reported state information is abnormal, determining that the state identification result of the data acquisition buried point is abnormal; and if the historical reporting state information is normal, acquiring the reporting time of the historical buried point data from the historical data reporting information, and determining the state identification result of the data acquisition buried point according to the reporting time.
The historical reporting state information is generated when the previous historical buried point data is triggered to be reported before the current time, and the type of the data acquisition buried point of the historical buried point data is the buried point type, so that the historical reporting state information can reflect whether the data reporting state of the previous buried point type is normal or not. The state at the current moment can be reflected to a certain extent based on the previous data reporting state.
Furthermore, if the historical reported state information is abnormal, the state identification result of the data acquisition buried point is directly determined to be abnormal, and abnormal reporting can be effectively avoided.
Furthermore, if the historical reporting state information is normal, the reporting time of the historical buried point data is obtained from the historical data reporting information, and the state identification result of the data acquisition buried point is determined according to the reporting time, so that whether the current report is abnormal can be further accurately verified, and the reporting management reliability is ensured.
In one embodiment, determining the status identification result of the data collection buried point according to the reporting time includes: if the difference value between the reporting time and the current time is smaller than a target threshold value, determining that the state identification result of the data acquisition buried point is abnormal; and if the difference value between the reporting time and the current time is larger than the target threshold, determining that the state identification result of the data acquisition buried point is normal.
If the difference value between the reporting time of the historical buried point data and the current time is smaller than the target threshold value, the reporting frequency is over high, the state identification result of the data acquisition buried point is determined to be abnormal, abnormal reporting is further avoided, and otherwise, the reporting is allowed.
In one embodiment, the method further comprises a target threshold determination method, so as to adaptively and accurately obtain the target threshold, and improve the accuracy of abnormality judgment: acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data; performing threshold analysis based on the terminal state information, the module state information and the historical reported state information by adopting a target threshold analysis model to obtain at least one threshold and the confidence of each threshold; determining the target threshold value according to the at least one threshold value and the confidence of each threshold value.
The terminal state information, that is, the global state information of the terminal itself, may include information such as the number of tasks running on the terminal, task information of running tasks, and CPU occupation state, which are collected. The terminal performance module corresponding to the data acquisition buried point is a specific performance module in the terminal, for example, a kernel module, and the data acquisition buried point is used for acquiring data of the corresponding terminal performance module. The module state information is the specific state information in the terminal capability module.
The target threshold analysis model is an intelligent model based on deep learning, and is trained in advance through collected training samples. And performing threshold analysis by adopting a target threshold analysis model based on the terminal state information, the module state information and the historical reported state information to obtain at least one threshold and the confidence of each threshold, and then screening out an accurate threshold (such as a threshold with the highest confidence) as a target threshold according to the confidence to realize self-adaptive updating of the target threshold.
It is understood that in some embodiments, the target threshold may be an empirical value set according to actual requirements, and the determination accuracy may be ensured to a certain extent.
In one embodiment, the performing abnormality identification based on the historical data reporting information to obtain a state identification result of the data collection buried point includes:
acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data; performing anomaly identification processing based on the terminal state information, the module state information and historical reported state information in the historical data reported information by adopting a target anomaly analysis model to obtain at least one state information and the confidence coefficient of each state information; and determining a state identification result of the data acquisition buried point according to the at least one state information and the confidence coefficient of each state information.
The terminal state information, that is, the global state information of the terminal itself, may include information such as the number of tasks running on the terminal, task information of running tasks, and CPU occupation state, which are collected. The terminal performance module corresponding to the data acquisition buried point is a specific performance module in the terminal, for example, a kernel module, and the data acquisition buried point is used for acquiring data of the corresponding terminal performance module. The module state information is the specific state information in the terminal capability module.
The target anomaly analysis model is an intelligent model based on deep learning, and is trained in advance through collected training samples. And performing anomaly identification processing based on the terminal state information, the module state information and historical reported state information in the historical data reported information by adopting a target threshold analysis model to obtain at least one state information and the confidence coefficient of each state information, and then screening out accurate state information (such as the state information with the highest confidence coefficient) according to the confidence coefficient to serve as a state identification result, thereby further improving the judgment accuracy of the state identification result.
In step S240, when the status identification result is normal, the target buried point data is reported.
When the state identification result is normal, reporting the data of the buried point is carried out, so that the abnormal reporting situation of the buried point can be avoided, and the reporting reliability of the data of the buried point is improved.
In one embodiment, the method further comprises: and when the state identification result is abnormal, the target buried point data is subjected to report stopping processing.
And stopping reporting, namely deleting the buried point data in one example, and locally caching the target buried point data in another example.
When target buried point data is cached locally, in one embodiment, a cache region and a first interface are established in a log saving process, the first interface is used for being called by a first performance module in a user program space, and the log saving process comprises a target thread; establishing a target kernel thread, a communication thread and a second interface in a kernel space, wherein the target kernel thread carries out cross-thread communication with the target thread through the communication thread, and the second interface is used for being called by a second performance module in a user program space; the processing of stopping reporting the target buried point data includes: when the acquisition buried point is positioned in the first performance module, calling the first interface based on the first performance module, and storing the target buried point data to the cache region; and when the acquisition buried point is positioned in the second performance module, calling the second interface based on the second performance module, and storing the target buried point data to the cache region through cross-thread communication.
The first performance module and the second performance module are both terminal performance modules in the terminal; the first performance module is positioned in a user program space (namely userpace), and the first performance module can comprise an AMS module, a Looper module, a Native module, a centres module, a Contact module, an Mms module and the like; the second performance module is located in the kernel space (i.e., kernel space), and may include a Mem module, a CPU module, an I0 module, and the like.
The log saving process is a logd process, a cache region and a first interface are established in the log saving process, the first interface is used for being called by a first performance module in a user program space, and the log saving process comprises a target thread. And establishing a target kernel thread, a communication thread and a second interface in the kernel space, wherein the target kernel thread carries out cross-thread communication with the target thread through the communication thread, and the second interface is used for being called by a second performance module in the user program space. Therefore, a unified management framework of the performance modules in the user program space and the kernel space can be realized, the coupling between data acquisition buried points can be reduced based on the framework, and the data cache is convenient and reliable. When abnormal reporting occurs to data acquisition buried points in different performance modules, cache processing can be conveniently and reliably realized, and effective cooperation of avoiding reporting and data storage is realized.
Specifically, when the reporting processing is stopped, when the acquisition buried point of the target buried point data is located in the first performance module and the target buried point data is triggered to be reported by the acquisition buried point, the first interface is called based on the first performance module, and the target buried point data is stored in the cache region; when the acquisition buried point is located in the second performance module and the target buried point data is triggered to be reported by the acquisition buried point, the second interface is called based on the second performance module, and the target buried point data is stored in the cache region through cross-thread communication, so that abnormal control of the buried point data can be further conveniently, reliably and low-coupling.
In order to better implement the buried point data reporting control method provided in the embodiments of the present application, the embodiments of the present application further provide a buried point data reporting control device based on the buried point data reporting control method. The meaning of the noun is the same as that in the buried point data reporting control method, and specific implementation details can refer to the description in the method embodiment. Fig. 3 shows a block diagram of a buried point data reporting control apparatus according to an embodiment of the present application.
As shown in fig. 3, the buried point data reporting control apparatus 300 may include a monitoring module 310, an obtaining module 320, an identifying module 330, and a control module 340.
The monitoring module 310 may be configured to determine a buried point type corresponding to a data acquisition buried point of target buried point data when it is monitored that the target buried point data triggers reporting; the obtaining module 320 may be configured to obtain, from a local database, historical data reporting information corresponding to the type of the embedded point; the identification module 330 may be configured to perform exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point; the control module 340 may be configured to report the target buried point data when the state identification result is normal.
In some embodiments of the present application, the identification module 330 includes: a state information obtaining unit, configured to obtain historical reporting state information from the historical data reporting information, where the historical reporting state information is generated when reporting of historical buried point data is triggered at a previous time before a current time, and a type of a data acquisition buried point of the historical buried point data is the buried point type; the first identification unit is used for determining that the state identification result of the data acquisition buried point is abnormal if the historical reported state information is abnormal; and the second identification unit is used for acquiring the reporting time of the historical buried point data from the historical data reporting information and determining the state identification result of the data acquisition buried point according to the reporting time if the historical reporting state information is normal.
In some embodiments of the present application, the second identification unit is configured to: if the difference value between the reporting time and the current time is smaller than a target threshold value, determining that the state identification result of the data acquisition buried point is abnormal; and if the difference value between the reporting time and the current time is larger than the target threshold, determining that the state identification result of the data acquisition buried point is normal.
In some embodiments of the present application, the identification module 330 includes: the information acquisition unit is used for acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data; the model analysis unit is used for performing anomaly identification processing based on the terminal state information, the module state information and the historical reported state information by adopting a target anomaly analysis model to obtain at least one state information and the confidence coefficient of each state information; and the result determining unit is used for determining the state identification result of the data acquisition buried point according to the at least one state information and the confidence coefficient of each state information.
In some embodiments of the present application, the apparatus further comprises a threshold updating unit configured to: acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data; performing threshold analysis based on the terminal state information, the module state information and historical reported state information in the historical data reported information by adopting a target threshold analysis model to obtain at least one threshold and a confidence coefficient of each threshold; determining the target threshold value according to the at least one threshold value and the confidence of each threshold value.
In some embodiments of the present application, the apparatus further comprises a stop control model for: and when the state identification result is abnormal, the target buried point data is subjected to report stopping processing.
In some embodiments of the present application, a cache area and a first interface are established in a log saving process, where the first interface is used for being called by a first performance module in a user program space, and the log saving process includes a target thread; establishing a target kernel thread, a communication thread and a second interface in a kernel space, wherein the target kernel thread carries out cross-thread communication with the target thread through the communication thread, and the second interface is used for being called by a second performance module in a user program space; the stop control model includes: the first control unit is used for calling the first interface based on the first performance module and storing the target buried point data to the cache region when the acquisition buried point is positioned in the first performance module and the target buried point data is triggered to be reported by the acquisition buried point; and the second control unit is used for calling the second interface based on the second performance module and storing the target buried point data to the cache region through the cross-thread communication when the acquisition buried point is positioned in the second performance module and the target buried point data is triggered and reported by the acquisition buried point.
In this way, based on the buried point data reporting control device 300, when it is detected that the target buried point data triggers reporting, the buried point type of the data acquisition buried point for acquiring the data is determined, and abnormality recognition processing is performed according to the historical data reporting information corresponding to the buried point type, so that the state recognition result of the buried point can be accurately obtained, and further, when the state recognition result is normal, the buried point data is reported, so that the abnormal reporting situation of the buried point data can be avoided, and the reliability of the buried point data reporting is improved.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
In addition, an embodiment of the present application further provides an electronic device, where the electronic device may be a terminal or a server, as shown in fig. 4, which shows a schematic structural diagram of the electronic device according to the embodiment of the present application, and specifically:
the electronic device may include components such as a processor 401 of one or more processing cores, memory 402 of one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will appreciate that the electronic device configuration shown in fig. 4 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:
the processor 401 is a control center of the electronic device, connects various parts of the entire computer device using various interfaces and lines, and performs various functions of the computer device and processes data by operating or executing software programs and/or modules stored in the memory 402 and calling data stored in the memory 402, thereby integrally monitoring the electronic device. Optionally, processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly handles operating systems, user pages, application programs, and the like, and the modem processor mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 401.
The memory 402 may be used to store software programs and modules, and the processor 401 executes various functional applications and data processing by operating the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to use of the computer device, and the like. Further, the memory 402 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 access to the memory 402.
The electronic device further comprises a power supply 403 for supplying power to the various components, and preferably, the power supply 403 is logically connected to the processor 401 through a power management system, so that functions of managing charging, discharging, and power consumption are realized through the power management system. The power supply 403 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
The electronic device may further include an input unit 404, and the input unit 404 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Although not shown, the electronic device may further include a display unit and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 401 in the electronic device loads the executable file corresponding to the process of one or more computer programs into the memory 402 according to the following instructions, and the processor 401 runs the computer program stored in the memory 402, so as to implement various functions, for example, the processor 401 may execute the following steps:
when the monitored target buried point data trigger report, determining a buried point type corresponding to a data acquisition buried point of the target buried point data; obtaining historical data reporting information corresponding to the type of the embedded point from a local database; performing exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point; and when the state identification result is normal, reporting the target buried point data.
In some embodiments of the present application, the performing abnormality identification based on the historical data report information to obtain a state identification result of the data collection buried point includes: acquiring historical reporting state information from the historical data reporting information, wherein the historical reporting state information is generated when historical buried point data is triggered and reported at the previous time at the current moment, and the type of a data acquisition buried point of the historical buried point data is the buried point type; if the historical reported state information is abnormal, determining that the state identification result of the data acquisition buried point is abnormal; and if the historical reporting state information is normal, acquiring the reporting time of the historical buried point data from the historical data reporting information, and determining the state identification result of the data acquisition buried point according to the reporting time.
In some embodiments of the present application, the determining the state identification result of the data collection buried point according to the reporting time includes: if the difference value between the reporting time and the current time is smaller than a target threshold value, determining that the state identification result of the data acquisition buried point is abnormal; and if the difference value between the reporting time and the current time is larger than the target threshold, determining that the state identification result of the data acquisition buried point is normal.
In some embodiments of the present application, the performing abnormality identification based on the historical data report information to obtain a state identification result of the data collection buried point includes: acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data; performing anomaly identification processing based on the terminal state information, the module state information and historical reported state information in the historical data reported information by adopting a target anomaly analysis model to obtain at least one state information and the confidence coefficient of each state information; and determining a state identification result of the data acquisition buried point according to the at least one state information and the confidence coefficient of each state information.
In some embodiments of the present application, the method further comprises: acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data; performing threshold analysis based on the terminal state information, the module state information and the historical reported state information by adopting a target threshold analysis model to obtain at least one threshold and the confidence of each threshold; determining the target threshold value according to the at least one threshold value and the confidence of each threshold value.
In some embodiments of the present application, the method further comprises: and when the state identification result is abnormal, the target buried point data is subjected to report stopping processing.
In some embodiments of the present application, a cache area and a first interface are established in a log saving process, where the first interface is used for being called by a first performance module in a user program space, and the log saving process includes a target thread; establishing a target kernel thread, a communication thread and a second interface in a kernel space, wherein the target kernel thread carries out cross-thread communication with the target thread through the communication thread, and the second interface is used for being called by a second performance module in a user program space; the processing of stopping reporting the target buried point data includes: when the acquisition buried point is located in the first performance module and the target buried point data is triggered to be reported by the acquisition buried point, calling the first interface based on the first performance module and storing the target buried point data to the cache region; and when the acquisition buried point is positioned in the second performance module and the target buried point data is triggered to be reported by the acquisition buried point, calling the second interface based on the second performance module, and storing the target buried point data to the cache region through cross-thread communication.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by a computer program, which may be stored in a computer-readable storage medium and loaded and executed by a processor, or by related hardware controlled by the computer program.
To this end, the present application further provides a storage medium, in which a computer program is stored, where the computer program can be loaded by a processor to execute the steps in any one of the methods provided in the present application.
Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
Since the computer program stored in the storage medium can execute the steps in any method provided in the embodiments of the present application, the beneficial effects that can be achieved by the methods provided in the embodiments of the present application can be achieved, for details, see the foregoing embodiments, and are not described herein again.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains.
It will be understood that the present application is not limited to the embodiments that have been described above and shown in the drawings, but that various modifications and changes can be made without departing from the scope thereof.
Claims (10)
1. A buried point data reporting control method is characterized by comprising the following steps:
when the monitored target buried point data trigger report, determining a buried point type corresponding to a data acquisition buried point of the target buried point data;
obtaining historical data reporting information corresponding to the type of the embedded point from a local database;
performing exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point;
and when the state identification result is normal, reporting the target buried point data.
2. The method of claim 1, wherein the performing anomaly identification based on the historical data reporting information to obtain the state identification result of the data acquisition buried point comprises:
acquiring historical reporting state information from the historical data reporting information, wherein the historical reporting state information is generated when historical buried point data is triggered and reported at the previous time at the current moment, and the type of a data acquisition buried point of the historical buried point data is the buried point type;
if the historical reported state information is abnormal, determining that the state identification result of the data acquisition buried point is abnormal;
and if the historical reporting state information is normal, acquiring the reporting time of the historical buried point data from the historical data reporting information, and determining the state identification result of the data acquisition buried point according to the reporting time.
3. The method of claim 2, wherein determining the status identification result of the data collection buried point according to the reporting time comprises:
if the difference value between the reporting time and the current time is smaller than a target threshold value, determining that the state identification result of the data acquisition buried point is abnormal;
and if the difference value between the reporting time and the current time is larger than the target threshold, determining that the state identification result of the data acquisition buried point is normal.
4. The method of claim 1, wherein the performing anomaly identification based on the historical data reporting information to obtain the state identification result of the data acquisition buried point comprises:
acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data;
performing anomaly identification processing based on the terminal state information, the module state information and historical reported state information in the historical data reported information by adopting a target anomaly analysis model to obtain at least one state information and the confidence coefficient of each state information;
and determining a state identification result of the data acquisition buried point according to the at least one state information and the confidence coefficient of each state information.
5. The method of claim 3, further comprising:
acquiring terminal state information of a local terminal and module state information of a terminal performance module corresponding to the data acquisition buried point of the target buried point data;
performing threshold analysis based on the terminal state information, the module state information and the historical reported state information by adopting a target threshold analysis model to obtain at least one threshold and the confidence of each threshold;
determining the target threshold value according to the at least one threshold value and the confidence of each threshold value.
6. The method of claim 1, further comprising:
and when the state identification result is abnormal, the target buried point data is subjected to report stopping processing.
7. The method of claim 6, wherein a cache and a first interface are established in a log saving process, the first interface is used for being called by a first performance module in a user program space, and the log saving process comprises a target thread;
establishing a target kernel thread, a communication thread and a second interface in a kernel space, wherein the target kernel thread carries out cross-thread communication with the target thread through the communication thread, and the second interface is used for being called by a second performance module in a user program space;
the processing of stopping reporting the target buried point data includes:
when the acquisition buried point is located in the first performance module and the target buried point data is triggered to be reported by the acquisition buried point, calling the first interface based on the first performance module and storing the target buried point data to the cache region;
and when the acquisition buried point is positioned in the second performance module and the target buried point data is triggered to be reported by the acquisition buried point, calling the second interface based on the second performance module, and storing the target buried point data to the cache region through cross-thread communication.
8. A buried point data reporting control device is characterized by comprising:
the monitoring module is used for determining the buried point type corresponding to the data acquisition buried point of the target buried point data when the monitored target buried point data is triggered to report;
the acquisition module is used for acquiring historical data reporting information corresponding to the embedded point type from a local database;
the identification module is used for carrying out exception identification processing based on the historical data reporting information to obtain a state identification result of the data acquisition buried point;
and the control module is used for reporting the target buried point data when the state identification result is normal.
9. A storage medium having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to carry out the method of any one of claims 1 to 7.
10. An electronic device, comprising: a memory storing a computer program; a processor reading a computer program stored in the memory to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111328475.XA CN114090433A (en) | 2021-11-10 | 2021-11-10 | Buried point data reporting control method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111328475.XA CN114090433A (en) | 2021-11-10 | 2021-11-10 | Buried point data reporting control method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114090433A true CN114090433A (en) | 2022-02-25 |
Family
ID=80299607
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111328475.XA Pending CN114090433A (en) | 2021-11-10 | 2021-11-10 | Buried point data reporting control method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114090433A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225660A (en) * | 2022-05-20 | 2022-10-21 | 上海电气国轩新能源科技有限公司 | Method, system, device and medium for processing communication data in energy storage system |
-
2021
- 2021-11-10 CN CN202111328475.XA patent/CN114090433A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225660A (en) * | 2022-05-20 | 2022-10-21 | 上海电气国轩新能源科技有限公司 | Method, system, device and medium for processing communication data in energy storage system |
| CN115225660B (en) * | 2022-05-20 | 2023-09-26 | 上海电气国轩新能源科技有限公司 | Method, system, equipment and medium for processing communication data in energy storage system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110928718B (en) | Abnormality processing method, system, terminal and medium based on association analysis | |
| CN109284269B (en) | Abnormal log analysis method and device, storage medium and server | |
| CN108388489B (en) | Server fault diagnosis method, system, equipment and storage medium | |
| CN108958729B (en) | Data processing method, device and storage medium | |
| CN111353911A (en) | Power equipment operation and maintenance method, system, equipment and storage medium | |
| CN110941530B (en) | Method, device, computer equipment and storage medium for acquiring monitoring data | |
| CN112486789A (en) | Log analysis system, method and device | |
| CN110990179B (en) | Task processing method, device and equipment | |
| CN109542722A (en) | Anomaly analysis processing method, device and storage medium | |
| CN114090433A (en) | Buried point data reporting control method and device, storage medium and electronic equipment | |
| CN113505044A (en) | Database warning method, device, equipment and storage medium | |
| CN114996103A (en) | Page abnormity detection method and device, electronic equipment and storage medium | |
| US9916220B2 (en) | Smart logging of trace data for storage systems | |
| CN110580220A (en) | method for measuring execution time of code segment and terminal equipment | |
| CN113220551A (en) | Index trend prediction and early warning method and device, electronic equipment and storage medium | |
| CN114416542A (en) | Data reporting method and device, storage medium and electronic equipment | |
| CN111045849A (en) | Method, device, server and storage medium for identifying reason of checking abnormality | |
| CN114244681B (en) | Equipment connection fault early warning method and device, storage medium and electronic equipment | |
| CN113472881B (en) | Statistical method and device for online terminal equipment | |
| CN109634796A (en) | A kind of method for diagnosing faults of computer, apparatus and system | |
| CN114328103A (en) | Method, system and related equipment for OpenBMC monitoring and management of discrete sensor | |
| CN113468029A (en) | Log management method and device, electronic equipment and readable storage medium | |
| CN111447086B (en) | Service processing method and device and electronic equipment | |
| CN112907257A (en) | Risk threshold determining method, abnormality detecting device and electronic equipment | |
| CN111124820A (en) | Method for realizing off-line monitoring and analysis of operating system and process resources |
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 |