Ensure JobClusterActor's logs always contain the clusterName for easy debugging
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 224
- Avg merge
- 22h 46m
- Merged PRs (30d)
- 1
Description
Context
This is similar to https://github.com/Netflix/mantis/issues/384 but in the context of the JobClusterActor.
Expected Behavior
Every emitted logline from the JobClusterActor has the cluster identifier appended automatically.
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 JobClusterActor entry point and review issue #384 for related context. Trace the actor's emitted log lines and verify that every one includes the clusterName identifier; the issue is done when this holds consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100