Skip to content

Conversation

@Dumbris
Copy link
Contributor

@Dumbris Dumbris commented Jul 3, 2025

  • Bug fix for Quarantine Servers (0) after app start. Improvements in state management for tray UI updates.
  • Update autostart menu item icons for macOS to improve visual clarity and user experience.

Dumbris added 4 commits July 3, 2025 16:55
…d monitoring. Added detailed debug and error messages in GetQuarantinedServers and ListQuarantinedUpstreamServers methods, along with improvements in state management for tray UI updates.
…osity and improve clarity. Removed redundant debug messages and streamlined cache checks for better performance.
…s, enhancing visual clarity and consistency.
@Dumbris Dumbris merged commit 91c98cb into main Jul 3, 2025
31 checks passed
@Dumbris Dumbris deleted the bugfix/menu-fixes branch July 14, 2025 08:53
rannow pushed a commit to rannow/mcpproxy-go that referenced this pull request Sep 23, 2025
- Bug fix for Quarantine Servers (0) after app start. Improvements in state management for tray UI updates.
- Update autostart menu item icons for macOS to improve visual clarity and user experience.
Dumbris added a commit that referenced this pull request Nov 3, 2025
… (Issue #8)

Added detailed structured logging with metrics tags for complete observability
of Docker recovery operations. All recovery events now emit metrics for
monitoring and analysis.

Changes:
- Added startup logging of Docker recovery configuration
- Log existing recovery state on startup for visibility
- Added detailed success metrics logging:
  - Total attempts, duration, average interval
  - Resumed from attempt count
  - Intervals used during recovery
- Added retry metrics logging for each attempt:
  - Current attempt number
  - Elapsed time since recovery started
  - Next retry interval
  - Error details
- Added reconnection phase metrics:
  - Success: reconnect attempt, max attempts
  - Failure: attempts exhausted
- All metrics logs tagged with "metric_type" for easy filtering:
  - docker_recovery_success
  - docker_recovery_retry
  - docker_recovery_reconnect_success
  - docker_recovery_reconnect_failure

Benefits:
- Easy monitoring via log aggregation tools (grep, Splunk, etc.)
- Complete audit trail of recovery attempts
- Performance analysis of recovery intervals
- Failure investigation with detailed context
- Persistent state file provides queryable metrics snapshot
- All E2E tests passing (25/25)

Example metrics query:
  grep 'metric_type.*docker_recovery' /path/to/logs/*.log

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant