How do associate queue processor item ID (param.pxItemID) with the details provided on processor landing page (e.g. data flow)
According to Queue-For-Processing help:
The system queues the page to the embedded Kafka data instance. This occurs immediately or upon the next Commit method run, depending on the Write Now setting. The queue processor picks up this item from the queue and processes the activity configured. A unique ID is generated to represent the ItemID and is available on the parameter page as the parameter, pxItemID.
Question:
Can the returned ItemID (param.pxItemID) be used to find out info/details on execution somewhere, e.g. Queue Processor landing page ? If so this would be great! From what I can see data flow details are about messages and their IDs, I cannot see any references to pxItemID there... I can only see details for broken queue items, I cannot see any details for queue items that were successfully processed (e.g. when was the queue item executed, how long the execution took etc...)
What can I use the returned ItemID for ?
Pegasystems Inc.
AU
Hi, I did not get to find out the answer to my question.
Abu Dhabi Executive Office (ADEO)
AE
Hi,
Thanks. We can see the Delayed Items and Broken items using this param.pxItemID.
I guess, once any item is processed, we can not know any information except the statistics from Data flow.
Pegasystems Inc.
PL
We're currently not tracking the individual items as they get processed by the Queue Processor. There's no way to see the details about items that have been processed via Admin Studio. We're doing this to maximize throughput of processing.
If needed you can implement a custom tracking mechanism (e.g. using DB) and store all the information about your work items (including pxItemID) there.
Please let me know in case you have any other questions.
Regards, Lukasz
US Bancorp
US
So you are saying that there is no way to get the following information
1. While Queue Processing is running, Can I know count of how many items are still pending / to be processed yet?
2. How many items are already processed?
As far I know there is an API call internally in pega that executes through Java step ((PegaAPI)tools).getSystemOperationsProvider().getQueueProcessorManagementAPI().getQueueProcessorDetails(tools,"QUEUEPROCESSORNAME");
This JAVA step API call will return the following parameters
{
"pxLag": "0",
"pxNodeType": "BackgroundProcessing",
"pxNumOfProcessedMessagesLastHour": "116",
"pxObjClass": "Data-SystemOperations-QueueProcessor-QueueProcessorInfo",
"pxQueueClass": "System-Queue-XXXXXXXXXX",
"pxQueueProcessorName": "QUEUEPROCESSORNAME",
"pxQueueProcessorState": "RUNNING",
"pzInsKey": "RULE-ASYNC-QUEUEPROCESSOR QUEUEPROCESSORNAME #20210302T182211.788 GMT",
"pzQueueProcessorConfig": {
So you are saying that there is no way to get the following information
1. While Queue Processing is running, Can I know count of how many items are still pending / to be processed yet?
2. How many items are already processed?
As far I know there is an API call internally in pega that executes through Java step ((PegaAPI)tools).getSystemOperationsProvider().getQueueProcessorManagementAPI().getQueueProcessorDetails(tools,"QUEUEPROCESSORNAME");
This JAVA step API call will return the following parameters
{
"pxLag": "0",
"pxNodeType": "BackgroundProcessing",
"pxNumOfProcessedMessagesLastHour": "116",
"pxObjClass": "Data-SystemOperations-QueueProcessor-QueueProcessorInfo",
"pxQueueClass": "System-Queue-XXXXXXXXXX",
"pxQueueProcessorName": "QUEUEPROCESSORNAME",
"pxQueueProcessorState": "RUNNING",
"pzInsKey": "RULE-ASYNC-QUEUEPROCESSOR QUEUEPROCESSORNAME #20210302T182211.788 GMT",
"pzQueueProcessorConfig": {
"pxObjClass": "Rule-Async-QueueProcessor",
"pyIsEnabled": "true",
"pyMaxThreads": "10"
}
}
Question : What are these pxLag & pxNumOfProcessedMessagesLastHour values? Does pxLag means how many are yet to be processed?