![work queue work queue](https://www.apptivo.com/wp-content/uploads/2015/04/viewpageofwq.png)
The detailed diagnosis of this measure reveals the details of jobs that are currently in progress.
![work queue work queue](https://documentation.clearcanvas.ca/Documentation/UsersGuide/ImageServer/1_5/clip0006.png)
If there are a large number of jobs that start after they are scheduled, your Broker is busy. Check the scheduled time against the start time for the job. Alternatively, this could be an indication that the Broker is unhealthy. If a lot of jobs are simultaneously in progress, one of the center scans may be taking a long time, for example, large VirtualCenter / Active Directory scans. This measure reports the number of records from the work_queue table where the status is ‘I’. Indicates the number of jobs that are currently executing.
![work queue work queue](https://pegaks.com/wp-content/uploads/2020/05/attachment-category-pega-8-2048x743.png)
Use the detailed diagnosis of this measure to know which jobs are pending, and their related details. Before a pending job should send up any flag, check that the Scheduled time is not before the Current time. Also, some jobs are pending because the Broker has actually scheduled them for a later time. You can have a number of pending jobs if the work queue has been suspended in order to process user logins, wherein this becomes a measure of how densely populated your Connection Broker is. A high value of this measure need not necessarily indicate a bottleneck. Waiting jobs are those jobs that are pending execution. Indicates the number of jobs that are currently waiting. For example, the more centers you have, the more refresh jobs will be in the queue. This is mostly a measure of the complexity of your Connection Broker configuration, in the sense of how many external systems you integrate with. Indicates the total number of jobs that are currently in queue. Measurements made by the test Measurement
#WORK QUEUE LICENSE#
The eG manager license should allow the detailed diagnosis capability.The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: To disable the capability, click on the Off option. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. If you want to view the detailed diagnosis for this measure, then set this flag to Yes. Accordingly, the ShowFinishedDD flag is set to No, by default. To reduce the strain on the database, the eG agent, by default, does not collect detailed diagnosis information for the New finished jobs measure. In such environments naturally, the detailed diagnosis data for this measure, if available, will consume a considerable amount of database space, and can sometimes even choke the database. In some environments, the count of the newly finished jobs could run to a thousand. The detailed diagnosis of this measure, if enabled, will provide the details of all the newly finished jobs. This test also reports the number of jobs in the queue that were recently completed. Specify the duration (in seconds) within which the test should timeout.
#WORK QUEUE HOW TO#
Refer to Pre-requisites for Monitoring the Leostream Connection Broker to know how to create such a user.Ĭonfirm the password by retyping it here. If need be, you can even create a special Administrator user on the Connection Broker for this purpose, and pass the credentials of that user to the test. To enable the test to log into the Connection Broker and extract statistics of interest from it, specify the login name of a user on the Connection Broker who is assigned the Administrator role. If the Connection Broker is SSL-enabled, then set this flag to Yes. Refers to the port used by the Connection Broker is listening.īy default, this flag is set to No, indicating that by default, the test connects to the Connection Broker via HTTP. Specify the IP address of the Connection Broker for which the test is to be configured. Configurable parameters for the test Parameter Outputs of the test : One set of results for the Connection Broker being monitored. Target of the test : A Leostream Connection BrokerĪgent deploying the test : An internal agent This test monitors the job queues and reports the status of jobs queued on the Connection Broker. For instance, if you requested an action and it has not taken place, check if the action is pending in the job queue.
![work queue work queue](https://academy.practicesuite.com/wp-content/uploads/2019/12/homescreenWQ.png)
When the Connection Broker is not functioning correctly, you can use the job queue as a diagnostics tool. The job queue contains Connection Broker processes that are independent of the Web interface.