temporalio / temporalio/sdk-java
Missing metric reporting in local activity execution
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Expected Behavior
temporal_activity_succeed_endtoend_latencytemporal_local_activity_execution_failed
are emitted correctly
Actual Behavior
They are missing in our production
You can see in the graph that the LA execution metrics are reported but not end to end. In fact, this is happening most of the time.
We also pretty sure there are many cases of LA execution failure but not reported based on our workflow history.
Steps to Reproduce the Problem
NA
Specifications
- Version:
1.22.3 - Platform:
Contributor guide
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
Start by tracing where the named local activity metrics, temporal_activity_succeed_endtoend_latency and temporal_local_activity_execution_failed, are emitted in the Java SDK. Compare those paths with the reported local activity execution metrics and verify behavior against workflow history; done means the missing success and failure metrics are emitted consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100