vaadin / vaadin/observability-kit
Add user information to traces
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7
- Forks
- 5
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 25
Description
Providing user information would make it easier to debug issues reported by specific customers / users. This could either be the username, or the user id. We probably want to set this as early as possible, and as context, so that nested spans inherit the attribute.
This depends on what auth mechanism / framework the application uses. In a first step we could add support for Spring applications, which seem to have some generic mechanisms for retrieving user info.
This might require some more research regarding security / privacy implications.
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
Start by researching how Spring applications expose authenticated user information and review the linked Spring Security reference. Then assess the security and privacy implications of adding a username or user ID to trace context. Done should define and implement a supported Spring integration with inherited trace attributes and appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100