CN112115019A - Application log monitoring method and system for application program - Google Patents
Application log monitoring method and system for application program Download PDFInfo
- Publication number
- CN112115019A CN112115019A CN202010869818.2A CN202010869818A CN112115019A CN 112115019 A CN112115019 A CN 112115019A CN 202010869818 A CN202010869818 A CN 202010869818A CN 112115019 A CN112115019 A CN 112115019A
- Authority
- CN
- China
- Prior art keywords
- application
- log
- monitoring
- logs
- application program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Abstract
The invention discloses an application log monitoring method and system for an application program, wherein the application log monitoring method comprises the following steps: checking the effectiveness of the collected application logs to screen out effective application logs; judging whether the screened effective application logs belong to a stack or not; according to configuration items of a preset rule index, performing predictive anomaly and non-predictive anomaly analysis on the effective application logs which do not belong to the stack; and sending alarm information related to the analysis result according to the configuration item. The invention aims at analyzing and alarming defects possibly occurring in business logic in logs in a targeted manner in real time at least.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an application log monitoring method and system for an application program.
Background
Journaling is a widely used concept in computer systems, and it is possible for operating system kernels, various application servers, etc., programs to output journaling. The content, size and use of the log are also different and difficult to generalize. With the development of software technology, the code line number of the software becomes very large, and the work of maintaining the software becomes very complicated and difficult. Usually, a log record code of a key service can be added in the process of writing the code, so that in the running process of software, the program processing condition of the key service is recorded in a log file, and once the software runs abnormally, corresponding processing can be carried out by analyzing log information.
The existing log analysis system is generally composed of a log collection agent and a log analysis management system, and can analyze and process a small number of log files. However, the existing log analysis system is not competent for analyzing and processing massive log files, and lacks real-time analysis, query and early warning capabilities. The real-time retrieval and monitoring of service indexes and abnormal stacks based on logs in the market are not realized by specific functions.
On the other hand, with the maturity of computer technology, although the application program running on the intelligent device is more and more perfect, the situation of error can be inevitable in the actual running process. Therefore, engineering technicians usually need to record the running state and the operation content of the application program through a log system so as to be conveniently viewed by personnel and used as a basis for debugging equipment. The log records various running states and operation information of the application program, and generates a log file.
But viewing and analyzing the log are based on Linux scripts and conventional tools are used for detecting the log. These tool approaches have the following disadvantages: the problem cannot be found at the first time if the system is not timely; the method is not intuitive and not easy to expand, and the application range is limited to a small number of host computers and log file types. In the existing method for monitoring the application logs, an application server records the application logs, periodically uploads application log files to a remote monitoring server, and then related technical maintenance personnel periodically acquire the log files from the monitoring server for analysis, so that the logs cannot be accurately processed in real time, the real-time requirement of an application level on alarm monitoring is met, and the log monitoring efficiency is low.
Disclosure of Invention
Aiming at the problems in the related art, the invention provides an application log monitoring method and system for an application program, which can analyze and alarm defects possibly occurring in business logic in logs in real time in a targeted manner.
The technical scheme of the invention is realized as follows:
according to an aspect of the present invention, there is provided an application log monitoring method for an application program, including:
checking the effectiveness of the collected application logs to screen out effective application logs;
judging whether the screened effective application logs belong to a stack or not;
according to configuration items of a preset rule index, performing predictive anomaly and non-predictive anomaly analysis on the effective application logs which do not belong to the stack;
and sending alarm information related to the analysis result according to the configuration item.
According to the embodiment of the invention, the application log monitoring method further comprises the following steps: and monitoring at least one of an error code type and a statistical index type through a visual console according to a monitoring index, wherein the monitoring index comprises at least one of a monitoring grade, whether to upgrade an alarm, a notification frequency and a notifier.
According to the embodiment of the present invention, sending the alarm information includes: and judging whether the alarm condition is met by utilizing the minute-level timing task.
According to the embodiment of the present invention, sending the alarm information related to the analysis result according to the configuration item includes: acquiring a result of a corresponding statistical item based on an index, and comparing the result of the statistical item with a threshold value of the index; and if the result of the statistical item reaches the threshold value of the index, sending the alarm information.
According to the embodiment of the invention, the application log monitoring method further comprises the following steps: and installing a collection tool for grabbing the collected application log locally in the application program.
According to another aspect of the present invention, there is provided an application log monitoring system for an application program, comprising:
the collection tool is installed locally in the application program and used for collecting the application logs to the distributed message queue;
the log routing module is used for checking the validity of the application logs in the distributed message queue so as to screen out valid application logs;
the log processing module is used for judging whether the screened effective application logs belong to a stack or not, and analyzing foreseeable exception and unpredicted exception of the effective application logs which do not belong to the stack according to configuration items of preset rule indexes;
and the alarm notification module is used for sending alarm information related to the analysis result according to the configuration item.
According to an embodiment of the present invention, the alarm notification module is further configured to receive a socket request or a microservice request sent by a logless system, and the logless application is converted into the valid application log.
According to the embodiment of the invention, the application log monitoring system further comprises a batch running module used for loading the configuration items and the related indexes at fixed time.
According to the embodiment of the invention, the application log monitoring system further comprises a visual console for monitoring at least one of the error code type and the statistical index type according to a monitoring index, wherein the monitoring index comprises at least one of a monitoring level, whether to upgrade an alarm, a notification frequency and a notifier.
According to the embodiment of the invention, the application log monitoring system further comprises a distributed cache or a database, which is used for storing the analysis result of the log processing module.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a flow diagram of an application log monitoring method for an application program according to an embodiment of the present invention;
FIG. 2 is a flow chart of the alarm steps of an application log monitoring method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an architecture of an application log monitoring system according to an embodiment of the invention;
FIG. 4 is a schematic diagram of a visual console error code class configuration of an application log monitoring system according to an embodiment of the present invention;
fig. 5 is a schematic diagram of determining configuration items for stack binning according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present invention.
Aiming at the defects in the prior art, the invention provides an application log monitoring method and an application log monitoring system for an application program. The application log monitoring method includes the following steps S1 to S4. The application log monitoring method of the present invention will be described below with reference to fig. 1.
(1) Step S1
At this step S1, the validity of the collected application logs is first checked to screen out valid application logs. Specifically, in step S1, the application log may be collected before the validity of the application log is determined, and filebolt (a log data collector of a local file) regular check is performed through step S11; at step S12, it is determined whether the application log check passed, and if the application log check passed, the process proceeds to step S13, where the collected application log is uploaded to the cluster, for example, to the kafka cluster. Then at step S14 in fig. 1, the application log of the cluster may be consumed by the log routing module and it is determined whether the application log is valid. In a case where the reference log is judged to be valid, the method proceeds to step S2.
(2) Step S2
At this step S2, it is determined whether the screened valid application log belongs to a stack. As shown in fig. 1, in the illustrated method flow example, it is determined at step S15 whether the screened valid application log belongs to a stack. The rule for judging whether the stack belongs to the stack can be configured according to actual needs. When the valid application log belongs to the stack, performing step S16, and warehousing the stack application log; when the valid application log is determined not to belong to the stack, step S17 is performed to process the valid application log that needs to be monitored. The stack log binning at step S16 in fig. 1 is the same as the valid log binning logic that does not belong to the stack. Fig. 5 is a schematic diagram of determining configuration items for stack binning according to an embodiment of the present invention.
(3) Step S3
At this step S3, predictive anomaly and non-predictive anomaly analyses are performed on the valid application logs not belonging to the stack according to configuration items of a predetermined rule index. As shown in fig. 1, in the illustrated method flow example, it is determined at step S18 whether there is a configuration item. And in the case of configuration items, performing step S19, performing further analysis statistics and logic operations on the screened valid logs, matching configuration items of established rule indexes, performing asynchronous operations, analyzing respectively for unforeseen anomalies and foreseeable anomalies, and persisting the final result. According to an embodiment of the present invention, the configuration items of the stack entry (stack exception) may be the same as the configuration items of the established rule index for monitoring the valid log.
(4) Step S4
And sending alarm information related to the analysis result according to the configuration item. And informing the lasting final result to each application responsible person according to the index configuration item and the related event through a certain rule. In some embodiments, the generated alert information may be sent by mail, text message, nail, voice call, or the like.
The application log monitoring method can monitor and establish a corresponding processing method in real time through the updated content in the application log file, so as to solve the technical problem that the existing application log monitoring method cannot carry out aggregation analysis and alarm on possible defects of service logic in the log in real time and pertinently, thereby being capable of accurately processing the system and the application in real time, meeting the real-time requirement of the application level on alarm monitoring, and further realizing the purposes of improving the monitoring efficiency and finding the instantaneity of the problems. The invention completes the monitoring of the corresponding index and the stack exception without intervening application codes. Effectively improve monitoring efficiency, the cost of using manpower sparingly.
The scheme of the invention can be applied to various application programs. For example, the application programs related to various payment success rates of card swiping business, cash in and out success rates of bank channels, wind control system interception situations and the like.
In some embodiments, the present invention applies a log monitoring method that utilizes minute-level timing tasks to determine whether an alarm condition is met. As shown in fig. 2, by timing the task at the minute level, when it is determined that the alarm condition is satisfied, the task is added to the queue to be sent to wait for sending. And when the alarm condition is judged not to be met, emptying the statistical result.
Fig. 3 is a schematic architecture diagram of an application log monitoring system according to an embodiment of the present invention. The application log monitoring method described above may be applied to the application log monitoring system shown in fig. 3. As shown in fig. 3, the application log monitoring system of the present invention includes a collection tool 21, a log routing module 22, a log processing module 23, and an alarm notification module 24.
The collection tool 21 may be installed locally to the application and used to collect application logs to the distributed message queue. The log routing module 22 is configured to check validity of the application logs in the distributed message queue to filter out valid application logs. The log processing module 23 is configured to determine whether the screened valid application logs belong to a stack, and according to a configuration item of a predetermined rule index. The log processing module 23 also performs predictive exception and non-predictive exception analysis on the active application logs that do not belong to the stack. The alarm notification module 24 is configured to send alarm information related to the analysis result according to the configuration item.
In the embodiment shown in fig. 3, when the object is a Niginx (an HTTP and reverse proxy web server) system log and application logs in various languages (such as Java, Python, etc.), the collection tool 21 may employ a Logstash (an application log management platform) or a Filebeat component, and the Logstash or the Filebeat component collects log file information to a distributed message queue Kafka (a distributed publish-subscribe message system). When the object is a logless system, the collection tool 21 may actively send a socket request or a microservice request to the alarm notification module 24 for processing. The log routing module 22 consumes messages from the distributed message queue Kafka to the routing application, translates them into byte objects, and checks the log validity. Valid logs can be screened out by established rules to wait for further analysis processing. The log processing module 23 further analyzes and counts the screened effective logs, performs logical operation, matches configuration items of established rule indexes, performs asynchronous operation, analyzes against unforeseen abnormality and predictive abnormality, and persists the final result.
In one particular example, it is foreseen that the anomaly may be, for example: the service is unavailable due to release or some other reasons of a certain channel service, and logs can be printed to be obtained through the system without throwing the exception; in this example, the established rule index may be: if the stack exception is different, alarming according to stack exception, or counting by defining error code, for example, alarming when a specific number of times occurs within 1 minute; in this example, the configuration items may include: the number of times the service connection failed, the transaction success rate, etc.
The alarm notification module 24 notifies the persistent final result to each application responsible person according to the index configuration item and the related event through a certain rule. The alarm notification module 24 is further configured to receive a socket request or a microservice request sent by the logless system, and convert the logless application into the valid application log.
With continued reference to FIG. 3, the application log monitoring system of the present invention further includes a batching module 25 and a visualization console 26. The batching module 25 is used for loading the configuration items and the related indexes at regular time. And the visual console 26 is used for monitoring at least one of the error code type and the statistical index type according to monitoring indexes, wherein the monitoring indexes comprise at least one of monitoring level, whether to upgrade the alarm, notification frequency and notifier. As shown in fig. 4, the present invention provides a visual console 26 to realize visual monitoring, and the visual console 26 can monitor the error code type, the statistical indicator type, and the like, respectively, wherein the related indicators include but are not limited to monitoring level, screen projection status, whether to automatically upgrade the alarm, whether to have a plan, a notifier, description, and notification frequency, and the like.
The application log monitoring system of the present invention further comprises a database 27, wherein the database 27 comprises a distributed cache redis or a database polardb, and is used for storing the analysis result of the log processing module.
The application log monitoring system provided by the invention captures the application logs of the application program by installing the logstack/filebeat collecting tool in the local of the application program or resource to be monitored. Format splicing and the like can be performed on the application logs by configuring some specific codes on the collection tool. If the middleware is redis and the like, a specific script can be used. Thereafter, the application log is sent to the Kafka cluster. The fileteam collection tool does not perform any filtering on the local log, and all filtering is performed by the method.
The monitoring system firstly obtains the log file from the distributed message queue Kafka, then the log file is distributed to a log processing core node at the back end based on the system, the core node converts the log into an internal object based on the log, then analysis statistics is carried out on the log based on configured statistical items, and the statistical result is put into a distributed cache Redis or a database polardb. The alarm system can obtain the results of the corresponding statistical items based on the indexes at regular time to summarize and calculate, and finally compares the results with the threshold values of the indexes, and if the threshold values are touched, the alarm system gives an alarm.
The traditional log monitoring technology only carries out statistical recording on logs, only monitors hosts similar to Cpu, memory and the like, but does not monitor the predictability and unpredictability errors of specific logics of an application, so that the abnormal discovery is delayed, a machine is waited for discovering problems and then logged to check the log to trace back the cause of the problems, and the checked problems are not the first site but snapshot.
In the invention, no invasive code implantation is carried out on the system and the application program, the system application prints a specification log for errors which can occur predictably, and the specification log is notified to a responsible person in real time at the first time when a problem occurs, so that a decision (rollback or other remedial measures) can be made immediately, and particularly for the application program with low error tolerance rate such as payment and the like.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (10)
1. An application log monitoring method for an application program, comprising:
checking the effectiveness of the collected application logs to screen out effective application logs;
judging whether the screened effective application logs belong to a stack or not;
according to configuration items of a preset rule index, performing predictive anomaly and non-predictive anomaly analysis on the effective application logs which do not belong to the stack;
and sending alarm information related to the analysis result according to the configuration item.
2. The application log monitoring method for an application program according to claim 1, further comprising:
and monitoring at least one of an error code type and a statistical index type through a visual console according to a monitoring index, wherein the monitoring index comprises at least one of a monitoring grade, whether to upgrade an alarm, a notification frequency and a notifier.
3. The application log monitoring method for the application program according to claim 1, wherein sending the alarm information comprises:
and judging whether the alarm condition is met by utilizing the minute-level timing task.
4. The application log monitoring method for the application program according to claim 1, wherein sending alarm information related to the analysis result according to the configuration item comprises:
acquiring a result of a corresponding statistical item based on an index, and comparing the result of the statistical item with a threshold value of the index;
and if the result of the statistical item reaches the threshold value of the index, sending the alarm information.
5. The application log monitoring method for an application program according to claim 1, further comprising:
and installing a collection tool for grabbing the collected application log locally in the application program.
6. An application log monitoring system for an application program, comprising:
the collection tool is installed locally in the application program and used for collecting the application logs to the distributed message queue;
the log routing module is used for checking the validity of the application logs in the distributed message queue so as to screen out valid application logs;
the log processing module is used for judging whether the screened effective application logs belong to a stack or not, and analyzing foreseeable exception and unpredicted exception of the effective application logs which do not belong to the stack according to configuration items of preset rule indexes;
and the alarm notification module is used for sending alarm information related to the analysis result according to the configuration item.
7. The application log monitoring system for an application program of claim 6,
the alarm notification module is further used for receiving a socket request or a micro-service request sent by the no-log system, and the no-log application is converted into the effective application log.
8. The application log monitoring system for an application program of claim 6, further comprising:
and the batch running module is used for loading the configuration items and the related indexes at fixed time.
9. The application log monitoring system for an application program of claim 6, further comprising:
and the visual control console is used for monitoring at least one of the error code type and the statistical index type according to monitoring indexes, wherein the monitoring indexes comprise at least one of monitoring level, alarm upgrading or not, notification frequency and notifier.
10. The application log monitoring system for an application program of claim 6, further comprising:
and the distributed cache or the database is used for storing the analysis result of the log processing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010869818.2A CN112115019A (en) | 2020-08-26 | 2020-08-26 | Application log monitoring method and system for application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010869818.2A CN112115019A (en) | 2020-08-26 | 2020-08-26 | Application log monitoring method and system for application program |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112115019A true CN112115019A (en) | 2020-12-22 |
Family
ID=73805592
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010869818.2A Pending CN112115019A (en) | 2020-08-26 | 2020-08-26 | Application log monitoring method and system for application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112115019A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105183609A (en) * | 2015-09-16 | 2015-12-23 | 焦点科技股份有限公司 | Real-time monitoring system and method applied to software system |
| CN105426292A (en) * | 2015-10-29 | 2016-03-23 | 网易（杭州）网络有限公司 | Game log real-time processing system and method |
| CN106815089A (en) * | 2016-12-23 | 2017-06-09 | 北京五八信息技术有限公司 | Malfunction elimination method and device based on daily record |
| CN106844147A (en) * | 2016-12-30 | 2017-06-13 | 杭州东方通信软件技术有限公司 | A kind of monitoring system and method |
| CN109522209A (en) * | 2018-09-29 | 2019-03-26 | 中国平安人寿保险股份有限公司 | Log stack information analysis method and device, computer installation and storage medium |
| CN110224865A (en) * | 2019-05-30 | 2019-09-10 | 宝付网络科技（上海）有限公司 | A kind of log warning system based on Stream Processing |
| CN111240832A (en) * | 2019-12-31 | 2020-06-05 | 上海汇付数据服务有限公司 | API management method and API gateway system |
-
2020
- 2020-08-26 CN CN202010869818.2A patent/CN112115019A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105183609A (en) * | 2015-09-16 | 2015-12-23 | 焦点科技股份有限公司 | Real-time monitoring system and method applied to software system |
| CN105426292A (en) * | 2015-10-29 | 2016-03-23 | 网易（杭州）网络有限公司 | Game log real-time processing system and method |
| CN106815089A (en) * | 2016-12-23 | 2017-06-09 | 北京五八信息技术有限公司 | Malfunction elimination method and device based on daily record |
| CN106844147A (en) * | 2016-12-30 | 2017-06-13 | 杭州东方通信软件技术有限公司 | A kind of monitoring system and method |
| CN109522209A (en) * | 2018-09-29 | 2019-03-26 | 中国平安人寿保险股份有限公司 | Log stack information analysis method and device, computer installation and storage medium |
| CN110224865A (en) * | 2019-05-30 | 2019-09-10 | 宝付网络科技（上海）有限公司 | A kind of log warning system based on Stream Processing |
| CN111240832A (en) * | 2019-12-31 | 2020-06-05 | 上海汇付数据服务有限公司 | API management method and API gateway system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107992398B (en) | Monitoring method and monitoring system of service system | |
| US8892960B2 (en) | System and method for determining causes of performance problems within middleware systems | |
| CN110309030A (en) | Log analysis monitoring system and method based on ELK and Zabbix | |
| US11093349B2 (en) | System and method for reactive log spooling | |
| CN110908883B (en) | User portrait data monitoring method, system, equipment and storage medium | |
| US8903923B2 (en) | Methods and apparatus for system monitoring | |
| WO2016188100A1 (en) | Information system fault scenario information collection method and system | |
| CN111459782B (en) | Method and device for monitoring service system, cloud platform system and server | |
| CN110231998B (en) | Detection method and device for distributed timing task and storage medium | |
| CN104574219A (en) | System and method for monitoring and early warning of operation conditions of power grid service information system | |
| CN113505044B (en) | Database warning method, device, equipment and storage medium | |
| US9600523B2 (en) | Efficient data collection mechanism in middleware runtime environment | |
| CN111522703A (en) | Method, apparatus and computer program product for monitoring access requests | |
| US8554908B2 (en) | Device, method, and storage medium for detecting multiplexed relation of applications | |
| CN115220995A (en) | Agent probe-based micro-service full-link analysis method | |
| CN112256548B (en) | Abnormal data monitoring method and device, server and storage medium | |
| US20060053021A1 (en) | Method for monitoring and managing an information system | |
| US8949669B1 (en) | Error detection, correction and triage of a storage array errors | |
| CN112115019A (en) | Application log monitoring method and system for application program | |
| CN113472881B (en) | Statistical method and device for online terminal equipment | |
| CN114297020A (en) | Enterprise industrial control safety brain platform system and operation method | |
| CN113342596A (en) | Distributed monitoring method, system and device for equipment indexes | |
| CN111061609A (en) | Log monitoring method and system | |
| CN112134760A (en) | Link state monitoring method, device, equipment and computer readable storage medium | |
| CN116610532B (en) | Redis client monitoring method, system, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |