You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 20b8e86
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/_server/logging.md
+37-24Lines changed: 37 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,8 +35,8 @@ The SDK supports 8 log levels with increasing severity:
35
35
36
36
## How Logging Works
37
37
38
-
1.**Client Configuration**: The client sends a `logging/setLevel` request to configure the minimum log level
39
-
2.**Server Filtering**: The server only sends log messages at the configured level or higher severity
38
+
1.**Client Configuration**: The client sends a `logging/setLevel` request to configure the minimum log level for its session only
39
+
2.**Server Filtering**: The server only sends session-scoped log messages at the configured level or higher severity
40
40
3.**Notification Delivery**: Log messages are sent as `notifications/message` to the client
41
41
42
42
For example, if the client sets the level to `"error"` (severity 4), the server will send messages with levels: `error`, `critical`, `alert`, and `emergency`.
@@ -45,44 +45,57 @@ For more details, see the [MCP Logging specification](https://modelcontextprotoc
45
45
46
46
**Usage Example:**
47
47
48
-
The client first configures the level with a `logging/setLevel` request:
48
+
The client first configures the level for its session with a `logging/setLevel` request:
0 commit comments