temporalio / temporalio/features
Customize activity failure logging (and more?)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Today SDKs log all activity failures, but some activity failures are intentional (e.g. for the activity-retry-based-polling pattern). So users want a way to not log some of these failures while still logging others. Also, some users want to customize the tags of logs or do other logging approaches. Users can do all of this today, but we also log in a way they can't disable.
Originally this issue suggested a full activity reporting handler, but now it seems wisest to allow users to disable our currently-forced implicit logging of activity failures so they can defer to their own logging code to do whatever they want.
Per-SDK Tickets
- Go -
- Java -
-
Core- N/A - TypeScript -
- Python -
- .NET -
- PHP -
-
Temporal CLI- N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the implicit activity-failure logging paths in the Go, Java, TypeScript, Python, and PHP SDKs, then review the existing discussion before defining a consistent opt-out behavior that preserves user-controlled logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, php, python, typescript
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100