-
Notifications
You must be signed in to change notification settings - Fork 235
Add detailed logs from the MCP Server #778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
anannya03
wants to merge
13
commits into
microsoft:main
Choose a base branch
from
anannya03:live-tests-debug_logs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
e5fc2e4
merge conflict 1
anannya03 22ed466
changed verbose to trace
anannya03 2a9a7c5
Changed fileappend to streamwriter
anannya03 969590e
renamed file logger
anannya03 621bf75
default value of log level set to null
anannya03 dffbee1
removed verbose flag
anannya03 c5b0238
used the logging mechanism from asp.net
anannya03 0b56126
added file path to appsettings
anannya03 1351f6b
deleted wrong appsetting
anannya03 b64199b
updated azmcp and dotnet format
anannya03 dfcb3ed
Merge branch 'main' into live-tests-debug_logs
anannya03 c7eec5c
reverted live.yml changes
anannya03 b12b0bb
adding the yml change back
anannya03 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can have a conversation offline if it is easier but I was hoping that we wouldn't have to add these switches.
Using a custom ILogger, we can leverage existing infrastructure to output logs. The user experience here is to do
azmcp.exe server start --log-level debug
. But this only applies to the logger we wrote, the settings won't also apply to the "EventSourceLogger" or any other ILogger.I was hoping that an end user would be able to do something like:
set Logging__LogLevel__Default=Debug ./azmcp.exe server start
And this log level would apply to your new logger, and also the EventSourceLogger, any other Console logger, possibly a file logger if there is one.
Or they can use the same configuration system to be more granular about their logging. There's a bigger example here: Configure Logging
The bonus would be that they wouldn't have to learn something new about our logging because it uses the same configuration as other .NET loggers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or if you used the
[ProviderAlias("AzureMcpDebugLogger")]
or something, they could configure our logger via:set Logging__AzureMcpDebugLogger__LogLevel=Debug