Automatic message distribution method and device for scientific education

Abstract

The invention discloses an automatic message distribution method and device for scientific education. The method comprises the following steps: determining a message distribution scene based on at least one of the following: an environment type of a current deployment environment, a message type of a to-be-sent message, and token configuration information; and pushing the to-be-sent message to a corresponding message group based on the determined message distribution scene. According to the invention, the technical problem that the group to which the message to be sent arrives is inaccurate in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of science education, and more particularly, to a method and apparatus for automatically distributing messages for science education. Background Art

[0002] In the existing field of science education, message automatic distribution systems are widely used in information transmission and teaching management. However, the existing message distribution systems usually face the following problems: the recipient groups of messages are not precise enough, resulting in the inability to efficiently convey information to specific groups that need to receive it. Specifically, message distribution in the prior art often relies on simple preset conditions or unified group settings and cannot dynamically adjust the distribution objects according to different environments or message contents. This method not only wastes resources but also may lead to the recipient groups of messages being too large or too small, thus affecting the effect and efficiency of information transmission.

[0003] In view of the above problems, no effective solution has been proposed yet. Summary of the Invention

[0004] Embodiments of the present invention provide a method and apparatus for automatically distributing messages for science education to at least solve the technical problem of inaccurate groups reached by messages to be sent in the prior art.

[0005] According to one aspect of the embodiments of the present invention, there is provided a method for automatically distributing messages for science education, including: determining a message distribution scenario based on at least one of the following: the environmental type of the current deployment environment, the message type of the message to be sent, and token configuration information; and pushing the message to be sent into a corresponding message group based on the determined message distribution scenario.

[0006] According to another aspect of the embodiments of the present invention, there is also provided an apparatus for automatically distributing messages for science education, including: a determining module configured to determine a message distribution scenario based on at least one of the following: the environmental type of the current deployment environment, the message type of the message to be sent, and token configuration information; and a pushing module configured to push the message to be sent into a corresponding message group based on the determined message distribution scenario.

[0007] In the embodiments of the present invention, a message distribution scenario is determined based on at least one of the following: the environmental type of the current deployment environment, the message type of the message to be sent, and token configuration information; and the message to be sent is pushed into a corresponding message group based on the determined message distribution scenario. Through the above solution, the technical problem of inaccurate groups reached by messages to be sent in the prior art is solved. Brief Description of the Drawings

[0008] The accompanying drawings described herein are used to provide a further understanding of the present invention and form a part of this application. The schematic 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 flowchart of a method for automatically distributing messages for science education according to an embodiment of the present invention;

[0010] Figure 2 is a flowchart of a message distribution method according to the prior art;

[0011] Figure 3A is a flowchart of another method for automatically distributing messages for science education according to an embodiment of the present invention;

[0012] Figure 3B is a code diagram for automatically distributing different messages according to an embodiment of the present invention;

[0013] Figure 4 is a flowchart of yet another method for automatically distributing messages for science education according to an embodiment of the present invention;

[0014] Figure 5 is a flowchart of a method for mass - sending messages based on a message distribution scenario according to an embodiment of the present invention;

[0015] Figure 6 is a schematic structural diagram of a device for automatically distributing messages for science education according to an embodiment of the present invention;

[0016] Figure 7 shows a schematic structural diagram of an electronic device suitable for implementing the embodiments of the present disclosure. Detailed Embodiments

[0017] In order to enable those skilled in the art of the present technology to better understand the solution of the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present invention.

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

[0019] According to an embodiment of the present invention, there is provided a method embodiment for automatic message distribution for science education. 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 the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here.

[0020] Figure 1 is for automatic message distribution for science education according to an embodiment of the present invention, as Figure 1 shown, the method includes the following steps:

[0021] Step S102, determine the message distribution scenario based on at least one of the following: the environment type of the current deployment environment, the message type of the message to be sent, and the token configuration information.

[0022] Automatically identify the environment type through the configuration file (profile) of the microservice framework of the current deployment environment, such as spring boot, where the environment type includes a production environment and / or a non-production environment; parse the metadata of the message to be sent, and obtain the message type from the metadata through the SPI extension interface based on the metadata, where the message type includes a notification type and / or an alarm type.

[0023] For example, when the environment type is the non-production environment, the message type is the alarm type, and the token configuration information is an independent token, the message distribution scenario is determined as the offline environment alarm scenario; when the environment type is the non-production environment, the message type is the alarm type, and the token configuration information is a non-independent token, the message distribution scenario is determined as the offline environment default scenario; when the environment type is the non-production environment, the message type is the notification type, and the token configuration information is an independent token, the message distribution scenario is determined as the offline environment notification scenario; when the environment type is the non-production environment, the message type is the notification type, and the token configuration information is a non-independent token, the message distribution scenario is determined as the offline environment default scenario; when the environment type is the production environment, the message type is the notification type, and the token configuration information is an independent token, the message distribution scenario is determined as the production environment notification scenario; when the environment type is the production environment, the message type is the notification type, and the token configuration information is a non-independent token, the message distribution scenario is determined as the production environment default scenario; when the environment type is the production environment, the message type is the alarm type, and the token configuration information is an independent token, the message distribution scenario is determined as the production environment alarm scenario; when the environment type is the production environment, the message type is the alarm type, and the token configuration information is a non-independent token, the message distribution scenario is determined as the production environment default scenario.

[0024] Step S104, based on the determined message distribution scenario, push the message to be sent into the corresponding message group.

[0025] When the message distribution scenario is determined as the offline environment alarm scenario, push the message to be sent to the offline environment alarm group; when the message distribution scenario is determined as the offline environment default scenario, push the message to be sent to the offline environment default group; when the message distribution scenario is determined as the offline environment notification scenario, push the message to be sent to the offline environment notification group; when the message distribution scenario is determined as the production environment notification scenario, push the message to be sent to the offline environment notification group; when the message distribution scenario is determined as the production environment default scenario, push the message to be sent to the offline environment notification group; when the message distribution scenario is determined as the production environment alarm scenario, push the message to be sent to the offline environment notification group.

[0026] In some other embodiments, before determining the message distribution scenario, the method further includes: using environment variables to dynamically specify tokens for the configuration center and the instant messaging group, and using middleware services to manage the mapping relationship between the configuration center and the instant messaging group; based on the determined message distribution scenario, pushing the message to be sent into the corresponding message group, including: based on the determined message distribution scenario, using the mapping relationship to push the message to be sent into the corresponding message group.

[0027] The embodiments of the present application improve environmental adaptability and reduce the need for manual configuration by automatically judging the environment. In addition, the embodiments of the present application enhance the message distribution ability, support distributing different types of messages to different group chats, and improve the flexibility and efficiency of message management.

[0028] In the current open-source community, the dynamic-tp framework is widely popular for its powerful functions and ease of use. It supports rapid deployment and monitoring and is applicable to various business scenarios. However, despite its relatively complete functionality in practice, there are still some limitations. First, for notifications from instant messaging tools, practical applications hope to be able to automatically identify offline and online environments, avoiding manual configuration by developers. This will greatly simplify the configuration process, improve efficiency, and reduce the occurrence of human errors. Second, for this notification, the existing system only supports two types: notification and alarm. Practical applications reserve room for extended configuration so that when the message volume increases later, notifications and alarms can be pushed to different groups respectively. Such flexibility will help better manage the message flow and ensure that different types of notifications can accurately reach the target groups.

[0029] To solve the above problems and achieve automatic message distribution, the embodiments of the present invention also provide another method for automatic message distribution in science education. In this method, the following improvements are mainly made: 1) Automatic environment judgment: By judging the profile of Spring Boot, different instant messaging tool tokens are determined; 2) Automatic message type judgment: According to the message type (notification or alarm), different instant messaging tool tokens are determined. In the open-source dynamic-tp, its process is as Figure 2 shown, only one token can be configured, and then both notifications and alarms are pushed to the same group. In the embodiments of the present application, the current deployment environment, message type, and whether there is an independent token are all judged, resulting in 8 message distribution scenarios.

[0030] Specifically, as Figure 3A shown, the method for automatic message distribution in science education according to the embodiments of the present application includes the following steps:

[0031] Step S300, determine that the notification threshold or alarm threshold is reached.

[0032] Step S302, determine whether the deployment environment is a production environment or a non-production environment.

[0033] For instant messaging tools, different tokens correspond to different group chats. Since the springboot profile of each environment is fixed, different tokens can be determined by judging the profile. At the same time, for alarm and notification type messages, the message type can also be extended through the SPI mechanism, and then different tokens can be used for judgment, so as to realize the automatic distribution of different messages. The specific implementation code is as follows:

[0034]

[0035] Step S304, determine whether the message type is an alarm type or a notification type.

[0036] Since the message type needs to be obtained, the default notification implementation of dynamic-tp is no longer applicable. This application uses the SPI mechanism to quickly provide a custom instant messaging tool notification implementation. The specific implementation code is as Figure 3B shown.

[0037] And the message type will be carried when sending notification and alarm messages. The specific implementation code is as follows:

[0038]

[0039] In this way, the distinction of different message types can be realized.

[0040] Step S306, determine whether the current push has an independent token.

[0041] Step S308, push the message.

[0042] If there is no independent token, the message is sent to the default unified push group of different environments; if there is an independent token, it is sent to an independent group, so as to realize automatic distribution when the initial state and the message volume increase. At the same time, the token comes from the public configuration space of the configuration center, and dynamic refresh of all services can be realized, that is, realize dynamic distribution without downtime.

[0043] The present invention automatically judges the environment and message type, and automatically selects the correct instant messaging tool group for message distribution according to the environment profile and message type. In addition, a flexible message distribution mechanism is adopted, which supports dynamically distributing notification and alarm messages to different group chats, improving the flexibility of message management.

[0044] In another embodiment, environment variables can also be used to dynamically specify the configuration center and the token of the instant messaging tool group, so that the configuration can be adjusted without modifying the code. In addition, a middleware service can be developed to manage the mapping relationship between the configuration center and the instant messaging tool group, which can be centrally managed and improve the maintainability of the system.

[0045] The embodiment of the present invention also provides another method for automatically distributing messages for science education, as Figure 4 shown, the method includes the following steps:

[0046] Step S402, configure and inject the automated thread pool.

[0047] The configuration and injection of the automated thread pool are described in detail in the patent application of the applicant with the application number 2025101418408 and the invention name "Configuration Method and Device for Science and Technology Innovation Education". The disclosure of this application is incorporated herein by reference in its entirety, so it will not be repeated here.

[0048] Step S404, send group messages.

[0049] The method for sending group messages provided by the embodiment of the present application is different from the prior art in that through secondary development of the dynamic-tp framework, it can not only automatically judge different deployment environments, but also intelligently select different instant messaging groups for distribution according to the message type, thus solving the problems of poor environmental adaptability and message distribution limitations in the process of dynamic instant messaging notification and alarm distribution in the prior art.

[0050] As Figure 5 shown, the method for sending group messages includes the following steps:

[0051] Step S4042, automatically judge the environment.

[0052] In the existing dynamic-tp framework, it is usually necessary to manually configure the instant messaging tokens in different environments. For example, different configurations are required for the production environment and the non-production environment. In order to simplify this process and improve the automation of the system, the present invention uses the profile mechanism of Spring Boot to automatically judge the current deployment environment, and then determine the required instant messaging tokens.

[0053] First, by reading the spring.profiles.active property in the Spring Boot configuration file, the environment in which the current application is running can be quickly identified. If the profile is "prod" or a similar production environment identifier, the system will automatically select the instant messaging token corresponding to the production environment; if the profile is "dev" or a similar development environment identifier, the instant messaging token corresponding to the development environment will be selected.

[0054] Next, automatic adaptation is performed. Based on this environment determination mechanism, when the system is deployed to different environments, there is no need to manually modify the code or configuration file. Just ensure that there are corresponding token configurations in different environments, and the system will automatically adapt to the correct instant messaging group according to the running environment.

[0055] In some embodiments, error recognition of the configuration file can also be performed. First, the context features of the configuration file are extracted. For example, the first feature vector and the second feature vector of the context are extracted. Then, based on the extended rank criterion, the two feature vectors are raised to a higher order. Through the raising operation, the features can be extended to a higher dimension, thereby capturing more potential correlations. After that, using multi-channel convolutional kernels, the first and second feature vectors after raising are subjected to feature coupling and fusion to generate a main embedding feature matrix and a secondary embedding feature matrix. In this way, the features at different levels in the configuration file can be effectively fused, providing rich feature information for subsequent error recognition. After that, the main embedding and secondary embedding feature matrices are unfolded along the extended dimension direction to form multiple sub-matrices. Each sub-matrix undergoes singular value decomposition (SVD) to extract the core subspace representation and the factor matrix. Finally, core feature extraction is performed. Based on the core subspace representation and the factor matrix, the principal component difference between the main feature matrix and the secondary feature matrix is calculated, and the core features are extracted. These core features can effectively characterize the error information and reference problems in the configuration file. By adopting the feature vector coupling and decomposition technology and combining multi-dimensional analysis methods, incorrect configuration files can be accurately identified.

[0056] Step S4044, automatically determine the message type.

[0057] In the prior art, instant message pushing usually treats notification and warning messages equally and pushes them to the same group chat, lacking flexibility. In the present invention, an automatic determination mechanism for message types (such as notifications and warnings) is introduced to achieve intelligent distribution of different types of messages.

[0058] Specifically, by using the SPI (Service Provider Interface) mechanism of the dynamic-tp framework, an extended interface for instant message notification implementation is customized. Through this mechanism, the system can identify the type of message (such as "notification" or "alarm"), and decide whether to use an independent instant message token according to the type. Specifically, notification messages and alarm messages are distinguished by the type identifier of the instant message. For example, a notification message may include some regular updates, while an alarm message is usually accompanied by a system exception or an alarm event. Each message type corresponds to a different instant message token and target group chat.

[0059] This application provides a flexible extension mechanism for the configuration of message types according to different business requirements, allowing the system to expand more message types and corresponding distribution strategies in the future according to the actual situation. For example, the system can modify the rules through the configuration center in the later stage to distribute different types of messages to different group chats, improving the management and monitoring effects of the messages.

[0060] Step S4046, dynamically manage the token.

[0061] To achieve dynamic update of instant message token configuration without downtime, the present invention introduces the concept of a configuration center and conducts unified management and update through this center. Through the configuration center, the system can obtain the instant message tokens required for different environments and message types in real time, avoiding the situation of message loss or incorrect push during system restart or deployment.

[0062] The system regularly or on demand pulls the instant message token configuration through the API interface provided by the configuration center. This configuration center can support distributed deployment to ensure that each service node can update the latest configuration in a timely manner, guaranteeing the accuracy and stability of message push. The token configuration information managed by the configuration center is shared among all services that need to send instant messages. When the token changes, all services will be able to obtain the new configuration in real time and push messages without interruption of operation.

[0063] Step S4048, determine the message distribution scenario.

[0064] To achieve more accurate message distribution, the present invention determines the message distribution scenario based on multiple factors such as the environment type, message type, and token independence.

[0065] In a production environment, if the message type is a notification and an independent token is used, the message will be pushed to the notification group in the production environment. In a non-production environment, if the message type is an alarm and an independent token is used, the message will be pushed to the alarm group in the non-production environment. If there is no independent token configuration, the system will push the message to the default environment group chat to ensure that the message can be correctly received under any circumstances.

[0066] Specifically, first, when the environment type is a non-production environment, the message type is an alarm type, and the token configuration information is an independent token, the system determines the message distribution scenario as an offline environment alarm scenario. This scenario is applicable to alarm messages in non-production environments such as development and testing. Especially when important alarms occur, using an independent token can ensure the security and accuracy of the message and timely transmit it to relevant personnel for processing. In a non-production environment, developers and testers need to quickly respond to potential system failures or anomalies, so this distribution scenario guarantees the priority and confidentiality of alarm messages.

[0067] When the environment type is a non-production environment, the message type is an alarm type, and the token configuration information is a non-independent token, the system determines the message distribution scenario as an offline environment default scenario. This scenario is applicable to some relatively routine or low-priority alarm messages in a non-production environment. In this case, although the message still needs to be transmitted in a timely manner, due to the non-independence of the token configuration information, the security requirements are relatively low. The target of such messages is usually developers or testers, aiming to provide feedback on the system operation status rather than an emergency alarm.

[0068] When the environment type is a non-production environment, the message type is a notification type, and the token configuration information is an independent token, the system determines the message distribution scenario as an offline environment notification scenario. Such notification messages are mainly used for information that needs to be conveyed during the development or testing process, such as system upgrades, test result feedback, etc. The independent token configuration ensures the security and accuracy of the notification message during the transmission process, avoiding unauthorized access or operations. In a non-production environment, this type of notification message usually does not involve highly sensitive content, but still requires ensuring the integrity and security of the message.

[0069] If the environment type is a non-production environment, the message type is a notification type, and the token configuration information is a non-independent token, the system determines the message distribution scenario as an offline environment default scenario. At this time, the push process of the notification message is relatively simple and is applicable to those routine notifications that do not contain sensitive information. Such notification messages are usually transmitted to developers or testers, and their security requirements are relatively low, so they can be pushed through a non-independent token to simplify the message transmission process.

[0070] When the environment type is the production environment, the message type is the notification type, and the token configuration information is an independent token, the system determines the message distribution scenario as the production environment notification scenario. Notification messages in the production environment usually involve important information such as system operation status and version updates. The accuracy and timeliness of these messages are crucial. By pushing messages through an independent token, the security and integrity of the messages can be ensured, avoiding any unauthorized access or tampering. Such notification messages are usually pushed to operation and maintenance personnel or relevant technical personnel so that they can process and respond in a timely manner in the production environment.

[0071] If the environment type is the production environment, the message type is the notification type, and the token configuration information is a non-independent token, the system determines the message distribution scenario as the production environment default scenario. In this case, although the notification message is passed to relevant personnel in the production environment, due to the non-independent token configuration information, the security requirements are relatively low. Such messages are applicable to routine notifications that do not involve sensitive data and have relatively low security requirements, and can usually be pushed to the default group of the production team or relevant departments.

[0072] When the environment type is the production environment, the message type is the alarm type, and the token configuration information is an independent token, the system determines the message distribution scenario as the production environment alarm scenario. Alarm messages in the production environment usually involve emergencies such as system failures and performance bottlenecks. Therefore, it is necessary to ensure the timeliness and security of message delivery. By pushing messages through an independent token, the system can strictly control the distribution of alarm messages, ensuring that only authorized personnel can receive these critical messages and thus make a rapid response.

[0073] Finally, when the environment type is the production environment, the message type is the alarm type, and the token configuration information is a non-independent token, the system determines the message distribution scenario as the production environment default scenario. At this time, the security requirements for alarm messages are relatively low, which is applicable to some low-priority or non-emergency alarms in the production environment. By pushing these messages through a non-independent token, although the security is reduced, the effective delivery of the messages can still be ensured, and it is usually used to provide non-emergency fault warnings or performance reminders to the production team.

[0074] Through these different scenario determination rules, the system can flexibly and efficiently handle the distribution of messages of different types, different priorities, and security requirements, ensuring accurate and secure message delivery in various environments. The design of these distribution scenarios ensures the adaptability and efficiency of the system under different conditions and can optimize message delivery according to actual needs.

[0075] Step S5049, distribute messages based on the message distribution scenario.

[0076] To further improve the performance and stability of the system, the present invention optimizes the logic of message pushing. Especially for message pushing in high-concurrency scenarios, the present invention adopts an asynchronous processing mechanism to ensure that instant message notifications and alarm messages can be quickly and reliably pushed to the target group chat.

[0077] By introducing message queue technology, the system can asynchronously process message pushing tasks. Messages first enter the queue and are then asynchronously consumed by the message pushing service, reducing the blocking waiting time for message sending and improving the system's response speed and processing efficiency. During the pushing process, if message sending fails due to network fluctuations or problems with the instant message interface, the system will automatically retry a certain number of times to ensure that the message can finally be successfully delivered to the target group.

[0078] The instant message notification and alarm message distribution method of the present invention has strong scalability and maintainability. Through unified configuration management and a flexible SPI extension mechanism, the system can easily handle new message types and distribution requirements that may arise in the future.

[0079] In summary, by introducing technologies such as automatic environment judgment, automatic message type judgment, dynamic token management, and intelligent message distribution on the basis of the existing dynamic-tp framework, the present invention solves the problems of poor environmental adaptability and poor flexibility of message distribution in the prior art. This solution not only improves the automation degree and flexibility of the system but also enhances the scalability and maintainability of the system, and can meet the continuously changing business needs in the future.

[0080] This application also provides a message automatic distribution device for science education, as Figure 6 shown, including: a determination module 62 configured to determine a message distribution scenario based on at least one of the following: the environment type of the current deployment environment, the message type of the message to be sent, and token configuration information; a push module 64 configured to push the message to be sent to the corresponding message group based on the determined message distribution scenario.

[0081] It should be noted that: for the message automatic distribution device for science education provided in the above embodiments, only the above division of each functional module is used for illustration. In actual applications, the above functions can be allocated to different functional modules according to needs, 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 automatic distribution device for science education provided in the above embodiments and the embodiments of the message automatic distribution method for science education belong to the same concept, and the specific implementation process is detailed in the method embodiments and will not be repeated here.

[0082] Figure 7The structural schematic diagram of an electronic device suitable for implementing the embodiments of the present disclosure is shown. It should be noted that Figure 7 The shown electronic device is only an example, and should not impose any limitations on the functions and usage scope of the embodiments of the present disclosure.

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

[0084] 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 required. 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 required, so that the computer program read from it can be installed into the storage section 1008 as required.

[0085] The above are only the preferred embodiments of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A method for automatic message distribution for scientific education, characterized in that: include: Determining a message distribution scenario based on at least one of: an environment type of a current deployment environment, a message type of a message to be sent, and token configuration information; Based on the determined message distribution scenario, the message to be sent is pushed to the corresponding message group.

2. The method according to claim 1, characterized in that Before determining the message distribution scenario, the method further includes: Automatically identifying the environment type through a configuration file of the microservice framework of the current deployment environment, wherein the environment type includes a production environment and / or a non-production environment; and / or Parse metadata of the message to be sent, and based on the metadata, obtain the message type through the SPI extension interface, wherein the message type includes a notification type and / or an alarm type.

3. The method according to claim 2, characterized in that Determining a message distribution scenario based on at least one of the following: an environment type of a current deployment environment, a message type of a message to be sent, and independent token configuration information, including at least one of the following: When the environment type is the non-production environment, the message type is the alarm type, and the token configuration information is an independent token, determining the message distribution scenario as an offline environment alarm scenario; When the environment type is the non-production environment, the message type is the alarm type, and the token configuration information is a non-independent token, or when the environment type is the non-production environment, the message type is the notification type, and the token configuration information is a non-independent token, the message distribution scenario is determined as an offline environment default scenario; When the environment type is the non-production environment, the message type is the notification type, and the token configuration information is an independent token, determining the message distribution scenario as an offline environment notification scenario; When the environment type is the production environment, the message type is the notification type, and the token configuration information is an independent token, the message distribution scenario is determined as a production environment notification scenario; When the environment type is the production environment, the message type is the notification type, and the token configuration information is a non-independent token, or when the environment type is the production environment, the message type is the alarm type, and the token configuration information is a non-independent token, the message distribution scenario is determined as a production environment default scenario; When the environment type is the production environment, the message type is the alarm type, and the token configuration information is an independent token, the message distribution scenario is determined to be a production environment alarm scenario.

4. The method according to claim 3, characterized in that Based on the determined message distribution scenario, pushing the message to be sent to a corresponding message group includes at least one of the following: When the message distribution scenario is determined to be the offline environment alarm scenario, pushing the message to be sent to an offline environment alarm group; When the message distribution scenario is determined to be the offline environment default scenario, the message to be sent is pushed to the offline environment default group; When the message distribution scenario is determined to be the offline environment notification scenario, pushing the message to be sent to an offline environment notification group; When the message distribution scenario is determined to be the production environment notification scenario, the message to be sent is pushed to an offline environment notification group; When the message distribution scenario is determined as the default scenario of the production environment, the message to be sent is pushed to an offline environment notification group; When the message distribution scenario is determined to be the production environment alarm scenario, the message to be sent is pushed to an offline environment notification group.

5. The method according to claim 1, characterized in that Before determining the message distribution scenario, the method further includes: determining whether a notification threshold or an alarm threshold is reached.

6. The method according to claim 1, characterized in that Before determining the message distribution scenario, the method further includes: using environment variables to dynamically specify tokens of a configuration center and an instant messaging group, and using a middleware service to manage a mapping relationship between the configuration center and the instant messaging group; Based on the determined message distribution scenario, the message to be sent is pushed to the corresponding message group, including: based on the determined message distribution scenario, the message to be sent is pushed to the corresponding message group by using the mapping relationship.

7. An automatic message distribution device for scientific education, characterized in that: include: A determination module configured to determine a message distribution scenario based on at least one of the following: an environment type of a current deployment environment, a message type of a message to be sent, and token configuration information; The push module is configured to push the message to be sent to a corresponding message group based on the determined message distribution scenario.

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