Plug-in based data background real-time monitoring processing method and system

Abstract

The application relates to the technical field of real-time monitoring, in particular to a data background real-time monitoring processing method and system based on plug-ins, which comprises the following steps: obtaining an activated plug-in thread identifier, analyzing field output content to extract a name path and a write state to establish a mapping structure, pairing path fields to identify name coincident data groups, judging field write time window overlap and buffer channel consistency to extract conflict path numbers, processing field order and delayed writing and updating the write state, and obtaining a monitoring field processing state list; in the application, plug-in field mapping structure is constructed to bind fields and output paths, conflict paths are identified, write time windows and buffer channel consistency are compared, a field order comparison mechanism is established to control repeated field delayed writing, a field control state table is generated, a monitoring processing state list is output according to field attribution and a function block, field behavior and control information consistency is guaranteed, and monitoring data processing integrity and logical reliability are improved.

Description

Technical Field

[0001] This invention relates to the field of real-time monitoring technology, and in particular to a plugin-based real-time data background monitoring and processing method and system. Background Technology

[0002] Real-time monitoring technology involves technical methods for continuously observing and processing system operating status, business data changes, and operational behaviors. Its core aspects include high-frequency data acquisition, status identification, anomaly detection, processing response, and information output. Through steps such as configuring monitoring points, collecting key indicators, setting judgment rules, executing event processing, and recording logs, dynamic processes can be tracked and controlled. The methodological path in this field typically relies on a data processing flow combining active monitoring and periodic tasks to achieve real-time understanding and handling of the target object's status. Traditional plug-in-based real-time data backend monitoring methods involve deploying plug-ins on servers or application systems to access the data flow path. The plug-ins capture operating logs, task execution information, or data change records according to set rules and transmit the data to the backend processing logic through a timer control mechanism. The backend identifies status changes based on key field comparisons or predefined threshold judgment methods, and then records the data by writing it to a database in a fixed format or outputting text logs. This method generally uses methods such as periodically querying log files, polling key database entries, or calling interfaces to obtain data snapshots to achieve data monitoring and processing.

[0003] Existing technologies cannot achieve precise matching of field names across multiple paths during the processing of plugin field data, resulting in omissions in field conflict detection. The field writing process lacks cross-validation mechanisms at the time window and channel levels, which can easily lead to problems such as duplicate field writing or disordered order. Data synchronization and consistency in multi-threaded or multi-path environments are difficult to guarantee, ultimately affecting the stability and accuracy of the backend monitoring system. Summary of the Invention

[0004] To address the technical problems existing in the prior art, embodiments of the present invention provide a plugin-based real-time data background monitoring and processing method;

[0005] To achieve the above objectives, the present invention adopts the following technical solution: a plugin-based real-time data background monitoring and processing method, comprising the following steps:

[0006] S1: Obtain the identifier of the active plugin thread, parse the field output content corresponding to the plugin thread, extract the field name, field output path and background writable status, the corresponding fields and the functional behavior of the plugin thread, and obtain the plugin field mapping structure set.

[0007] S2: Based on the plugin field mapping structure set, compare the plugin path field names, identify path pairs with overlapping names and match the fields to obtain a field path overlapping pairing data group;

[0008] S3: Based on the path pair information in the field path overlap pairing data group, supplement the extraction of the buffer channel identifier corresponding to the field, determine the time window overlap status of the field writing behavior and compare the consistency of the buffer channel, separate the conflict path, and obtain the conflict path number mapping list.

[0009] S4: Based on the path number in the conflict path number mapping list, read the field order in the path, perform write delay processing on duplicate fields, and update the field write status to obtain the field write control status table.

[0010] S5: Write the fields into the control status table, verify the consistency of the field order structure, and obtain the monitoring field processing status list according to the field behavior status, path number and control information mapping status action.

[0011] As a further embodiment of the present invention, the plugin field mapping structure set includes field name, field output path, and background write permission status; the field path overlap pairing data group includes field name overlap path pairs, field name corresponding to each path group, and mapping relationship between field paths; the conflict path number mapping list includes path number, field write time window overlap identifier, and buffer channel consistency identifier; the field write control status table includes field order, field write delay status, and field path number; and the monitoring field processing status list includes plugin information to which the field belongs, function block identifier, field sequence structure consistency status, field behavior status, and control information mapping result.

[0012] As a further aspect of the present invention, the field output content corresponding to the plug-in thread refers to the original data set mapped by the monitoring system fields;

[0013] The field writing behavior refers to the process of detecting conflicts in the field writing timing and path.

[0014] As a further aspect of the present invention, the update field write status refers to eliminating write conflicts and marking the field status through a delayed processing mechanism;

[0015] The mapping state action refers to the process of mapping field behavior with control policies to generate monitoring and processing status.

[0016] As a further aspect of the present invention, the specific steps of S1 are as follows:

[0017] S101: Obtain the identifier of the currently active plugin thread, monitor the data output content corresponding to each plugin thread, extract the field name, field output path and backend write permission status, corresponding field name and source plugin thread, and append the field output path and permission status to the corresponding field item to obtain the initial associated content of the field information.

[0018] S102: Based on the initial associated content of the field information, extract the correspondence between the field output path and the plugin thread, compare the thread source corresponding to the field path with the plugin thread identifier in the field output path set, and obtain the path thread consistent field set;

[0019] S103: Based on the path thread consistent field set, for the field's corresponding name, output path, permission status and plugin thread, match the field with the plugin, associate the field name with the field path corresponding to the plugin identifier, and append the permission status to the corresponding field path information to obtain the plugin field mapping structure set.

[0020] As a further aspect of the present invention, the specific steps of S2 are as follows:

[0021] S201: Based on the data of writable fields in the plugin field mapping structure set, extract the field name and field path, partition the plugin path, extract the field name under each path, assign the field name to the corresponding path set, and obtain a list of paths with repeated field names;

[0022] S202: Based on the list of repeated paths for the field name, read the field position of any two paths in the set, extract the positioning order of the field name in the two paths, and bidirectionally match the path number and field position of the same field in the differentiated path to obtain the matching list of the path field.

[0023] S203: Based on the path name, field name and field position data in the matching list corresponding to the path field, match the path name corresponding to the field, merge the path numbers with the same field name into the same output sequence, and output the path sequence under each field name independently to obtain the field path overlapping pairing data group.

[0024] As a further aspect of the present invention, the specific steps of S3 are as follows:

[0025] S301: Based on the path pair information in the field path overlap pairing data group, monitor the write timestamp sequence of the corresponding field in the path, compare the start time and end time of the field in the interval, identify path pairs with write intersection within the same time range, and obtain the path time window overlap comparison table.

[0026] S302: Based on the path pairs in the path time window overlap comparison table, inspect the buffer channel number pointed to by the field, compare the corresponding channel number in the field of the path pair, extract the path pairs with the same channel number, and obtain the buffer channel consistent path table.

[0027] S303: Based on the path pair information in the buffer channel consistent path table, parse the plug-in path identifier corresponding to the path, transfer the path pairs with time window intersection and the same channel number into the path group entries respectively, and convert them into number item columns to obtain the conflict path number mapping list.

[0028] As a further aspect of the present invention, the specific steps of S4 are as follows:

[0029] S401: Based on the path number information in the conflict path number mapping list, read the field writing order data under the corresponding plugin path of the path number, check the field appearance order within the same path, distinguish the first appearance position and the second appearance position of the field, and obtain the path field appearance order comparison table.

[0030] S402: Based on the path field occurrence order lookup table, detect the writing order of repeated fields in the same path, perform a delay adjustment action on the writing order of repeated fields, and synchronously write the delay mark into the field control information entry to obtain the field delay writing status set.

[0031] S403: Based on the set of delayed write statuses of the fields, the corresponding associated path number, field name and delayed status information are written into the field control data entry to obtain the field write control status table.

[0032] As a further aspect of the present invention, the specific steps of S5 are as follows:

[0033] S501: Based on the field written to the control status table, the set of fields in the delayed state is extracted, the plug-in identifier and function block name corresponding to the field are extracted, and the preset plug-in function structure table is associated to obtain the corresponding function block name. The fields are mapped into the field set in sequence according to the plug-in and function block information. During the mapping process, data items with inconsistent field numbers are excluded to obtain the field classification dataset.

[0034] S502: Based on the field set in the field classification dataset, retrieve the field occurrence order in the corresponding path, extract the field fragments that are adjacent to each other in the path and include write actions, and divide the field fragments into segments according to the path number to obtain the field path fragment set;

[0035] S503: Based on the behavior status, path number and control information of the fields in the field path fragment set, extract the control status of the fields in the path, update the field status label content according to the writing behavior status, and obtain the monitoring field processing status list.

[0036] A plug-in-based real-time data backend monitoring and processing system includes:

[0037] Plugin field mapping module: Obtain the identifier of the active plugin thread, parse the field output content corresponding to the plugin thread, extract the field name, field output path and backend writable status, the corresponding fields and plugin thread functional behaviors, and obtain the plugin field mapping structure set;

[0038] Path field pairing module: Based on the field name and path information of the writable fields in the plugin field mapping structure set, compare the plugin path field names, identify path pairs with overlapping names and pair the fields to obtain a field path overlapping pairing data group.

[0039] Conflict path identification module: Based on the path information in the field path overlapping pairing data group, supplement and extract the buffer channel identifier corresponding to the field, determine the time window overlap status of the field writing behavior and compare the consistency of the buffer channel, separate the conflict path, and obtain the conflict path number mapping list.

[0040] Write status control module: Based on the path number in the conflict path number mapping list, read the field order in the path, perform write delay processing on duplicate fields, and update the field write status to obtain the field write control status table.

[0041] Monitoring status output module: Based on the information of the delayed status field written into the control status table, the module classifies the fields by plug-in and function block, checks the consistency of the field order structure, and obtains the monitoring field processing status list according to the field behavior status, path number and control information mapping status action.

[0042] Compared with the prior art, the advantages and positive effects of the present invention are as follows:

[0043] In this invention, a plugin field mapping structure is constructed to bind fields to output paths. By combining overlapping field paths with paired data groups, conflicting paths are identified by number and the consistency of the writing time window and buffer channel is compared. A field writing order comparison mechanism is established to implement delayed writing control for duplicate fields. A field control status table is formed, and a monitoring field processing status list is output based on field ownership and functional block structure. This ensures the consistency of field behavior status and control information, improves the integrity of monitoring data processing and the logical reliability of system execution. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a schematic diagram of the steps of the present invention;

[0046] Figure 2 This is a detailed schematic diagram of S1 of the present invention;

[0047] Figure 3 This is a detailed schematic diagram of S2 of the present invention;

[0048] Figure 4 This is a detailed schematic diagram of S3 of the present invention;

[0049] Figure 5 This is a detailed schematic diagram of S4 of the present invention;

[0050] Figure 6 This is a detailed schematic diagram of S5 of the present invention;

[0051] Figure 7 This is a system module diagram of the present invention. Detailed Implementation

[0052] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0053] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0054] Please see Figure 1 This invention provides a plugin-based real-time data background monitoring and processing method, including the following steps:

[0055] S1: Obtain the identifier of the currently active plugin thread, parse the field output content corresponding to each plugin thread, extract the field name, field output path and backend write permission status, match the field output path according to the plugin thread, and map the fields to the plugin to obtain the plugin field mapping structure set.

[0056] S2: Based on the field name and path information of the writable fields in the plugin field mapping structure set, perform field matching on the plugin path in the running state, identify the plugin path pairs with overlapping names by comparing field names, match each pair of field path pairs, and obtain the field path overlapping pairing data group.

[0057] S3: Based on the path pair information in the field path overlap pairing data group, compare the writing behavior time window overlap status of the corresponding field in the path, compare the consistency of the buffer channel pointed to by the field, and after identifying the path pair that has both time window overlap relationship and buffer channel consistency, separate the conflicting path and obtain the conflicting path number mapping list.

[0058] S4: Based on the path number recorded in the conflict path number mapping list, write the field order of each path corresponding to the number, locate the field order of the first occurrence in the path, perform write delay processing on duplicate fields in the path, and delay the status in the field control information to obtain the field write control status table.

[0059] S5: Based on the set of fields in the delayed state of the field writing control status table, classify them according to the plug-in information and function block identifier of the field, check the consistency of the order structure of each group of fields after classification, identify the field sequence that is continuously arranged in the same path and has writing behavior, and perform state mapping actions according to the field behavior status, path number and control information to obtain the monitoring field processing status list.

[0060] The plugin field mapping structure set includes field name, field output path, and backend write permission status. The field path overlap pairing data group includes field name overlap path pairs, field name corresponding to each path, and mapping relationship between field paths. The conflict path number mapping list includes path number, field write time window overlap identifier, and buffer channel consistency identifier. The field write control status table includes field order, field write delay status, and field path number. The monitoring field processing status list includes plugin information to which the field belongs, function block identifier, field sequence structure consistency status, field behavior status, and control information mapping result.

[0061] Please see Figure 2 The specific steps of S1 are as follows:

[0062] S101: Obtain the identifier of the currently active plugin thread, monitor the data output content corresponding to each plugin thread, extract the field name, field output path and backend write permission status, corresponding field name and source plugin thread, and append the field output path and permission status to the corresponding field item to obtain the initial associated content of the field information.

[0063] First, by calling process management functions through the operating system's underlying kernel interface, all active plugin process branches in the current running memory space are retrieved in real time, and a unique hexadecimal thread identifier code is obtained for each plugin process. In the real-time monitoring scenario of industrial control systems, for the running data acquisition plugin thread, communication protocol conversion plugin thread, and logic operation plugin thread, hook functions are used to attach to the private memory buffer of each plugin thread, continuously monitoring the data stream content pushed out at a fixed frequency. For each captured data stream, the field name, such as the acquisition frequency field or pressure offset field, is extracted through message parsing logic, and the physical output path of the field in the distributed file system is recorded simultaneously. At the same time, the security access control list is accessed to query the underlying write permissions of the current thread identifier for the physical path, determining whether it is in a binary state of full access, read-only access, or write-prohibited access. The extracted field name is bound one-to-one with its corresponding plugin thread identifier to establish a traceability relationship between the field and its source. Then, the obtained physical output path information and permission status flags are appended to the corresponding field description structure to obtain the initial associated content of the field information.

[0064] S102: Based on the initial associated content of the field information, extract the correspondence between the field output path and the plugin thread, compare the thread source corresponding to the field path with the plugin thread identifier in the field output path set, and obtain the path thread consistent field set;

[0065] First, the array of field description structures in memory is traversed, and the output path string and plugin thread identifier encapsulated in each field item are read sequentially. All field output paths are aggregated to build a path index tree, and path attribution verification is performed. For each independent field output path, the parent process and its child thread identifiers bound during underlying registration are queried in reverse. The thread source recorded in the initial field association content is compared with the thread identifier obtained from the underlying query to determine if they are completely consistent. During this process, a consistency matching score parameter is introduced for auxiliary judgment. This score parameter is a weighted sum of character matching overlap (1), permission matching identifier (1), and path depth weight (0.2) calculated based on path hierarchy, resulting in a consistency matching score of 2.2. Since the preset consistency score judgment threshold is 2.0, the current result is in the range above the threshold, therefore the field item is deemed valid. By iteratively comparing all path items, all successfully verified field items are filtered out to obtain the path thread consistent field set.

[0066] S103: Based on the path thread consistent field set, for the field name, output path, permission status and plugin thread, match the field and plugin, associate the field name with the field path corresponding to the plugin identifier, and append the permission status to the corresponding field path information to obtain the plugin field mapping structure set;

[0067] First, each validated field in the set is accessed sequentially using an iterator to extract its corresponding field name, output path, permission status, and plugin thread identifier. Precise coupling matching between fields and plugins is performed. The plugin metadata table is queried using the plugin identifier to locate the plugin's logical name in the environment. The field name is used as a key-value pair, associated with the field path owned by its corresponding plugin identifier, and the permission status information of the field is converted into a specific permission descriptor and appended to the end of the field path information. This mapping logic is quantified using an association strength coefficient, which is determined by the product of field activity and permission level, plus a path uniqueness indicator, resulting in an association strength coefficient of 4.9. Experimental testing shows that the mapping structure achieves optimal stability when the association strength coefficient is between 4.5 and 5.5. By classifying and storing these associated data items according to plugin identifiers, the final plugin field mapping structure set is obtained.

[0068] Please see Figure 3 The specific steps of S2 are as follows:

[0069] S201: Based on the data of writable fields in the plugin field mapping structure set, extract the field name and field path, partition the plugin path, extract the field name under each path, assign the field name to the corresponding path set, and obtain the list of paths with repeated field names;

[0070] First, based on the data items in the plugin field mapping structure whose flags are writable, all read-only or write-prohibited fields are filtered out, retaining only the field names with write permissions and their corresponding physical output paths. The runtime status monitor is accessed to obtain the current runtime lifecycle status of each plugin, including initialization, running, suspended, and stopped states. Plugin paths are logically partitioned according to their runtime status. For each partition's path set, all field names covered under that path are deeply extracted. The extracted field names are allocated according to path affiliation and stored in the corresponding path resource pool. During this process, the partition load balance is calculated. The load balance is determined to be 5 based on the ratio of 100 total paths to 20 running plugins. This value is within the preset reasonable load range of 4 to 6. A cyclic deduplication operation is performed within the full path resource pool to identify identical field names appearing in different physical paths or different plugin paths. The path information with overlapping names is extracted to obtain a list of paths with duplicate field names.

[0071] S202: Based on the list of repeated paths with field names, read the field positions of any two paths in the set, extract the positioning order of the field names in the two paths, and bidirectionally match the path number and field position of the same field in the differentiated paths to obtain the matching list of path fields.

[0072] First, for each pair of fields with the same name recorded in the list, a random read function is used to obtain file pointers for any two paths to be tested in the set, locating the absolute byte offset position of the field in the file structure of each path. The file allocation table is parsed to extract the positioning order of the field name within the two different paths. Bidirectional matching logic is executed, comparing the field path number and field position in the first path with the corresponding item in the second path to record the arrangement characteristics of the fields with the same name in the differentiated path environment. During this process, the position alignment difference rate is calculated, which is obtained by dividing the absolute value of the difference in the field positioning order in the two paths by the total number of items in the path. The calculated position alignment difference rate is 0.3. Since this difference rate is lower than the preset significance threshold of 0.5, it indicates that the logical status of the fields is highly similar in different paths. By bidirectionally matching the path number and field position of the fields with the same name within the differentiated paths, a matching list of path fields is obtained.

[0073] S203: Based on the path name, field name and field position data in the matching list corresponding to the path field, match the path name corresponding to the field, merge the path numbers with the same field name into the same output sequence, and output the path sequence under each field name independently to obtain the field path overlapping matching data group.

[0074] First, based on the path names, field names, and precise field location data recorded in the matching list corresponding to the path field, a pairing and aggregation operation is performed on the field paths. For each item in the list, its corresponding globally unique path number is queried by path name. All path numbers with the exact same field name are grouped together and merged into the same output sequence buffer. This step is evaluated using a path overlap coefficient, which is determined by the ratio of path sequence length to the total number of paths. The calculated overlap coefficient is 0.1. Since this coefficient is greater than the judgment benchmark of 0.05, it indicates that the path overlap phenomenon of this field is significant. For each independent field name, a set of corresponding path sequences is output. The advantage of this operation is that it transforms spatial conflict relationships into serialized data, resulting in a set of field path overlap pairing data.

[0075] Please see Figure 4 The specific steps of S3 are as follows:

[0076] S301: Based on the path pair information in the field path overlap pairing data group, monitor the write timestamp sequence of the corresponding field in the path, compare the start time and end time of the field in the interval, identify path pairs with write intersection within the same time range, and obtain the path time window overlap comparison table.

[0077] First, based on the path pair information in the field path overlap pairing data group, a high-precision clock interface is invoked to monitor and record the timestamp sequence generated by the corresponding field in the path during the write operation in real time. For each path pair with possible overlap, an interval comparison operation is performed to retrieve the precise start and end times of the field write operation. During this process, the time overlap rate is calculated. The calculation logic is to obtain the intersection length of the two write intervals and divide it by the length of the total union of the two intervals, resulting in a time overlap rate of 0.33. A time conflict threshold of 0.1 is set. Since 0.33 is greater than 0.1, it is determined that the path pair has a write intersection on the time axis. By identifying path pairs with write intersections within the same time range, a path time window overlap reference table is obtained.

[0078] S302: Based on the path pairs in the path time window overlap comparison table, inspect the buffer channel number pointed to by the field, compare the corresponding channel number in the field of the path pair, extract the path pairs with the same channel number, and obtain the buffer channel consistent path table;

[0079] First, based on the path pairs in the path time window overlap lookup table, the physical buffer channel number pointed to by the monitored field is examined by accessing the hardware abstraction layer interface. An item comparison operation is performed to verify the consistency of the channel numbers requested by each field in the path pair. Channel consistency determination involves channel occupancy weight, which is calculated as the ratio of channel bandwidth demand to remaining available bandwidth. Assuming two paths point to the same channel and their sum of occupancy weights reaches 1.2, a physical channel conflict is determined when the total weight exceeds the load threshold of 1.0. By extracting path pairs with consistent channel numbers and overload characteristics, a buffer channel consistency path table is obtained.

[0080] S303: Based on the path pair information in the buffer channel consistent path table, parse the plug-in path identifier corresponding to the path, transfer the path pairs with time window intersection and the same channel number into the path group entries respectively, and convert them into number item columns to obtain the conflict path number mapping list.

[0081] First, based on the path pair information in the buffer channel consistent path table, the plugin path identifier code corresponding to each path is deeply analyzed, and the underlying logical business chain is obtained through reverse indexing. Path pairs with overlapping time windows and completely identical channel numbers are transferred to specific conflict path group entries. A data structure transformation operation is performed to convert complex path string descriptions into concise numeric number columns, thereby constructing a mapping relationship. The advantage of this process is that it reduces memory usage through digital encoding. For example, converting path strings into integer numbers improves processing efficiency. By converting path pair information into number column entries, a conflict path number mapping list is obtained.

[0082] Please see Figure 5 The specific steps of S4 are as follows:

[0083] S401: Based on the path number information in the conflict path number mapping list, read the field writing order data under the corresponding plugin path of the path number, check the field appearance order within the same path, distinguish the first appearance position and the second appearance position of the field, and obtain the path field appearance order comparison table.

[0084] First, based on the path number information in the conflict path number mapping list, the original data of the write order of all fields under the plugin path corresponding to the path number is read by accessing the file system log records. An order verification operation is performed, scanning the order of field appearances within a specific period within the same path, distinguishing between the first appearance and subsequent reappearance of a field in the path. During this process, an order stability coefficient is introduced, statistically analyzing the proportion of times a field's position remains unchanged within consecutive processing periods, resulting in a stability coefficient of 0.8. Since this coefficient is greater than the benchmark value of 0.75, the write order is determined to be regular. By verifying the field appearance order within the same path, a path field appearance order lookup table is obtained.

[0085] S402: Based on the path field occurrence order lookup table, detect the writing order of repeated fields in the same path, perform a delay adjustment action on the writing order of repeated fields, and synchronously write the delay mark into the field control information entry to obtain the field delay writing status set.

[0086] First, based on the path field occurrence order lookup table, the timing analysis module detects the write order index corresponding to the fields that appear repeatedly within the same path. For the identified repeated fields, a delay adjustment is performed. By modifying the priority parameter of the scheduling algorithm, the repeated write order is shifted backward by a preset fine-tuning pulse width on the time axis. The delay time is set based on a delay compensation factor, which is calculated by multiplying the average path response time by the conflict frequency to obtain a conflict intensity coefficient. This coefficient is then converted into a delay time by combining it with the fine-tuning conversion ratio set by the system. In this embodiment, the final calculated delay time is 20 microseconds. The original write time is increased by 20 microseconds to obtain the new write time. Simultaneously, the delay flag is written into the field control information entry, resulting in a set of field delayed write states.

[0087] S403: Based on the set of delayed write statuses of fields, the corresponding associated path number, field name and delayed status information are written into the field control data entry to obtain the field write control status table.

[0088] First, using a data association engine, the affected fields are multi-dimensionally bound to their associated path numbers, field names, and the latest delayed status information. An information synchronization operation is then performed, uniformly writing the adjusted field writing order information and delayed status attributes into the field control data entries. The effectiveness of this status table is evaluated using the conflict resolution rate, calculated by subtracting the proportion of collisions that still occur after adjustment from 1, resulting in a conflict resolution rate of 0.98. Compared to the unadjusted rate of 0.45, the conflict resolution rate has increased by 117.8%. By uniformly writing the field writing order and delayed status information, the field writing control status table is obtained.

[0089] Please see Figure 6 The specific steps of S5 are as follows:

[0090] S501: Based on the field set in the delayed state of the field writing control status table, extract the plug-in identifier and function block name corresponding to the field, associate it with the preset plug-in function structure table, obtain the corresponding function block name, and map the fields into the field set in sequence according to the plug-in and function block information. During the mapping process, exclude data items with inconsistent field numbers to obtain the field classification dataset.

[0091] First, based on the set of fields in the delayed state written to the control status table, a classifier is used to extract the unique plug-in identifier and the logical name of the corresponding functional block for each field. A mapping algorithm is then used to map the fields sequentially into the global field set according to the plug-in and functional block hierarchy. During the mapping process, a consistency filter check is performed to exclude all abnormal data items whose field numbers do not match the records in the control table. Descriptor dissimilarity is introduced into the classification process for auxiliary discrimination. This dissimilarity is calculated by proportionally dividing the Hamming distance between functional block descriptors by the total number of bits; a lower ratio indicates greater similarity. In this embodiment, the calculated dissimilarity is 0.03125, indicating a high matching degree, thus it is classified as a highly similar category and grouped into the same class. By excluding inconsistent data during the mapping process, a field classification dataset is obtained.

[0092] S502: Based on the field set in the field classification dataset, retrieve the field occurrence order in the corresponding path, extract the field fragments that are adjacent to each other in the path and include write actions, and divide the field fragments into segments according to the path number to obtain the field path fragment set;

[0093] First, based on the field set in the field classification dataset, the real-time occurrence order of fields in the corresponding path is retrieved through a tracing program. Field fragments that are adjacent to each other in the physical space of the path and contain write operations are extracted. The segment length is determined by the transaction atomicity threshold, which is set based on the ratio of the maximum number of bytes the buffer can hold to the average size of a single field, resulting in a segment length of 8 fields. These field fragments are then sequentially segmented according to the logical order of the path numbers. Each fragment represents a minimum, indivisible unit of write transaction. This segmentation process allows for finer-grained monitoring of write behavior, resulting in a set of field path fragments.

[0094] S503: Based on the behavior status, path number and control information of the fields in the field path fragment set, extract the control status of the fields in the path, update the field status label content according to the write behavior status, and obtain the monitoring field processing status list.

[0095] First, based on the behavior status, path number, and detailed control information of the fields in the field path fragment set, the real-time control status of each field in the path is extracted by the parsing engine. According to the captured write behavior trigger signal, the field status annotation is dynamically updated, changing the field status from pending execution to completed or delayed execution. The update of the processing status is verified using a state transition determinism coefficient. The coefficient is calculated as 0.9999 by dividing the number of successful transitions by the total number of attempts. Experimental results show that the scheme has extremely high stability. Finally, all processed status information is integrated to obtain a list of monitored field processing statuses.

[0096] Please see Figure 7 A plugin-based real-time data backend monitoring and processing system includes:

[0097] Plugin field mapping module: Obtain the identifier of the active plugin thread, parse the field output content corresponding to the plugin thread, extract the field name, field output path and backend writable status, the corresponding fields and plugin thread functional behaviors, and obtain the plugin field mapping structure set;

[0098] Path field pairing module: Based on the field name and path information of writable fields in the plugin field mapping structure set, compare the plugin path field names, identify path pairs with overlapping names and pair the fields to obtain a data group of overlapping field paths.

[0099] Conflict path identification module: Based on the path information in the data group with overlapping field paths, it supplements and extracts the buffer channel identifier corresponding to the field, judges the time window overlap status of the field writing behavior and compares the consistency of the buffer channel, separates the conflict path, and obtains the conflict path number mapping list.

[0100] Write status control module: Based on the path number in the conflict path number mapping list, read the field order in the path, perform write delay processing on duplicate fields, and update the field write status to obtain the field write control status table.

[0101] Monitoring status output module: Based on the information of the delayed status fields written into the control status table, it classifies by plug-in and function block, checks the consistency of the field order structure, and obtains the monitoring field processing status list according to the field behavior status, path number and control information mapping status action.

[0102] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A plugin-based real-time data backend monitoring and processing method, characterized in that, Includes the following steps: S1: Obtain the identifier of the currently active plugin thread, parse the field output content corresponding to each plugin thread, extract the field name, field output path and backend write permission status, match the field output path according to the plugin thread, and map the fields to the plugin to obtain the plugin field mapping structure set. S2: Based on the field name and path information of the writable fields in the plugin field mapping structure set, perform field matching on the plugin path in the running state, identify the plugin path pairs with overlapping names by comparing field names, match each pair of field path pairs, and obtain the field path overlapping pairing data group. S3: Based on the path pair information in the field path overlap pairing data group, compare the writing behavior time window overlap status of the corresponding field in the path, compare the consistency of the buffer channel pointed to by the field, and after identifying the path pair that has both time window overlap relationship and buffer channel consistency, separate the conflicting path and obtain the conflicting path number mapping list. S4: Based on the path number recorded in the conflict path number mapping list, write the field order of each path corresponding to the number, locate the first occurrence of the field order in the path, perform write delay processing on duplicate fields in the path, and update the field write status to obtain the field write control status table. S5: Based on the set of fields in the delayed state of the field writing control status table, classify them according to the plug-in information and function block identifier of the field, check the consistency of the order structure of each group of fields after classification, identify the field sequence that is continuously arranged in the same path and has writing behavior, and obtain the monitoring field processing status list according to the field behavior status, path number and control information mapping status action.

2. The data background real-time monitoring and processing method based on plug-ins according to claim 1, characterized in that, The plugin field mapping structure set includes field name, field output path, and backend write permission status. The field path overlap pairing data group includes field name overlap path pairs, field name corresponding to each path group, and mapping relationship between field paths. The conflict path number mapping list includes path number, field write time window overlap identifier, and buffer channel consistency identifier. The field write control status table includes field order, field write delay status, and field path number. The monitoring field processing status list includes plugin information to which the field belongs, function block identifier, field sequence structure consistency status, field behavior status, and control information mapping result.

3. The real-time data background monitoring and processing method based on plug-ins according to claim 1, characterized in that, The field output content corresponding to the plugin thread refers to the original data set mapped by the monitoring system fields; The field writing behavior refers to the process of detecting conflicts in the timing and path of field writing.

4. The real-time data background monitoring and processing method based on plug-ins according to claim 1, characterized in that, The updated field write status refers to eliminating write conflicts and marking the field status through a delayed processing mechanism; The mapping state action refers to the process of mapping field behavior with control policies to generate monitoring and processing status.

5. The real-time data background monitoring and processing method based on plug-ins according to claim 1, characterized in that, The specific steps of S1 are as follows: S101: Obtain the identifier of the currently active plugin thread, monitor the data output content corresponding to each plugin thread, extract the field name, field output path and backend write permission status, corresponding field name and source plugin thread, and append the field output path and permission status to the corresponding field item to obtain the initial associated content of the field information. S102: Based on the initial associated content of the field information, extract the correspondence between the field output path and the plugin thread, compare the thread source corresponding to the field path with the plugin thread identifier in the field output path set, and obtain the path thread consistent field set; S103: Based on the path thread consistent field set, for the field's corresponding name, output path, permission status and plugin thread, match the field with the plugin, associate the field name with the field path corresponding to the plugin identifier, and append the permission status to the corresponding field path information to obtain the plugin field mapping structure set.

6. The data background real-time monitoring and processing method based on plug-ins according to claim 1, characterized in that, The specific steps of S2 are as follows: S201: Based on the data of writable fields in the plugin field mapping structure set, extract the field name and field path, partition the plugin path, extract the field name under each path, assign the field name to the corresponding path set, and obtain a list of paths with repeated field names; S202: Based on the list of repeated paths for the field name, read the field position of any two paths in the set, extract the positioning order of the field name in the two paths, and bidirectionally match the path number and field position of the same field in the differentiated path to obtain the matching list of the path field. S203: Based on the path name, field name and field position data in the matching list corresponding to the path field, match the path name corresponding to the field, merge the path numbers with the same field name into the same output sequence, and output the path sequence under each field name independently to obtain the field path overlapping pairing data group.

7. The real-time data background monitoring and processing method based on plug-ins according to claim 1, characterized in that, The specific steps for S3 are as follows: S301: Based on the path pair information in the field path overlap pairing data group, monitor the write timestamp sequence of the corresponding field in the path, compare the start time and end time of the field in the interval, identify path pairs with write intersection within the same time range, and obtain the path time window overlap comparison table. S302: Based on the path pairs in the path time window overlap comparison table, inspect the buffer channel number pointed to by the field, compare the corresponding channel number in the field of the path pair, extract the path pairs with the same channel number, and obtain the buffer channel consistent path table. S303: Based on the path pair information in the buffer channel consistent path table, parse the plug-in path identifier corresponding to the path, transfer the path pairs with time window intersection and the same channel number into the path group entries respectively, and convert them into number item columns to obtain the conflict path number mapping list.

8. The data background real-time monitoring and processing method based on plug-ins according to claim 1, characterized in that, The specific steps of S4 are as follows: S401: Based on the path number information in the conflict path number mapping list, read the field writing order data under the corresponding plugin path of the path number, check the field appearance order within the same path, distinguish the first appearance position and the second appearance position of the field, and obtain the path field appearance order comparison table. S402: Based on the path field occurrence order lookup table, detect the writing order of repeated fields in the same path, perform a delay adjustment action on the writing order of repeated fields, and synchronously write the delay mark into the field control information entry to obtain the field delay writing status set. S403: Based on the set of delayed write statuses of the fields, the corresponding associated path number, field name and delayed status information are written into the field control data entry to obtain the field write control status table.

9. The real-time data background monitoring and processing method based on plug-ins according to claim 1, characterized in that, The specific steps of S5 are as follows: S501: Based on the field written to the control status table, the set of fields in the delayed state is extracted, the plug-in identifier and function block name corresponding to the field are extracted, and the preset plug-in function structure table is associated to obtain the corresponding function block name. The fields are mapped into the field set in sequence according to the plug-in and function block information. During the mapping process, data items with inconsistent field numbers are excluded to obtain the field classification dataset. S502: Based on the field set in the field classification dataset, retrieve the field occurrence order in the corresponding path, extract the field fragments that are adjacent to each other in the path and include write actions, and divide the field fragments into segments according to the path number to obtain the field path fragment set; S503: Based on the behavior status, path number and control information of the fields in the field path fragment set, extract the control status of the fields in the path, update the field status label content according to the writing behavior status, and obtain the monitoring field processing status list.

10. A plug-in-based real-time data backend monitoring and processing system, characterized in that, The system is used to implement the plug-in-based real-time data background monitoring and processing method according to any one of claims 1-9, the system comprising: Plugin field mapping module: Obtain the identifier of the active plugin thread, parse the field output content corresponding to the plugin thread, extract the field name, field output path and backend writable status, the corresponding fields and plugin thread functional behaviors, and obtain the plugin field mapping structure set; Path field pairing module: Based on the field name and path information of the writable fields in the plugin field mapping structure set, compare the plugin path field names, identify path pairs with overlapping names and pair the fields to obtain a field path overlapping pairing data group. Conflict path identification module: Based on the path information in the field path overlapping pairing data group, supplement and extract the buffer channel identifier corresponding to the field, determine the time window overlap status of the field writing behavior and compare the consistency of the buffer channel, separate the conflict path, and obtain the conflict path number mapping list. Write status control module: Based on the path number in the conflict path number mapping list, read the field order in the path, perform write delay processing on duplicate fields, and update the field write status to obtain the field write control status table. Monitoring status output module: Based on the information of the delayed status field written into the control status table, the module classifies the fields by plug-in and function block, checks the consistency of the field order structure, and obtains the monitoring field processing status list according to the field behavior status, path number and control information mapping status action.

Images