feat(activity): expand activity log with new event types (Spec 024) #254
Conversation
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
Deploying mcpproxy-docs with
|
| Latest commit: |
7886ccb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8f49384a.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://024-expand-activity-log.mcpproxy-docs.pages.dev |
Dumbris
force-pushed
the
024-expand-activity-log
branch
from
81e119e to
b3dd605
Compare
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 20970324618 --repo smart-mcp-proxy/mcpproxy-go
|
Add comprehensive activity logging for system lifecycle, internal tool calls, and configuration changes: - Add 4 new activity types: system_start, system_stop, internal_tool_call, config_change - Implement multi-type filtering with OR logic (comma-separated types) - Log system startup/shutdown events with version and duration metadata - Log all internal MCP tool calls (retrieve_tools, call_tool_*, code_execution, upstream_servers, quarantine_security, list_registries, search_servers, read_cache) - Log configuration changes with action, affected entity, and changed values Web UI enhancements: - Multi-select dropdown for type filtering with checkboxes - Intent column with operation type badges and tooltips - Sortable columns (timestamp, type, server, status, duration) - Activity Log enabled in sidebar navigation CLI enhancements: - Support comma-separated --type values for multi-type filtering - Updated help text with new event types Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Dumbris
force-pushed
the
024-expand-activity-log
branch
from
b3dd605 to
013da07
Compare
…Spec 024) - Log connection errors (connecting, disconnected, no client) to activity - Add sessions filter dropdown with client name + session ID suffix - Add arguments parameter to tool call activity events - Add arguments/response to internal tool call events - Add SSE listeners for internal_tool_call, system_start/stop, config_change - Log enable/disable server events as config changes Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…ec 024) - Fix SSE event listeners for system lifecycle events - Changed activity.system_start to activity.system.start (matches backend) - Changed activity.system_stop to activity.system.stop (matches backend) - Expand Activity.vue handlers to detect all event type fields - internal_tool_call: internal_tool_name, target_server, target_tool - config_change: action, affected_entity - system_start/stop: version, listen_address, reason - Fix CLI activity watch to show all event types (not just .completed) - Added dedicated formatters for each event type - Shows config_change, system_start, system_stop, policy_decision - Improved filtering for server name across different event types Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
… log (Spec 024) Successful call_tool_* internal tool calls now excluded by default from activity listings (Web UI, CLI, API) to avoid duplicates alongside their corresponding upstream tool_call entries. Failed call_tool_* calls are still shown since they have no corresponding tool_call entry. ## Changes - Add ExcludeCallToolSuccess filter to storage layer (default: true) - Add include_call_tool query parameter to REST API - Filter successful call_tool_* in CLI activity watch command - Add E2E tests for activity log filtering scenarios - Update spec 024, docusaurus docs, and swagger.yaml Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Remove Tool Calls History page (ToolCalls.vue) entirely - Update Dashboard and Sessions "View Calls" links to Activity Log - Activity Log now accepts ?session= query param for filtering - Update sidebar navigation to show Activity Log instead of Tool Call History - Fix internal tool call logging to include arguments and response JSON (retrieve_tools, read_cache, upstream_servers, quarantine_security, search_servers, list_registries now log full request/response data) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
technicalpickles
pushed a commit
to technicalpickles/mcpproxy-go
that referenced
this pull request
Jan 21, 2026
…mart-mcp-proxy#254) * feat(activity): expand activity log with new event types (Spec 024) Add comprehensive activity logging for system lifecycle, internal tool calls, and configuration changes: - Add 4 new activity types: system_start, system_stop, internal_tool_call, config_change - Implement multi-type filtering with OR logic (comma-separated types) - Log system startup/shutdown events with version and duration metadata - Log all internal MCP tool calls (retrieve_tools, call_tool_*, code_execution, upstream_servers, quarantine_security, list_registries, search_servers, read_cache) - Log configuration changes with action, affected entity, and changed values Web UI enhancements: - Multi-select dropdown for type filtering with checkboxes - Intent column with operation type badges and tooltips - Sortable columns (timestamp, type, server, status, duration) - Activity Log enabled in sidebar navigation CLI enhancements: - Support comma-separated --type values for multi-type filtering - Updated help text with new event types Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(activity): log early tool call failures and add sessions filter (Spec 024) - Log connection errors (connecting, disconnected, no client) to activity - Add sessions filter dropdown with client name + session ID suffix - Add arguments parameter to tool call activity events - Add arguments/response to internal tool call events - Add SSE listeners for internal_tool_call, system_start/stop, config_change - Log enable/disable server events as config changes Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(activity): fix auto-refresh and CLI watch for new event types (Spec 024) - Fix SSE event listeners for system lifecycle events - Changed activity.system_start to activity.system.start (matches backend) - Changed activity.system_stop to activity.system.stop (matches backend) - Expand Activity.vue handlers to detect all event type fields - internal_tool_call: internal_tool_name, target_server, target_tool - config_change: action, affected_entity - system_start/stop: version, listen_address, reason - Fix CLI activity watch to show all event types (not just .completed) - Added dedicated formatters for each event type - Shows config_change, system_start, system_stop, policy_decision - Improved filtering for server name across different event types Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(activity): filter out duplicate call_tool_* entries from activity log (Spec 024) Successful call_tool_* internal tool calls now excluded by default from activity listings (Web UI, CLI, API) to avoid duplicates alongside their corresponding upstream tool_call entries. Failed call_tool_* calls are still shown since they have no corresponding tool_call entry. ## Changes - Add ExcludeCallToolSuccess filter to storage layer (default: true) - Add include_call_tool query parameter to REST API - Filter successful call_tool_* in CLI activity watch command - Add E2E tests for activity log filtering scenarios - Update spec 024, docusaurus docs, and swagger.yaml Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(activity): replace Tool Calls History with Activity Log (Spec 024) - Remove Tool Calls History page (ToolCalls.vue) entirely - Update Dashboard and Sessions "View Calls" links to Activity Log - Activity Log now accepts ?session= query param for filtering - Update sidebar navigation to show Activity Log instead of Tool Call History - Fix internal tool call logging to include arguments and response JSON (retrieve_tools, read_cache, upstream_servers, quarantine_security, search_servers, list_registries now log full request/response data) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: regenerate OpenAPI spec Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
system_start,system_stop,internal_tool_call,config_change--typevalues for multi-type filteringTest plan
go test ./internal/...)./scripts/run-linter.sh)./scripts/test-api-e2e.sh)🤖 Generated with Claude Code