v1.0.2
Release v1.0.2
Release Notes
This release introduces retry capabilities for failed checks and enhances the project documentation with visual branding and improved examples.
New Features
Retry Mechanism for Failed Checks
- Added configurable retry functionality to improve reliability of monitoring checks
- New configuration options
RetriesandRetryIntervalallow checks to automatically retry on failure - Failed checks will now retry up to the specified number of times with a configurable delay between attempts
- This reduces false alerts caused by temporary network issues or brief service interruptions
Improvements
Enhanced Documentation and Branding
- Added official Gogios logo and visual branding to README
- Improved configuration examples with retry settings demonstrated
- Added Taskfile.yml for streamlined build process using go-task
- Enhanced project description to better explain use cases and target audience
- Added reference to upcoming Gorum project for advanced clustering features
Better User Experience
- Improved error messages for dependency validation
- Added comprehensive documentation for NRPE remote monitoring setup
- Clarified high-availability setup instructions and trade-offs
Technical Improvements
Code Quality and Architecture
- Refactored check execution logic for better maintainability
- Split retry logic into separate function for cleaner code organization
- Improved concurrent check execution with proper resource management
- Enhanced timeout handling during check retries
Configuration Enhancements
- Better validation for check dependencies
- More descriptive error messages when configuration issues are detected
Documentation Updates
- Added detailed explanation of retry configuration options
- Improved examples showing real-world monitoring scenarios
- Enhanced troubleshooting guidance for common setup issues
- Better explanation of trade-offs between simplicity and features
This release maintains backward compatibility - existing configurations will continue to work without modification. The new retry features are optional and only activate when explicitly configured.