CN112764992B - Thread pool monitoring method, device and equipment - Google Patents
Thread pool monitoring method, device and equipment Download PDFInfo
- Publication number
- CN112764992B CN112764992B CN202110073864.6A CN202110073864A CN112764992B CN 112764992 B CN112764992 B CN 112764992B CN 202110073864 A CN202110073864 A CN 202110073864A CN 112764992 B CN112764992 B CN 112764992B
- Authority
- CN
- China
- Prior art keywords
- monitoring
- thread pool
- monitoring data
- data
- index
- 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.)
- Active
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 470
- 238000000034 method Methods 0.000 title claims abstract description 77
- 238000012216 screening Methods 0.000 claims description 67
- 238000012545 processing Methods 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 19
- 238000004364 calculation method Methods 0.000 claims description 14
- 238000012806 monitoring device Methods 0.000 claims description 10
- 230000001186 cumulative effect Effects 0.000 claims description 7
- 238000004140 cleaning Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 16
- 238000004891 communication Methods 0.000 description 11
- 230000000694 effects Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 208000016253 exhaustion Diseases 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2474—Sequence data queries, e.g. querying versioned data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2477—Temporal data queries
Abstract
The embodiment of the application provides a method, a device and equipment for monitoring a thread pool, wherein the method comprises the following steps: the method comprises the steps that a monitoring client acquires monitoring data from service providing equipment according to a preset time interval, wherein the monitoring data are used for indicating the running state of a thread pool deployed in the service providing equipment; the monitoring client sends monitoring data to the monitoring server so that the monitoring server stores the monitoring data. The monitoring of the thread pool is realized through the process, and the gap of the thread pool monitoring function is filled, so that the service provider can know the working state of the thread pool in time according to the monitoring data, and the problem of insufficient service capability caused by the exhaustion of the thread pool is avoided.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for monitoring a thread pool.
Background
Some communication architectures include a service providing device and a service consuming device. The service providing device is used for providing services. The service consuming device may send a service request to the service providing device to invoke the service provided by the service providing device.
The service providing device is provided with a thread pool, and the thread pool comprises a plurality of threads. Each thread may be used to execute a service request. In a scenario where service requests are highly concurrent, the multiple threads may be used to execute multiple service requests in parallel.
However, the inventors found in the course of implementing the present application that: the service provider cannot know the real working state of the thread pool, so that the condition that the thread pool is exhausted may exist, and the service providing device cannot normally provide the service. Therefore, how to monitor the working state of the thread pool becomes a technical problem to be solved.
Disclosure of Invention
The application provides a method, a device and equipment for monitoring a thread pool, which are used for monitoring the working state of the thread pool.
In a first aspect, the present application provides a method for monitoring a thread pool, applied to a monitoring client, where the method includes:
acquiring monitoring data from service providing equipment according to a preset time interval, wherein the monitoring data are used for indicating the running state of a thread pool deployed in the service providing equipment;
and sending the monitoring data to a monitoring server so that the monitoring server stores the monitoring data into a database.
In a possible implementation manner, the acquiring monitoring data from the service providing device according to a preset time interval includes:
acquiring acquisition parameters, wherein the acquisition parameters comprise: at least one monitoring index corresponding to the thread pool;
collecting data corresponding to the at least one monitoring index from the service providing equipment according to the preset time interval;
and generating the monitoring data according to the time stamp corresponding to the acquisition time and the data corresponding to the at least one monitoring index.
In a possible implementation, the monitoring client is integrated in the service providing device; the step of collecting data corresponding to the at least one monitoring index from the service providing device according to the preset time interval includes:
and calling an index acquisition interface provided by the thread pool according to the preset time interval to obtain data corresponding to the at least one monitoring index.
In a possible implementation manner, the at least one monitoring index includes one or more of the following:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
The number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
the number of service requests being processed by the thread pool;
the thread pool has processed a cumulative number of service requests.
In a possible implementation manner, the collecting parameters further include: screening indication information, wherein the screening indication information is used for indicating a screening mode supported by the monitoring data during display;
the generating the monitoring data according to the time stamp corresponding to the acquisition time and the data corresponding to the at least one monitoring index includes:
and generating the monitoring data according to the time stamp corresponding to the acquisition time, the data corresponding to the at least one monitoring index and the screening indication information.
In a second aspect, the present application provides a method for monitoring a thread pool, applied to a monitoring server, where the method includes:
receiving monitoring data from a monitoring client, wherein the monitoring data are acquired from a service providing device by the monitoring client according to a preset time interval, and the monitoring data are used for indicating the running state of a thread pool deployed in the service providing device;
And storing the monitoring data into a database.
In a possible implementation manner, the monitoring data includes data corresponding to at least one monitoring index, and the at least one monitoring index includes one or more of the following:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
the number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
the number of service requests being processed by the thread pool;
the thread pool has processed an accumulated number of service requests.
In a possible implementation manner, the monitoring data further includes: and the screening indication information is used for indicating a screening mode supported by the monitoring data during display.
In a possible implementation manner, the monitoring data further includes: a time stamp; storing the monitoring data in a database, comprising:
and storing the time stamp and the data corresponding to the first monitoring index into a time sequence database corresponding to the first monitoring index aiming at any first monitoring index in the at least one monitoring index.
In a possible implementation manner, before storing the monitoring data in the database, the method further includes:
and cleaning the monitoring data.
In a possible implementation manner, the method further includes:
receiving a display request message from a terminal device;
according to the display request message, acquiring target monitoring data to be displayed from the database;
and sending the target monitoring data to the terminal equipment so that the terminal equipment displays the target monitoring data.
In a possible implementation manner, the display request message includes an index to be displayed and a display parameter, and according to the display request message, target monitoring data to be displayed is obtained from the database, including:
acquiring data corresponding to the index to be displayed from the database according to the index to be displayed;
and according to the display parameters, carrying out calculation processing and/or screening processing on the data corresponding to the index to be displayed to obtain the target monitoring data.
In a possible implementation manner, the display parameters include at least one of the following:
the time parameter is used for indicating a time range for displaying the monitoring data;
The display mode parameter is used for indicating to display real-time monitoring data or historical monitoring data;
the screening parameters are used for indicating screening modes adopted when the monitoring data are displayed;
the granularity parameter is used for indicating the time granularity for displaying the monitoring data;
and the calculation mode parameter is used for indicating the mode of carrying out the calculation processing on the monitoring data.
In a third aspect, the present application provides a monitoring device for a thread pool, applied to a monitoring client, where the device includes:
the system comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for acquiring monitoring data from service providing equipment according to a preset time interval, and the monitoring data are used for indicating the running state of a thread pool deployed in the service providing equipment;
and the sending module is used for sending the monitoring data to a monitoring server so that the monitoring server stores the monitoring data into a database.
In a possible implementation manner, the acquiring module is specifically configured to:
acquiring acquisition parameters, wherein the acquisition parameters comprise: at least one monitoring index corresponding to the thread pool;
collecting data corresponding to the at least one monitoring index from the service providing equipment according to the preset time interval;
And generating the monitoring data according to the time stamp corresponding to the acquisition time and the data corresponding to the at least one monitoring index.
In a possible implementation, the monitoring client is integrated in the service providing device; the acquisition module is specifically configured to:
and calling an index acquisition interface provided by the thread pool according to the preset time interval to obtain data corresponding to the at least one monitoring index.
In a possible implementation manner, the at least one monitoring index includes one or more of the following:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
the number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
the number of service requests being processed by the thread pool;
the thread pool has processed a cumulative number of service requests.
In a possible implementation manner, the collecting parameters further include: screening indication information, wherein the screening indication information is used for indicating a screening mode supported by the monitoring data during display; the acquisition module is specifically configured to:
And generating the monitoring data according to the time stamp corresponding to the acquisition time, the data corresponding to the at least one monitoring index and the screening indication information.
In a fourth aspect, the present application provides a thread pool monitoring device, applied to a monitoring server, where the device includes:
the receiving module is used for receiving monitoring data from a monitoring client, wherein the monitoring data are acquired from a service providing device by the monitoring client according to a preset time interval, and the monitoring data are used for indicating the running state of a thread pool deployed in the service providing device;
and the processing module is used for storing the monitoring data into a database.
In a possible implementation manner, the monitoring data includes data corresponding to at least one monitoring index, and the at least one monitoring index includes one or more of the following:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
the number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
The number of service requests being processed by the thread pool;
the thread pool has processed an accumulated number of service requests.
In a possible implementation manner, the monitoring data further includes: and the screening indication information is used for indicating a screening mode supported by the monitoring data during display.
In a possible implementation manner, the monitoring data further includes: a time stamp; the processing module is specifically configured to:
and storing the time stamp and the data corresponding to the first monitoring index into a time sequence database corresponding to the first monitoring index aiming at any first monitoring index in the at least one monitoring index.
In a possible implementation manner, the processing module is further configured to: and cleaning the monitoring data.
In a possible implementation manner, the receiving module is further configured to: receiving a display request message from a terminal device;
the processing module is further configured to: according to the display request message, acquiring target monitoring data to be displayed from the database;
the device also comprises a sending module, wherein the sending module is used for: and sending the target monitoring data to the terminal equipment so that the terminal equipment displays the target monitoring data.
In a possible implementation manner, the display request message includes an index to be displayed and a display parameter, and the processing module is specifically configured to:
acquiring data corresponding to the index to be displayed from the database according to the index to be displayed;
and according to the display parameters, carrying out calculation processing and/or screening processing on the data corresponding to the index to be displayed to obtain the target monitoring data.
In a possible implementation manner, the display parameters include at least one of the following:
the time parameter is used for indicating a time range for displaying the monitoring data;
the display mode parameter is used for indicating to display real-time monitoring data or historical monitoring data;
the screening parameters are used for indicating screening modes adopted when the monitoring data are displayed;
the granularity parameter is used for indicating the time granularity for displaying the monitoring data;
and the calculation mode parameter is used for indicating the mode of carrying out the calculation processing on the monitoring data.
In a fifth aspect, embodiments of the present application provide an electronic device, including: a memory for storing a computer program, and a processor for running the computer program to implement the method according to any one of the first aspects or to implement the method according to any one of the second aspects.
In a sixth aspect, embodiments of the present application provide a computer readable storage medium comprising: a computer program which, when executed by a processor, implements the method according to any of the first aspects or the second aspect.
In a seventh aspect, embodiments of the present application provide a computer program product comprising: a computer program which, when executed by a processor, implements the method according to any of the first aspects or the second aspect.
The method, device and equipment for monitoring the thread pool provided by the embodiment of the application comprise the following steps: the method comprises the steps that a monitoring client acquires monitoring data from service providing equipment according to a preset time interval, wherein the monitoring data are used for indicating the running state of a thread pool deployed in the service providing equipment; the monitoring client sends monitoring data to the monitoring server so that the monitoring server stores the monitoring data. The monitoring of the thread pool is realized through the process, and the gap of the thread pool monitoring function is filled, so that the service provider can know the working state of the thread pool in time according to the monitoring data stored in the database, thereby avoiding the problem of insufficient service capacity caused by the exhaustion of the thread pool.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive faculty for a person skilled in the art.
Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application;
fig. 2 is a schematic diagram of a service providing device according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a thread pool monitoring system according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of another thread pool monitoring system according to an embodiment of the present disclosure;
FIG. 5 is a flowchart illustrating a method for monitoring a thread pool according to an embodiment of the present disclosure;
FIG. 6 is a flowchart illustrating another method for monitoring a thread pool according to an embodiment of the present disclosure;
FIG. 7 is a schematic diagram of a display interface according to an embodiment of the present disclosure;
FIG. 8 is a schematic structural diagram of a thread pool monitoring device according to an embodiment of the present disclosure;
FIG. 9 is a schematic structural diagram of another thread pool monitoring device according to an embodiment of the present disclosure;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be capable of operation in sequences other than those illustrated or described herein, for example. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application. As shown in fig. 1, the system architecture includes a service providing device (Provider) and a service consuming device (Consumer). The service providing device refers to a device for providing a service. The service in the embodiments of the present application may be an interface that may be invoked by a service consumer device to perform a specified task. The service providing device starts a service monitor port and issues the service. The service consuming device may connect to a port that the service providing device initiates and invoke a service published by the service providing device.
It should be appreciated that the number of service consuming devices may be one or more. When the number of service consumption devices is plural, the plural service consumption devices may also request services from the service providing device at the same time.
The number of service providing devices may be one or more. When the number of service providing apparatuses is plural, the types of services provided by the plural service providing apparatuses may be the same or different. In one example, the number of service providing apparatuses is 10, of which 5 are used to provide payment type services, another 4 are used to provide order type services, and still another 1 are used to provide refund type services.
It should be noted that the system architecture shown in fig. 1 may be applied to various service systems, for example, an e-commerce platform service system, a social network service system, and the like. The service providing device may also be referred to as a service system server. In some traffic scenarios, when the number of service providing devices is plural, the plural service providing devices may employ a distributed architecture or a clustered architecture.
Fig. 2 is a schematic diagram of a service providing device according to an embodiment of the present application. As shown in fig. 2, the service providing apparatus has a service request queue disposed therein. The service request queue is used for caching the service requests to be processed. The service request in this embodiment may also be referred to as a Task (Task). When the service providing device receives a service request sent by the service consuming device, the service request may be added to the service request queue.
With continued reference to fig. 2, in this embodiment, a thread pool is also deployed in the service providing device. A thread pool is a pattern of thread usage in which multiple threads are maintained. Each thread may be used to execute a service request in a service request queue. In a scenario where service requests are highly concurrent, the multiple threads may be scheduled in parallel, thereby concurrently executing multiple service requests in a service request queue. The problem of high memory overhead caused by repeatedly creating and destroying threads can be avoided by adopting the thread pool.
However, the inventors found in the course of implementing the present application that: due to the lack of the thread pool monitoring function, in practical application, a service provider cannot know the real working state of the thread pool, so that the condition that the thread pool is exhausted may exist, and the service providing device cannot normally provide services. For example, taking the example of 10 threads included in the thread pool, if the service providing device receives 15 service requests, only 10 of the service requests may be executed, while the other 5 service requests are rejected. In this case, since the service providing apparatus appears to be operating normally, the service provider may misunderstand that the service capability itself is normal. It should be appreciated that in the case of distortion in service capability assessment, thread pool exhaustion is likely to occur. Therefore, how to monitor the working state of the thread pool becomes a technical problem to be solved.
The method, the device and the equipment for monitoring the thread pool aim to solve the technical problems. The architecture of the thread pool monitoring system in the embodiments of the present application is described below in conjunction with fig. 3 and 4.
Fig. 3 is a schematic architecture diagram of a thread pool monitoring system according to an embodiment of the present application. The monitoring system can be used for monitoring the working state of a thread pool deployed by the service providing equipment. As shown in fig. 3, the monitoring system includes: a monitoring client and a monitoring server.
The monitoring client is in communication connection with the service providing device. The monitoring client is used for collecting monitoring data from the service providing equipment, wherein the monitoring data indicates the running state of the thread pool. And the monitoring client sends the collected monitoring data to the monitoring server, so that the monitoring server stores the monitoring data.
In some possible implementations, as shown in fig. 3, a terminal device may also be included in the monitoring system. The terminal device may be any electronic device having a display function including, but not limited to: desktop computers, notebook computers, smart phones, televisions, projectors, etc. The terminal device is in communication connection with the monitoring server. The terminal device can acquire the monitoring data from the monitoring server and display the acquired monitoring data. Thus, the user can intuitively know the running state of the thread pool through the display interface of the terminal device.
It should be understood that the monitoring client and the monitoring server may be integrated into one physical device, and the monitoring client and the monitoring server may also be two physical devices that are independent of each other, which is not limited in this embodiment of the present application.
FIG. 4 is a schematic diagram of another thread pool monitoring system according to an embodiment of the present application. As shown in fig. 4, in some possible implementations, the monitoring client may also be integrated into the service providing device.
It should be noted that, in the embodiment of the present application, when the communication protocol adopted between the service providing device and the service consuming device is different, the types of thread pools deployed in the service providing device may also be different. Illustratively, when a Jeff (JSF) communication scheme is adopted between a service providing device and a service consuming device, a JSF thread pool is deployed in the service providing device. When other communication modes are adopted between the service providing device and the service consuming device, other types of thread pools are deployed in the service providing device. The method for monitoring the thread pool provided by the embodiment of the application is not limited to the type of the thread pool, and can be used for monitoring any type of thread pool.
The technical scheme of the present application is described in detail below with specific examples. The following embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.
Fig. 5 is a flowchart of a method for monitoring a thread pool according to an embodiment of the present application. The method of the embodiment can be used for monitoring the running state of a thread pool deployed in the service providing equipment. As shown in fig. 5, the method of the present embodiment includes:
S501: and the monitoring client acquires monitoring data from the service providing equipment according to a preset time interval, wherein the monitoring data are used for indicating the running state of a thread pool deployed in the service providing equipment.
It should be understood that the present embodiment is not limited to the preset time interval. For example, the monitoring client may acquire monitoring data from the service providing apparatus once every second, or acquire monitoring data from the service providing apparatus once every minute, or the like.
In a possible implementation manner, in connection with fig. 3, in a scenario where the monitoring client and the service providing device are spatially independent from each other, the monitoring client and the service providing device are communicatively connected through a preset protocol. The monitoring client can send a monitoring request to the service providing equipment according to a preset time interval, and the service providing equipment acquires monitoring data according to the monitoring request and sends the monitoring data to the monitoring client.
In another possible implementation, in connection with fig. 4, the monitoring client may also be integrated in the service providing device. In this manner, the monitoring client may be integrated into the service providing device in a maven-dependent manner. The monitoring client can call a data acquisition interface provided by the thread pool according to a preset time interval to obtain monitoring data. By integrating the monitoring client into the service providing equipment, the acquisition time delay of the monitoring data can be reduced, and the real-time performance of the monitoring result is ensured.
In this embodiment, the monitoring data includes data corresponding to one or more monitoring indexes. Wherein the monitoring index may include, but is not limited to, one or more of the following:
(1) Maximum number of threads configured in thread pool
(2) Maximum number of threads once used in thread pool
(3) Number of threads currently used in thread pool
(4) Number of active threads in thread pool
(5) The number of core threads in the thread pool
(6) Length of service request queue corresponding to thread pool
(7) Number of service requests being processed by a thread pool
(8) Cumulative number of service requests once processed by thread pool
It should be appreciated that the above monitoring metrics describe the operating state of the thread pool. The service provider can know the working state of the thread pool according to the data corresponding to the monitoring index. When the thread pool is about to be exhausted or the exhaustion risk exists, relevant measures (such as capacity expansion thread number, parameter adjustment of the thread pool and the like) can be timely taken, so that the problem that the service providing equipment cannot normally provide service due to the fact that the thread pool is exhausted is avoided.
Optionally, the monitoring data may further include a timestamp corresponding to the time of the monitoring data acquisition. In this way, the service provider can know the monitoring data corresponding to different time points according to the time stamp, so that when the state of the thread pool is monitored to be abnormal, the problem can be conveniently positioned or analyzed.
S502: the monitoring client sends monitoring data to the monitoring server.
Accordingly, the monitoring server receives the monitoring data from the monitoring client.
In this embodiment, various communication modes may be adopted between the monitoring client and the monitoring server. For example, the monitoring client may send the monitoring data to the monitoring server in a point-to-point delivery mode. The monitoring data may also be communicated between the monitoring client and the monitoring server, for example, using a publish-subscribe mode.
In one possible implementation, kafka is used to communicate monitoring data between a monitoring client and a monitoring server. Kafka is a publish/subscribe based messaging system. Illustratively, kafka maintains one or more Topic (Topic) queues. And after the monitoring client collects the monitoring data, the monitoring data is issued to a topic queue corresponding to Kafka according to the category of the monitoring data. The monitoring server may subscribe to the monitoring data of one or more topics and obtain the monitoring data in the topics to which it subscribes from Kafka. By adopting Kafka, the communication performance between the monitoring client and the monitoring server can be improved.
S503: the monitoring server stores the monitoring data in a database.
In some possible implementations, after the monitoring server receives the monitoring data, the monitoring data may be cleaned, and then the cleaned monitoring data is stored in the database, so as to ensure the integrity and validity of the monitoring data stored in the database.
In some possible implementations, the monitoring server may also classify the monitoring data. For example, the data can be classified and stored according to the monitoring index, so that the query efficiency can be improved when the data corresponding to a certain monitoring index needs to be queried. Of course, in practical application, other classification storage manners may exist, and this embodiment is not limited to this.
The method for monitoring the thread pool provided by the embodiment comprises the following steps: the method comprises the steps that a monitoring client acquires monitoring data from service providing equipment according to a preset time interval, wherein the monitoring data are used for indicating the running state of a thread pool deployed in the service providing equipment; the monitoring client sends monitoring data to the monitoring server so that the monitoring server stores the monitoring data. The monitoring of the thread pool is realized through the process, and the gap of the thread pool monitoring function is filled, so that the service provider can know the working state of the thread pool in time according to the monitoring data stored in the database, thereby avoiding the problem of insufficient service capacity caused by the exhaustion of the thread pool.
Fig. 6 is a flowchart of another method for monitoring a thread pool according to an embodiment of the present application. This embodiment will be described in detail with reference to the embodiment shown in fig. 5. As shown in fig. 6, the method of the present embodiment includes:
s601: the monitoring client acquires acquisition parameters, wherein the acquisition parameters comprise: at least one monitoring index corresponding to the thread pool.
Wherein the at least one monitoring indicator includes, but is not limited to, one or more of the following:
(1) Maximum number of threads configured in thread pool
(2) Maximum number of threads once used in thread pool
(3) Number of threads currently used in thread pool
(4) Number of active threads in thread pool
(5) The number of core threads in the thread pool
(6) Length of service request queue corresponding to thread pool
(7) Number of service requests being processed by a thread pool
(8) Cumulative number of service requests once processed by thread pool
In some possible implementations, the monitoring client obtains a preset acquisition parameter. That is, the acquisition parameters may be preset by the monitoring client, or may be agreed upon by the monitoring client and the monitoring server.
In other possible implementations, the monitoring client obtains the acquisition parameters input by the user. That is, the acquisition parameters may be user-configurable. For example, the monitoring client may have a parameter configuration interface where a user may configure the monitoring metrics that need to be collected.
S602: and the monitoring client acquires data corresponding to the at least one monitoring index from the service providing equipment according to a preset time interval.
Optionally, when the monitoring client is integrated in the service providing device, the monitoring client invokes the index collection interface provided by the thread pool according to a preset time interval, so as to obtain data corresponding to the at least one monitoring index.
S603: and the monitoring client generates monitoring data according to the time stamp corresponding to the acquisition time and the data corresponding to the at least one monitoring index.
The monitoring data includes data corresponding to the at least one monitoring index and the timestamp.
In some possible implementations, the acquisition parameters may further include: and screening the indication information. The screening indication information is used for indicating a screening mode supported by the monitoring data during display. Illustratively, the screening means may be one or more of the following: screening by thread pool name, screening by IP of service providing device, screening by identification of service providing device, etc.
In this way, the monitoring client can generate the monitoring data according to the time stamp corresponding to the acquisition time, the data corresponding to the at least one monitoring index and the screening indication information. That is, the monitoring data may include: the method comprises the steps of collecting a time stamp corresponding to a moment, data corresponding to at least one monitoring index and screening indication information.
In one example, the monitoring data generated by the monitoring client is as follows:
it should be noted that the above examples are only one possible illustration, and in practical applications, other more information may be included in the monitoring data, which is not limited in this embodiment.
S604: the monitoring client sends monitoring data to the monitoring server.
Accordingly, the monitoring server receives the monitoring data from the monitoring client.
S605: and the monitoring server performs cleaning treatment on the monitoring data.
It should be understood that the specific implementation of S604 and S605 is similar to the embodiment shown in fig. 5, and will not be repeated here.
S606: the monitoring server stores the time stamp and the data corresponding to the first monitoring index into a time sequence database corresponding to the first monitoring index aiming at any first monitoring index in the at least one monitoring index.
Taking the number of active threads (activeCount) in the thread pool as an example, the time series database corresponding to the monitoring index is as follows:
in this example, 1608011620-1608011627 is a timestamp, and the value following the timestamp is the number of active threads collected at the corresponding time.
It can be understood that in this embodiment, by classifying and storing the monitoring data according to the monitoring index, different monitoring indexes are stored in different time sequence databases, so that when data corresponding to a certain monitoring index needs to be queried, the data can be directly obtained from the time sequence database corresponding to the monitoring index, thereby improving query efficiency.
Optionally, if the monitoring data reported by the monitoring client includes screening indication information, the monitoring server stores the screening indication information in the corresponding time sequence database when storing the monitoring data in the time sequence database corresponding to different monitoring indexes in a classified manner. When the user carries out screening display on the monitoring index through the terminal equipment, screening processing can be carried out according to the screening indication information.
S607: and the terminal equipment sends a display request message to the monitoring server.
S608: and the monitoring server acquires target monitoring data to be displayed from the database according to the display request message.
In one possible implementation, the presentation request message includes the index to be presented and the presentation parameter. The terminal device provides a display interface for a user, and the user can input the index to be displayed and the display parameter in the display interface. Fig. 7 is a schematic diagram of a display interface according to an embodiment of the present application. As shown in fig. 7, the indicator to be displayed may be one or more of the above-mentioned monitoring indicators. The presentation parameters may include at least one of:
(1) And the time parameter is used for indicating the time range for displaying the monitoring data. For example, the user may set the start monitoring time and the end monitoring time.
(2) And the display mode parameter is used for indicating to display the real-time monitoring data or the historical monitoring data. For example, the user may choose to monitor in real time or not.
(3) And the screening parameter is used for indicating the mode of screening the monitoring data. For example, the user may choose to filter the monitoring data based on the group identification of the service providing device, the IP of the service providing device, the thread pool name, etc.
(4) And the granularity parameter is used for indicating the time granularity for displaying the monitoring data. For example, the user may choose to present the monitoring data at a time of day, minute, hour, etc. granularity.
(5) And the calculation mode parameter is used for indicating the mode of calculating and processing the monitoring data. For example, the user may choose to display the mean, the most value, the TOP value, etc. of the index to be displayed.
Specifically, the monitoring server acquires data corresponding to the index to be displayed from the database according to the index to be displayed. For example, assuming that the monitoring index to be displayed by the user is "the number of active threads in the thread pool", the monitoring server acquires data from the time sequence database corresponding to the monitoring index. And then, the monitoring server performs calculation processing and/or screening processing on the data corresponding to the index to be displayed according to the display parameters to obtain target monitoring data.
S609: and the monitoring server sends the target monitoring data to the terminal equipment.
S610: and the terminal equipment displays the target monitoring data.
Illustratively, assuming that the user filters a thread pool named "N1", FIG. 7 illustrates the presentation results corresponding to the monitor indicator "number of active threads in thread pool". Wherein the horizontal axis is the time axis and the vertical axis is the number of active threads in the thread pool.
In this embodiment, the gap of the thread pool monitoring function is filled by monitoring the thread pool, so that the service provider can timely know the working state of the thread pool according to the monitoring data of the thread pool, thereby avoiding the problem of insufficient service capability caused by the exhaustion of the thread pool.
Fig. 8 is a schematic structural diagram of a thread pool monitoring device according to an embodiment of the present application. The apparatus of this embodiment may be in the form of software and/or hardware. The device of the embodiment may be used as a monitoring client or integrated in the monitoring client. As shown in fig. 8, the thread pool monitoring device 800 provided in this embodiment includes: an acquisition module 801 and a transmission module 802.
The acquiring module 801 is configured to acquire monitoring data from a service providing device according to a preset time interval, where the monitoring data is used to indicate an operation state of a thread pool deployed in the service providing device;
And a sending module 802, configured to send the monitoring data to a monitoring server, so that the monitoring server stores the monitoring data in a database.
In a possible implementation manner, the obtaining module 801 is specifically configured to:
acquiring acquisition parameters, wherein the acquisition parameters comprise: at least one monitoring index corresponding to the thread pool;
collecting data corresponding to the at least one monitoring index from the service providing equipment according to the preset time interval;
and generating the monitoring data according to the time stamp corresponding to the acquisition time and the data corresponding to the at least one monitoring index.
In a possible implementation, the monitoring client is integrated in the service providing device; the obtaining module 801 is specifically configured to:
and calling an index acquisition interface provided by the thread pool according to the preset time interval to obtain data corresponding to the at least one monitoring index.
In a possible implementation manner, the at least one monitoring index includes one or more of the following:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
The number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
the number of service requests being processed by the thread pool;
the thread pool has processed a cumulative number of service requests.
In a possible implementation manner, the collecting parameters further include: screening indication information, wherein the screening indication information is used for indicating a screening mode supported by the monitoring data during display; the obtaining module 801 is specifically configured to:
and generating the monitoring data according to the time stamp corresponding to the acquisition time, the data corresponding to the at least one monitoring index and the screening indication information.
The thread pool monitoring device provided in this embodiment may be used to execute the method executed by the monitoring client in any of the above method embodiments, and its implementation principle and technical effects are similar, and are not described herein.
Fig. 9 is a schematic structural diagram of another thread pool monitoring device according to an embodiment of the present application. The apparatus of this embodiment may be in the form of software and/or hardware. The device of the embodiment can be used as a monitoring guest server or integrated in the monitoring server. As shown in fig. 9, the thread pool monitoring apparatus 900 provided in this embodiment includes: a receiving module 901 and a processing module 902.
The receiving module 901 is configured to receive monitoring data from a monitoring client, where the monitoring data is obtained from a service providing device by the monitoring client according to a preset time interval, and the monitoring data is used to indicate an operation state of a thread pool deployed in the service providing device;
a processing module 902, configured to store the monitoring data in a database.
In a possible implementation manner, the monitoring data includes data corresponding to at least one monitoring index, and the at least one monitoring index includes one or more of the following:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
the number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
the number of service requests being processed by the thread pool;
the thread pool has processed an accumulated number of service requests.
In a possible implementation manner, the monitoring data further includes: and the screening indication information is used for indicating a screening mode supported by the monitoring data during display.
In a possible implementation manner, the monitoring data further includes: a time stamp; the processing module 902 is specifically configured to:
and storing the time stamp and the data corresponding to the first monitoring index into a time sequence database corresponding to the first monitoring index aiming at any first monitoring index in the at least one monitoring index.
In a possible implementation manner, the processing module 902 is further configured to: and cleaning the monitoring data.
In a possible implementation manner, as shown in fig. 9, the apparatus of this embodiment may further include a sending module 903, where the receiving module 901 is further configured to: receiving a display request message from a terminal device;
the processing module 902 is further configured to: according to the display request message, acquiring target monitoring data to be displayed from the database;
the sending module 903 is configured to: and sending the target monitoring data to the terminal equipment so that the terminal equipment displays the target monitoring data.
In a possible implementation manner, the display request message includes an index to be displayed and a display parameter, and the processing module 902 is specifically configured to:
acquiring data corresponding to the index to be displayed from the database according to the index to be displayed;
And according to the display parameters, carrying out calculation processing and/or screening processing on the data corresponding to the index to be displayed to obtain the target monitoring data.
In a possible implementation manner, the display parameters include at least one of the following:
the time parameter is used for indicating a time range for displaying the monitoring data;
the display mode parameter is used for indicating to display real-time monitoring data or historical monitoring data;
the screening parameters are used for indicating screening modes adopted when the monitoring data are displayed;
the granularity parameter is used for indicating the time granularity for displaying the monitoring data;
and the calculation mode parameter is used for indicating the mode of carrying out the calculation processing on the monitoring data.
The thread pool monitoring device provided in this embodiment may be used to execute the method executed by the monitoring server in any of the above method embodiments, and its implementation principle and technical effects are similar, and are not described herein.
Fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device may act as a monitoring client or monitoring server. As shown in fig. 10, the electronic device 1000 provided in this embodiment includes: processor 1001 and memory 1002.
Wherein the memory 1002 is for storing a computer program; the processor 1001 is configured to execute a computer program stored in the memory, so as to implement the method for monitoring the thread pool executed by the monitoring client in the above embodiment, or implement the method for monitoring the thread pool executed by the monitoring server. The specific reference may be made to the related descriptions in the foregoing method embodiments, where the implementation principle and the technical effect are similar, and the description of this embodiment is omitted here.
Alternatively, the memory 1002 may be separate or integrated with the processor 1001.
When the memory 1002 is a device separate from the processor 1001, the electronic apparatus 1000 may further include: a bus 1003 connecting the memory 1002 and the processor 1001.
Optionally, the electronic device 1000 may also include a communication component 1004 for communicating with other devices.
The embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium includes a computer program, where the computer program is configured to implement a method for monitoring a thread pool executed by a monitoring client in any one of the method embodiments described above, or implement a method for monitoring a thread pool executed by a monitoring server, where the implementation principle and technical effects are similar, and are not repeated herein.
The embodiment of the application also provides a chip, which comprises: the computer program is stored in the memory, and the processor runs the computer program to execute the method for monitoring the thread pool executed by the monitoring client in any method embodiment, or to implement the method for monitoring the thread pool executed by the monitoring server, and its implementation principle and technical effects are similar, and are not repeated here.
The embodiment of the application further provides a computer program product, which comprises a computer program, when the computer program is executed by a processor, the method for monitoring the thread pool executed by the monitoring client in any of the method embodiments is realized, or the method for monitoring the thread pool executed by the monitoring server is realized, and the implementation principle and the technical effect are similar, and are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.
The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional module in each embodiment of the present application may be integrated in one processing unit, or each module may exist alone physically, or two or more modules may be integrated in one unit. The units formed by the modules can be realized in a form of hardware or a form of hardware and software functional units.
The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional module is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (english: processor) to perform some of the steps of the methods described in the embodiments of the present application.
It should be understood that the above processor may be a central processing unit (english: central Processing Unit, abbreviated as CPU), or may be other general purpose processors, digital signal processors (english: digital Signal Processor, abbreviated as DSP), application specific integrated circuits (english: application Specific Integrated Circuit, abbreviated as ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.
The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile memory NVM, such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk or optical disk, etc.
The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or one type of bus.
The storage medium may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). It is also possible that the processor and the storage medium reside as discrete components in an electronic device or a master device.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims (13)
1. A method for monitoring a thread pool, applied to a monitoring client, the method comprising:
acquiring monitoring data from service providing equipment according to a preset time interval, wherein the monitoring data are used for indicating the running state of a thread pool deployed in the service providing equipment;
sending the monitoring data to a monitoring server so that the monitoring server stores the monitoring data into a database;
the obtaining monitoring data from the service providing device according to the preset time interval comprises the following steps:
acquiring acquisition parameters, wherein the acquisition parameters comprise: at least one monitoring index and screening indication information corresponding to the thread pool; the screening indication information is used for indicating a screening mode supported by the monitoring data during display; the screening mode is at least one of screening according to the name of the thread pool, screening according to the IP of the service providing equipment and screening according to the identification of the service providing equipment;
Collecting data corresponding to the at least one monitoring index from the service providing equipment according to the preset time interval;
generating the monitoring data according to the screening indication information, the time stamp corresponding to the acquisition time and the data corresponding to the at least one monitoring index;
wherein the at least one monitoring indicator comprises one or more of:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
the number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
the number of service requests being processed by the thread pool;
the thread pool has processed a cumulative number of service requests.
2. The method of claim 1, wherein the monitoring client is integrated in the service providing device; the step of collecting data corresponding to the at least one monitoring index from the service providing device according to the preset time interval includes:
and calling an index acquisition interface provided by the thread pool according to the preset time interval to obtain data corresponding to the at least one monitoring index.
3. A method for monitoring a thread pool, applied to a monitoring server, the method comprising:
receiving monitoring data from a monitoring client, wherein the monitoring data is generated according to the screening indication information, a time stamp corresponding to the acquisition time and data corresponding to at least one monitoring index after the monitoring client acquires at least one monitoring index and screening indication information corresponding to a thread pool and acquires data corresponding to at least one monitoring index from service providing equipment according to a preset time interval, and the monitoring data is used for indicating the running state of the thread pool deployed in the service providing equipment;
storing the monitoring data in a database;
the monitoring data comprises data corresponding to at least one monitoring index, and the at least one monitoring index comprises one or more of the following:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
the number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
The number of service requests being processed by the thread pool;
the thread pool has processed an accumulated number of service requests.
4. A method according to claim 3, wherein the monitoring data further comprises: a time stamp; storing the monitoring data in a database, comprising:
and storing the time stamp and the data corresponding to the first monitoring index into a time sequence database corresponding to the first monitoring index aiming at any first monitoring index in the at least one monitoring index.
5. The method of claim 3 or 4, further comprising, prior to storing the monitoring data in a database:
and cleaning the monitoring data.
6. The method according to claim 3 or 4, characterized in that the method further comprises:
receiving a display request message from a terminal device;
according to the display request message, acquiring target monitoring data to be displayed from the database;
and sending the target monitoring data to the terminal equipment so that the terminal equipment displays the target monitoring data.
7. The method of claim 6, wherein the presentation request message includes an indicator to be presented and a presentation parameter, and wherein obtaining target monitoring data to be presented from the database according to the presentation request message comprises:
Acquiring data corresponding to the index to be displayed from the database according to the index to be displayed;
and according to the display parameters, carrying out calculation processing and/or screening processing on the data corresponding to the index to be displayed to obtain the target monitoring data.
8. The method of claim 7, wherein the presentation parameters include at least one of:
the time parameter is used for indicating a time range for displaying the monitoring data;
the display mode parameter is used for indicating to display real-time monitoring data or historical monitoring data;
the screening parameters are used for indicating screening modes adopted when the monitoring data are displayed;
the granularity parameter is used for indicating the time granularity for displaying the monitoring data;
and the calculation mode parameter is used for indicating the mode of carrying out the calculation processing on the monitoring data.
9. A thread pool monitoring apparatus for use with a monitoring client, the apparatus comprising:
the system comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for acquiring monitoring data from service providing equipment according to a preset time interval, and the monitoring data are used for indicating the running state of a thread pool deployed in the service providing equipment;
A sending module for sending the monitoring data to a monitoring server so that the monitoring server stores the monitoring data in a database
The acquisition module is specifically configured to acquire acquisition parameters, where the acquisition parameters include: at least one monitoring index and screening indication information corresponding to the thread pool; the screening indication information is used for indicating a screening mode supported by the monitoring data during display; the screening mode is at least one of screening according to the name of the thread pool, screening according to the IP of the service providing equipment and screening according to the identification of the service providing equipment; collecting data corresponding to the at least one monitoring index from the service providing equipment according to the preset time interval; generating the monitoring data according to the screening indication information, the time stamp corresponding to the acquisition time and the data corresponding to the at least one monitoring index;
wherein the at least one monitoring indicator comprises one or more of:
the maximum number of threads configured in the thread pool;
the maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
the number of active threads in the thread pool;
The number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
the number of service requests being processed by the thread pool;
the thread pool has processed a cumulative number of service requests.
10. A thread pool monitoring device for use with a monitoring server, the device comprising:
the receiving module is used for receiving monitoring data from a monitoring client, wherein the monitoring data is generated according to the screening indication information, a time stamp corresponding to the acquisition moment and data corresponding to the at least one monitoring index after the monitoring client acquires at least one monitoring index and screening indication information corresponding to a thread pool and acquires data corresponding to the at least one monitoring index from service providing equipment according to a preset time interval, and the monitoring data is used for indicating the running state of the thread pool deployed in the service providing equipment;
the processing module is used for storing the monitoring data into a database;
the monitoring data comprises data corresponding to at least one monitoring index, and the at least one monitoring index comprises one or more of the following:
the maximum number of threads configured in the thread pool;
The maximum number of threads used once in the thread pool;
the number of threads currently used in the thread pool;
the number of active threads in the thread pool;
the number of core threads in the thread pool;
the length of the service request queue corresponding to the thread pool;
the number of service requests being processed by the thread pool;
the thread pool has processed an accumulated number of service requests.
11. An electronic device, comprising: a memory for storing a computer program, and a processor for running the computer program to implement the method of claim 1 or 2, or to implement the method of any of claims 3 to 8.
12. A computer-readable storage medium, comprising: computer program which, when executed by a processor, implements the method according to claim 1 or 2 or implements the method according to any of claims 3 to 8.
13. A computer program product comprising a computer program which, when executed by a processor, implements the method according to claim 1 or 2, or implements the method according to any of claims 3 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110073864.6A CN112764992B (en) | 2021-01-20 | 2021-01-20 | Thread pool monitoring method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110073864.6A CN112764992B (en) | 2021-01-20 | 2021-01-20 | Thread pool monitoring method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112764992A CN112764992A (en) | 2021-05-07 |
| CN112764992B true CN112764992B (en) | 2024-04-12 |
Family
ID=75703445
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110073864.6A Active CN112764992B (en) | 2021-01-20 | 2021-01-20 | Thread pool monitoring method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112764992B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115981962B (en) * | 2022-12-30 | 2024-03-12 | 北京基调网络股份有限公司 | Thread pool monitoring method and device, electronic equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106385341A (en) * | 2016-08-31 | 2017-02-08 | 福建天晴数码有限公司 | Thread monitoring method and system of client |
| CN108763046A (en) * | 2018-06-01 | 2018-11-06 | 中国平安人寿保险股份有限公司 | Thread operation and monitoring method, device, computer equipment and storage medium |
| CN112100034A (en) * | 2020-09-29 | 2020-12-18 | 泰康保险集团股份有限公司 | Service monitoring method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9274853B2 (en) * | 2013-08-05 | 2016-03-01 | International Business Machines Corporation | Utilizing multiple memory pools during mobility operations |
-
2021
- 2021-01-20 CN CN202110073864.6A patent/CN112764992B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106385341A (en) * | 2016-08-31 | 2017-02-08 | 福建天晴数码有限公司 | Thread monitoring method and system of client |
| CN108763046A (en) * | 2018-06-01 | 2018-11-06 | 中国平安人寿保险股份有限公司 | Thread operation and monitoring method, device, computer equipment and storage medium |
| CN112100034A (en) * | 2020-09-29 | 2020-12-18 | 泰康保险集团股份有限公司 | Service monitoring method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112764992A (en) | 2021-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110086666B (en) | Alarm method, device and system | |
| CN107992398B (en) | Monitoring method and monitoring system of service system | |
| CN109271411B (en) | Report generation method, report generation device, computer equipment and storage medium | |
| CN108776934B (en) | Distributed data calculation method and device, computer equipment and readable storage medium | |
| CN108683720B (en) | Container cluster service configuration method and device | |
| US20150170070A1 (en) | Method, apparatus, and system for monitoring website | |
| CN109039819B (en) | Time delay statistical method, device, system and storage medium | |
| US20130007261A1 (en) | Virtual data center monitoring | |
| US10680926B2 (en) | Displaying adaptive content in heterogeneous performance monitoring and troubleshooting environments | |
| CN112307057A (en) | Data processing method and device, electronic equipment and computer storage medium | |
| US6240453B1 (en) | Managing unused resources in a service application | |
| US9292336B1 (en) | Systems and methods providing optimization data | |
| CN109327353B (en) | Service flow determination method and device and electronic equipment | |
| CN109407984B (en) | Method, device and equipment for monitoring performance of storage system | |
| CN109992473A (en) | Monitoring method, device, equipment and the storage medium of application system | |
| CN112328448A (en) | Zookeeper-based monitoring method, monitoring device, equipment and storage medium | |
| CN110932933A (en) | Network condition monitoring method, computing device and computer storage medium | |
| CN112764992B (en) | Thread pool monitoring method, device and equipment | |
| CN114048090A (en) | K8S-based container cloud platform monitoring method and device and storage medium | |
| CN112100034A (en) | Service monitoring method and device | |
| CN114785690B (en) | Monitoring method based on service grid and related equipment | |
| CN111339466A (en) | Interface management method and device, electronic equipment and readable storage medium | |
| CN111061588A (en) | Method and device for locating database abnormal source | |
| CN109995834A (en) | Massive dataflow processing method, calculates equipment and storage medium at device | |
| CN113973273A (en) | Charging method and device for network slicing service |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |