Hi,
I was wondering if there is a way to visualize in the UI what’s on the task queue to see what haven’t been processed?
Thanks,
Derek
Hi,
I was wondering if there is a way to visualize in the UI what’s on the task queue to see what haven’t been processed?
Thanks,
Derek
So we do not directly support this today from the UI or even the API. That being said, depending on your use case there may be some capabilities that solve your problem. Can you give me a bit more info on your use case?
I think it would be useful for
Thanks,
Derek
Are there metrics that give some information about the task backlogs?
You can use schedule to start latency metric. Without backlog it is close to 0 and keeps increasing with backlog size. We do have plans to add counts and possibly list operation for a task list.
Maxim, what metric are you referring to for schedule to start latency? I see the schedule_to_start_timeout counter, but I don’t see a timer metric for schedule to start.
It’s a client-side metric, see Go sample here. We are working on a java sample for it atm as well.
For Java, this thread that has a lot of info on how to set it up before the sample is committed.
We have got similar requirement where we would want to know the count of pending messages/events from the task queue. Is there any metric/api in the latest server version, we are on 1.20.1 server version
Is there any update on this? We want to use the number of messages in queue for scaling purpose. We already have it on schedule to start latency metrics but that doesn’t give a clear picture on how many messages are in queue that we would be beneficial for us.
Don’t think this is available as of yet.
one way to measure backlog currently via service metrics is service_latency
histogram metric for operations PollActivityTaskQueue
and PollWorkflowTaskQueue
, sample query:
histogram_quantile(0.95, sum(rate(service_latency_bucket{operation=~"PollActivityTaskQueue|PollWorkflowTaskQueue"}[5m])) by (operation, le))
On the SDK metrics side, as previously mentioned you would look at latencies of
workflow_task_schedule_to_start_latency
and activity_schedule_to_start_latency