Message track enhancement method and system

Abstract

The invention discloses a message track enhancement method and system. The method comprises the following steps: configuring an area identifier of a message middleware service as a non-default value, and starting a track data reporting switch, so that a production end and a consumption end report message track data to a specified theme; dynamically generating a trajectory data query theme based on the current region identifier, wherein the trajectory data query theme comprises at least one of a system-defined theme prefix, a trajectory data identifier and a region identifier; and querying theme retrieval message trajectory data according to the trajectory data, and analyzing the retrieval message trajectory data to obtain a producer network address, a consumer network address, a consumption time range and a consumption time consumption index. The technical problem that effective monitoring cannot be carried out due to the fact that track data cannot be accurately reported in an under-line environment in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of computers, and in particular to a message trajectory enhancement method and system. Background Art

[0002] With the continuous development of information technology, message middleware has been widely used in distributed systems to achieve reliable message delivery and efficient processing. Messages transmitted between the production end and the consumer end usually have complex processing flows. Therefore, how to effectively track and analyze the trajectory of messages has become an urgent problem to be solved in optimizing system performance, improving data transparency and monitoring capabilities.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present invention provide a message track enhancement method and system to at least solve the technical problem in the prior art that offline environments fail to accurately report track data, resulting in inability to perform effective monitoring.

[0005] According to one aspect of an embodiment of the present invention, a message trace enhancement method is provided, comprising: configuring a regional identifier of a message middleware service to be a non-default value, and enabling a trace data reporting switch so that a production end and a consumer end report message trace data to a specified topic; dynamically generating a trace data query topic based on a current regional identifier, wherein the trace data query topic comprises at least one of the following: a system-defined topic prefix, a trace data identifier, and a regional identifier; retrieving message trace data according to the trace data query topic, and parsing the retrieved message trace data to obtain a producer network address, a consumer network address, a consumption time range, and a consumption time indicator.

[0006] According to another aspect of an embodiment of the present invention, a message trace enhancement system is provided, including: a configuration management module, used to configure the regional identifier of the message middleware service to a non-default value, and enable the trace data reporting switch, so that the production end and the consumer end report the message trace data to the specified topic; a topic generation module, used to dynamically generate a trace data query topic based on the current regional identifier, and the trace data query topic includes at least one of the following: a system-defined topic prefix, a trace data identifier, and a regional identifier; a console interaction module, used to retrieve message trace data according to the trace data query topic, and parse the retrieved message trace data to obtain the producer network address, the consumer network address, the consumption time range and the consumption time indicator.

[0007] In an embodiment of the present invention, the regional identifier of the message middleware service is configured to be non-default, and the track data reporting switch is enabled, so that the production end and the consumer end report the message track data to the specified topic; based on the current regional identifier, a track data query topic is dynamically generated, and the track data query topic includes at least one of the following: a system-defined topic prefix, a track data identifier, and a regional identifier; according to the track data query topic, the message track data is retrieved, and the retrieved message track data is parsed to obtain the producer network address, the consumer network address, the consumption time range, and the consumption time consumption index. The above scheme solves the problem of the offline environment failing to accurately report track data in the prior art, resulting in the inability to perform effective monitoring technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0009] Figure 1 is a flow chart of an optional message track enhancement method according to an embodiment of the present invention;

[0010] Figure 2 It is to view the interface diagram according to the message track of the prior art;

[0011] Figure 3 It is an error reporting interface diagram according to the prior art;

[0012] Figure 4 This is a flow chart of a method for adding a message track to the RocketMQ open source version according to an embodiment of the present invention;

[0013] Figure 5 is a flow chart of an optional data reporting method according to an embodiment of the present invention;

[0014] Figure 6 This is an interface diagram for adding a regionId configuration item in an optional configuration according to an embodiment of the present invention;

[0015] Figure 7 is a schematic diagram of a code for modifying a topic name of a query according to an embodiment of the present invention;

[0016] Figure 8 is an interface diagram for displaying detailed information of a message track according to an embodiment of the present invention;

[0017] Fig. 9 is a flow chart of another message trajectory enhancement method according to an embodiment of the present invention;

[0018] Fig.10is a schematic structural diagram of an optional message trace enhancement device according to an embodiment of the present invention;

[0019] Fig.11 A schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0021] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0022] According to an embodiment of the present invention, a method embodiment of a message track enhancement method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0023] Figure 1 This is a flow chart of a message track enhancement method according to an embodiment of the present invention. This embodiment improves the message track reporting mechanism to ensure that message track data can be accurately reported in different environments; optimizes the console display to provide more user-friendly prompts and more comprehensive data display; and is compatible with the topic differences between the commercial version and the open source version through the modified data query logic.

[0024] Specifically, Figure 1 As shown, the message track enhancement method includes the following steps:

[0025] Step S102, configuring the regional identifier of the message middleware service to a non-default value, and enabling the track data reporting switch, so that the production end and the consumer end report the message track data to the specified topic.

[0026] A regional identifier such as RegionId is a unique code used to identify the logical or physical partition where the message middleware service is located, such as a data center ID, an availability zone identifier, or a custom logical grouping label. A trace data reporting switch such as MsgTraceSwitch is a configuration parameter that controls whether the producer and consumer report message trace data, usually a Boolean variable (on / off). A designated topic is a pre-defined or dynamically generated dedicated storage topic in the message middleware, which is used to centrally store message trace data.

[0027] In this embodiment, a region identifier field is defined in a message middleware configuration file, and a preset logical partition identifier is injected through a configuration management service, wherein the logical partition identifier is associated with a physical or logical topology of a deployment environment.

[0028] This embodiment avoids the mixing of message trajectory data in cross-region scenarios by explicitly configuring the region identifier as a non-default value, and achieves precise isolation of physical or logical partitions. At the same time, enabling the trajectory data reporting switch can flexibly control the data collection scope and reduce the resource consumption of redundant data reporting. In addition, combined with the configuration management service to dynamically inject logical partition identifiers, it can seamlessly adapt to complex deployment environments such as hybrid cloud and multi-active architecture, and improve system scalability.

[0029] Step S104: dynamically generate a trajectory data query subject based on the current region identifier, wherein the trajectory data query subject includes at least one of the following: a system-defined subject prefix, a trajectory data identifier, and a region identifier.

[0030] For example, the configuration of the current area identifier is automatically loaded; based on the configuration of the current area identifier, a topic is constructed through string processing logic, so that the constructed topic matches the trajectory data topic reported by the message middleware service to generate the trajectory data query topic.

[0031] This embodiment dynamically generates query topics by coupling regional identifiers to ensure that data query paths in different regions are naturally isolated, avoiding the risk of data contamination during cross-regional retrieval. In addition, the topic naming rules are automatically adapted through string processing logic, eliminating the need to manually maintain multiple sets of query templates, reducing the complexity of operation and maintenance.

[0032] Step S106, searching message trajectory data according to the trajectory data query subject, and parsing the searched message trajectory data to obtain the producer network address, consumer network address, consumption time range and consumption time index.

[0033] The producer network address and consumer network address fields are extracted from the retrieved message trajectory data, and the consumption time range and consumption time are calculated based on the timestamp sequence. Afterwards, the producer network address, consumer network address, consumption time range and consumption time indicators are rendered in a structured form to the console interaction interface, and after receiving the filtering instruction, filtering operations can be performed based on time or network address. Finally, verify whether the trajectory data reporting switch status and the area identifier configuration meet the data reporting conditions; if it is detected that the current area identifier is the default value or the trajectory data reporting switch is in the off state, a highlighted alarm is triggered in the interactive interface, and the associated configuration repair instructions are configured.

[0034] In this embodiment, by parsing the network address fields of producers and consumers, abnormal communication nodes across services or regions can be quickly located to assist in root cause analysis of faults. In addition, this embodiment avoids data omissions or false positives due to configuration errors through an automated verification mechanism, such as cross-region data pollution caused by unupdated regional identifiers. The linkage design of highlighted alarms and repair instructions shortens the mean time to repair (MTTR) of configuration anomalies and ensures the reliability of the trajectory collection system. The strong correlation between alarm rules and configuration conditions can be extended to other operation and maintenance scenarios, such as security policy compliance checks.

[0035] In actual applications, both the open source version and the commercial version of RocketMQ are widely used. Among them, the open source version is deployed in the offline environment, while the commercial version is used in the production environment. The console module of the open source version is used to view monitoring data. However, in the open source version 4.9.2 of RocketMQ, the message track display function has obvious deficiencies. Specifically, the default topic configured on the console side does not match the actual report, resulting in the inability to view the track data. In addition, the console of the open source version lacks friendly user prompts in abnormal situations, so that when viewing the message track, the user interface is displayed as empty, and the console error information is unclear.

[0036] Therefore, when viewing the message trace through the console, it is displayed as empty, such as Figure 2 As shown in the figure. Since the open source version of the console does not provide friendly prompts for abnormalities, check the console and the error is as follows Figure 3 shown.

[0037] At the same time, in use, the SDK mainly uses the commercial version, rather than using different SDKs for different environments, so as to avoid the need to switch SDKs between different environments, which increases the difficulty of maintenance and may also cause problems due to logical differences and compatibility. If the commercial version of the SDK is not configured with regionId on the broker side (that is, using the default regionId, defaultRegion), neither the sender nor the consumer will upload trajectory data.

[0038] Compared with the commercial version, the open source RocketMQ lacks some key functions and is not as timely in terms of maintenance and repair as the commercial version. Moreover, under the current configuration, the offline environment fails to report trajectory data, resulting in the inability to conduct effective monitoring and troubleshooting. In addition, the console cannot view key data such as producer IP, consumer IP, number of consumers, consumption start time, and consumption duration, which increases the complexity of developers during the development and debugging process.

[0039] In order to solve the above problems, the present invention provides a method for increasing message traces in RocketMQ open source version, such as Figure 4 As shown, the method includes:

[0040] Step S402: data reporting.

[0041] Ensure that MsgTraceSwitch is set to true in each service configuration, or use the default value of true. At the same time, assign a non-default value to the regionId in the Broker configuration file to ensure that the message trace data is correctly reported.

[0042] like Figure 5 As shown, the data reported includes:

[0043] 1) Reported by the producer.

[0044] from Figure 5 As you can see, to confirm the reporting of message trace data, the following configuration is required: in each service configuration, set MsgTraceSwitch to true, or do not set it to the default value of true; in the Broker configuration file, set regionId to a non-default value. In this embodiment, add a regionId configuration item in the configuration, such as Figure 6 shown.

[0045] 2) Consumer reports.

[0046] The consumer reporting logic is similar to that of the producer and will not be repeated here.

[0047] Step S404, data query.

[0048] Since the trajectory data topic used by RocketMQ is different from the open source version, the present invention has modified the query logic and ensured the accuracy of data query by fixing the topic to OnsTraceConstants.traceTopic+currentRegionId.

[0049] Since the topic of the trajectory data reported by RocketMQ is different from the open source version, the query also needs to be modified. Fix the topic to

[0050] OnsTraceConstants.traceTopic+currentRegionId=

[0051] MixAll.SYSTEM_TOPIC_PREFIX+"TRACE_DATA_"+currentRegionId=

[0052] "rmq_sys_"+"TRACE_DATA_"+currentRegionId=

[0053] "rmq_sys_TRACE_DATA_"+currentRegionId.

[0054] In this embodiment, modify the query topic name such as Figure 7 As shown, the effect is Figure 8 shown.

[0055] The method provided in this embodiment improves the visualization and observability of message traces, making it easier for developers to monitor and troubleshoot problems; through a unified configuration and reporting mechanism, it simplifies SDK switching and maintenance work in different environments. By enhancing the robustness of the system, compatibility issues caused by environmental differences are reduced.

[0056] Fig. 9 This is a flow chart of another message track enhancement method according to an embodiment of the present invention. This embodiment solves the defects of the open source version of RocketMQ in the message track function by optimizing the message track reporting mechanism, dynamically adapting the query subject, and enhancing the data analysis and alarm capabilities, and achieves cross-environment compatibility and high observability. Fig. 9 As shown, the method comprises the following steps:

[0057] Step S902: configure the area identifier and enable the trajectory data reporting switch.

[0058] 1) Define and configure the region identifier (regionId).

[0059] The region identifier (regionId) is a unique code used to identify the logical or physical partition where the message middleware service is located. It includes physical partitions (such as data center ID DC1 or availability zone identifier AZ-A) and logical partitions (such as custom environment label DEV or business group OrderService). At the configuration level, two methods are supported: static configuration file injection and dynamic configuration management. Static configuration modifies the configuration file (broker.conf) of RocketMQ Broker, explicitly defines the regionId field and assigns a non-default value (for example, regionId = PROD_GROUP_A). Dynamic configuration relies on an integrated configuration center (such as Nacos or Apollo) to update the regionId value in real time by listening to configuration changes, such as automatically pulling a new regionId and triggering a Broker restart when the environment is switched. By forcing the regionId to be a non-default value, the trajectory data of different partitions is naturally isolated when stored, avoiding data overwriting or mixing due to conflicts in default values.

[0060] 2) Enable the trace data reporting switch (MsgTraceSwitch).

[0061] MsgTraceSwitch is a Boolean switch that controls whether the producer and consumer report message traces. The default value is true. Its configuration is divided into global level and client level. The global configuration turns on the switch uniformly on the Broker side, forcing all clients to inherit this setting; the client-level configuration allows producers and consumers to independently override global rules (for example, temporarily turning off reporting in a test environment to reduce resource consumption). In implementation, the producer checks the switch status before sending a message: if the switch is enabled, the trace data (including message ID, sending timestamp, etc.) is constructed and sent to the specified Topic. By flexibly controlling the reporting switch, the data collection scope can be adjusted as needed in different environments to reduce the impact of redundant data on system performance.

[0062] 3) Report data storage rules.

[0063] The storage topic of the trace data is dynamically generated based on the regionId, and the naming rule is the concatenation of the system topic prefix (such as rmq_sys_), the trace data identifier (TRACE_DATA_) and the current regionId. For example, when regionId = PROD, the final topic name is rmq_sys_TRACE_DATA_PROD. Different regionIds correspond to independent storage topics to ensure data isolation at the physical level and avoid data pollution caused by topic mixing during cross-region queries.

[0064] Through the above method, it is ensured that the production and consumption ends accurately report message trajectory data within the specified logical partition, avoiding cross-regional data mixing.

[0065] Step S904: dynamically generate a trajectory data query subject.

[0066] 1) Determine the query subject generation rules.

[0067] The generation of query topics depends on three core elements: the system-defined topic prefix, the trace data identifier, and the current regionId. The system topic prefix is ​​a fixed value (such as rmq_sys_), the trace data identifier is the constant string TRACE_DATA_, and the regionId is obtained in real time from the Broker configuration or environment variables. The complete Topic name is dynamically generated through string concatenation logic, for example, in the code, it is implemented by MixAll.SYSTEM_TOPIC_PREFIX+"TRACE_DATA_"+currentRegionId. In this way, hard-coded Topic names are avoided, automatic adaptation of multiple environments is supported, and the query path is strictly consistent with the data storage path.

[0068] 2) Query request routing and exception handling.

[0069] The console automatically routes query requests to the corresponding Topic based on the current user's regionId. If the query Topic does not exist (for example, the regionId configuration is incorrect), the system will record an error log (such as "Topic[rmq_sys_TRACE_DATA_DEV] not found") and return a prompt message in the console (such as "Trajectory data is not found in the current region, please check the regionId configuration"). This effectively avoids query failures caused by configuration errors, while providing clear repair instructions to shorten troubleshooting time.

[0070] Through the above method, the topic differences between the open source version and the commercial version of RocketMQ are compatible, and seamless adaptation of cross-environment data queries is achieved.

[0071] Step S906, retrieving, parsing and displaying the message trajectory data.

[0072] 1) Data retrieval and analysis.

[0073] Data retrieval supports filtering by time range, producer IP, consumer IP and other fields. The original data is stored in the message body in JSON format. When parsing, key fields (such as producer IP, message ID, send timestamp, consumer IP, consumption timestamp, etc.) need to be extracted. The consumption duration is obtained by calculating the difference between the send timestamp and the consumption timestamp (duration = consumeTimestamp-sendTimestamp). The parsed data is stored in an in-memory database (such as Redis) or a file system, supporting fast retrieval and aggregate analysis.

[0074] 2) Enhance console visualization.

[0075] The console interface is divided into a list view and a details panel. The list view displays core fields (such as producer IP, consumer IP, message status, time consumption, etc.), and supports sorting by time or IP search. The details panel provides extended information (such as message content, track timeline, and associated logs) to help developers quickly locate problems. The time range selector allows custom query windows, and the IP search box supports accurate filtering of track records for specific nodes.

[0076] 3) Anomaly detection and alarm linkage.

[0077] The system periodically scans the regionId and MsgTraceSwitch configurations of all Brokers. If the regionId is detected to be the default value (DefaultRegion) or MsgTraceSwitch is closed, the console homepage will trigger a highlighted alarm (such as a red banner prompting "RegionId is not configured or MsgTraceSwitch is closed, trace data may be lost!"), with a jump link to the configuration management page. Through active detection and visual alarms, the mean time to repair (MTTR) of configuration anomalies can be shortened by more than 60%, significantly improving system reliability.

[0078] In some other embodiments, regionId and MsgTraceSwitch can be hosted in a configuration center (such as Nacos) to achieve grayscale release and rollback through version control. For example, after the configuration center releases a new regionId, Broker automatically pulls and applies the changes without manually modifying the configuration file. In this way, the error rate of manual operation can be reduced and the consistency of multiple environments can be improved.

[0079] In some other embodiments, an AI operation and maintenance engine can be integrated to automatically analyze the cause of configuration anomalies and execute repair scripts. For example, when the regionId is detected to be the default value, the engine automatically restores the valid value from the historical record or calls the API to reset the configuration. In this way, MTTR can be further shortened and unattended operation and maintenance can be achieved.

[0080] This embodiment significantly improves the completeness and usability of the message tracking function of RocketMQ open source version through three core improvements: refined configuration management, dynamic topic adaptation, and intelligent alarm. The technical solution takes into account flexibility and reliability, and provides efficient technical support for complex scenarios such as hybrid cloud and multi-active architecture.

[0081] The present application also provides a message track enhancement system, such as Fig.10 As shown, it includes: a configuration management module 12, which is used to configure the regional identifier of the message middleware service to a non-default value, and enable the trajectory data reporting switch so that the production end and the consumer end report the message trajectory data to the specified topic; a topic generation module 14, which is used to dynamically generate a trajectory data query topic based on the current regional identifier, and the trajectory data query topic includes at least one of the following: a system-defined topic prefix, a trajectory data identifier, and a regional identifier; a console interaction module 16, which is used to retrieve the message trajectory data according to the trajectory data query topic, and parse the retrieved message trajectory data to obtain the producer network address, the consumer network address, the consumption time range and the consumption time indicator.

[0082] It should be noted that the message track enhancement system provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the message track enhancement system provided in the above embodiment and the message track enhancement method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0083] Fig.11 FIG. 1 shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiment of the present disclosure. It should be noted that: Fig.11 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0084] like Fig.11 As shown, the electronic device includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 into a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for system operation are also stored. The CPU 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0085] The following components are connected to the I / O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage section 1008 as needed.

[0086] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A message trajectory enhancement method, characterized in that: include: Configure the regional identifier of the message middleware service to a non-default value and enable the trace data reporting switch so that the producer and consumer ends report message trace data to the specified topic; dynamically generating a trajectory data query subject based on the current region identifier, the trajectory data query subject comprising at least one of: a system-defined subject prefix, a trajectory data identifier, and a region identifier; The message trajectory data is retrieved according to the trajectory data query subject, and the retrieved message trajectory data is parsed to obtain the producer network address, the consumer network address, the consumption time range and the consumption time consumption index.

2. The method according to claim 1, characterized in that Configuring a region identifier of a message middleware service to be a non-default value includes: defining a region identifier field in a message middleware configuration file, and injecting a preset logical partition identifier through a configuration management service, wherein the logical partition identifier is associated with a physical or logical topology of a deployment environment.

3. The method according to claim 1, characterized in that Dynamically generate trajectory data based on the current region identifier. Query topics include: Automatically loading the configuration of the current zone identifier; Based on the configuration of the current area identifier, a topic is constructed through string processing logic, so that the constructed topic matches the trajectory data topic reported by the message middleware service, so as to generate the trajectory data query topic.

4. The method according to claim 1, characterized in that: The search message trace data is parsed, including: extracting producer network address and consumer network address fields from the search message trace data, and calculating consumption time range and consumption time according to a timestamp sequence.

5. The method according to claim 4, characterized in that After parsing the retrieved message trajectory data, the method further includes: rendering the producer network address, consumer network address, consumption time range and consumption time index in a structured form to the console interaction interface, and after receiving a filtering instruction, being able to perform filtering operations based on time or network address.

6. The method according to claim 1, characterized in that After parsing the retrieved message trace data, the method further includes: Verify whether the trajectory data reporting switch status and area identifier configuration meet the data reporting conditions; If it is detected that the current area identifier is a default value or the trajectory data reporting switch is in the off state, a highlighted alarm is triggered in the interactive interface, and associated configuration repair instructions are provided.

7. A message track enhancement system, characterized in that: include: The configuration management module is used to configure the regional identifier of the message middleware service to a non-default value and enable the track data reporting switch so that the producer and consumer ends report the message track data to the specified topic; a topic generation module, configured to dynamically generate a trajectory data query topic based on a current region identifier, wherein the trajectory data query topic includes at least one of the following: a system-defined topic prefix, a trajectory data identifier, and a region identifier; The console interaction module is used to retrieve message trajectory data according to the trajectory data query topic, and parse the retrieved message trajectory data to obtain the producer network address, consumer network address, consumption time range and consumption time consumption index.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 6.

9. A computer device, characterized in that: include: Memory and processor, The memory stores a computer program; The processor is used to execute the computer program stored in the memory, and when the computer program is run, the processor is enabled to execute the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images