temporalio / temporalio/features

SDK should log when WFT completion takes a long time

Open
#827 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
32
Forks
28
Avg merge
1d 9h
Merged PRs (30d)
7

Description

Is your feature request related to a problem? Please describe.

With the introduction of external storage, downloading and uploading payload from/to external storage contributes to the workflow task duration. The operational time of workflow tasks may be longer due to communication with storage systems and cause them to approach the workflow task timeout or exceed it.

Describe the solution you'd like

When approaching the workflow task timeout, the worker should log information that may contribute to the workflow task duration, for example:

  • Total wall clock time for external storage download
  • Total number of payloads downloaded
  • Total size of payloads downloaded
  • Total wall clock time for external storage upload
  • Total number of payloads uploaded
  • Total size of payloads uploaded

The worker should emit this information at the info level when greater than 5s and warning level when greater than 10s. The worker should emit this information with the TMPRL1104 rule.

Per-SDK Tickets
  • Go -
  • temporalio/sdk-java#2883
  • temporalio/sdk-typescript#2066
  • Python -
  • .NET -
  • Ruby -
  • Rust -
  • PHP -
  • Temporal CLI -

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or specific SDK implementation. Start by selecting the applicable SDK ticket and locating its workflow-task completion path plus external-storage upload and download handling; read the TMPRL1104 rule for the logging convention. Done means the requested timing, count, and size information is emitted at the specified thresholds.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.