c54c569f30
Completed clean root directory structure: - Root now contains only: .git, .env, docs/, orig/ - Moved all remaining files and directories to orig/: - Config files (.claude, .dockerignore, .drone.yml, etc.) - All .env variants (except active .env) - Git config (.gitconfig, .github, .gitignore, etc.) - Tool configs (.golangci.yml, .revive.toml, etc.) - Documentation (*.md files, @prompts) - Build files (Dockerfiles, Makefile, go.mod, go.sum) - Docker compose files - All source directories (scripts, tests, tools, etc.) - Runtime directories (logs, monitoring, reports) - Dependency files (node_modules, lib, cache) - Special files (--delete) - Removed empty runtime directories (bin/, data/) V2 structure is now clean: - docs/planning/ - V2 planning documents - orig/ - Complete V1 codebase preserved - .env - Active environment config (not in git) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
1.1 KiB
1.1 KiB
You are an expert in Go error handling and logging best practices. I'm building an MEV bot in Go that needs robust error handling and comprehensive logging for production deployment.
I need help with:
- Implementing structured logging throughout the application
- Creating meaningful error messages for debugging
- Implementing retry mechanisms for transient failures
- Handling fatal errors gracefully
- Implementing circuit breakers for external services
- Creating health checks and metrics
Please provide production-ready Go code that:
- Uses a structured logging library (like zap or logrus)
- Implements comprehensive error wrapping and context
- Includes retry mechanisms with exponential backoff
- Handles fatal errors gracefully with proper cleanup
- Follows Go best practices for error handling
- Is optimized for performance
- Includes comprehensive comments
The code should:
- Log at appropriate levels (debug, info, warn, error)
- Include contextual information in log messages
- Implement circuit breakers for RPC connections
- Handle timeouts appropriately
- Provide health check endpoints
- Export metrics for monitoring