microsoftgraph / microsoftgraph/msgraph-sdk-java
What happened to DefaultLogger and the ability to set the logging level?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 444
- Forks
- 154
- Avg merge
- 18h 28m
- Merged PRs (30d)
- 4
Description
Expected behavior
The DefaultLogger class was removed as was the GraphServiceClient.builder() which had a logger() with no obvious replacement. Do we have to access low level OkHttp to add a logging interceptor? All I want to do is set logging to DEBUG vs. INFO based on the user's config.
Actual behavior
No way to easily set the logging level.
Steps to reproduce the behavior
I migrated from 5.77.0 to 6.6.0
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 comparing the 5.77.0 and 6.6.0 logging-related APIs, especially DefaultLogger, GraphServiceClient.builder(), and the logger() option. Check how the current SDK exposes OkHttp and determine what would provide configurable DEBUG versus INFO logging without requiring low-level access; done means users have an obvious supported replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100