temporalio / temporalio/sdk-java
MDC custom naming convention
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
We want to have an ability (extension point) to control default MDC keys. Now they are statically defined in workers.
Why it's important:
- we have multiple stacks: Java + Python and trying to unite our services logs/metrics/traces with single naming conventions.
- we have logging based integration: sentry, metrics from logs, etc.
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 locating the workers where the default MDC keys are statically defined. Review how those keys are used across logging, metrics, and tracing, then determine the extension point's required scope from the issue. Done means services can supply a custom naming convention for the default MDC keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100