Add tracing to observability
Maintainers usually reply within 3 days
@patbeqo is already working on this.
Since Sep 28, 2026.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- observability
Research direction
Start with the linked discussion in pull request #39 and determine what support for distributed tracing with otel should cover. The issue names no files or tests, so inspect the repository's language skills and existing observability guidance first; done means the requested tracing guidance is supported and verifiable.
Written by the indexing model from the issue text.
Description
Language skills do not explain how to use otel for distributed tracing. Add support for this.
Originally posted by @cecilphillip in https://github.com/temporalio/skill-temporal-developer/pull/39#discussion_r2991274458
- Dominant language
- No language data
- Stars
- 230
- Forks
- 31
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from temporalio/skill-temporal-developer
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
temporalio/skill-temporal-developer#109 · 1 comment ·
Maintainers usually reply within 3 days
-
Improve Go Saga PatternPossibly taken @brianstrauch claimed this 12 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/skill-temporal-developer#68 ·
Maintainers usually reply within 3 days
-
Add generalized metrics supportPossibly taken @patbeqo claimed this 12 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
temporalio/skill-temporal-developer#62 · 1 assignee ·
Maintainers usually reply within 3 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
temporalio/skill-temporal-developer#54 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
temporalio/skill-temporal-developer#29 ·
Maintainers usually reply within 3 days
All issues in temporalio/skill-temporal-developer
Similar issues
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mastra-ai/mastra#26635 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage receiver/dockerstats
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
open-telemetry/opentelemetry-collector-contrib#51948 · 1 comment ·
Maintainers usually reply within 1 day
-
template: humanize prints 1000k instead of 1M for values that round up to the next prefixPossibly taken @Rakshit-gen claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
prometheus/prometheus#19984 ·
Maintainers usually reply within 1 day
-
[Bug]: ActionObservations.emitSafely swallows event-delivery exception (no message, no stack trace)Possibly taken @amyaxy claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
agentscope-ai/agentscope-java#3475 ·
Maintainers usually reply within 1 day
-
bug(pkg/runtime): Shutdown() returns only last provider error, drops othersPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-telemetry/opentelemetry-go-compile-instrumentation#1467 ·
Maintainers usually reply within 3 days