vibeMK v0.2.0 - Working CheckMK Metrics API

🎯 vibeMK v0.2.0 - Working CheckMK Metrics API

✨ Major New Features

📊 Performance Metrics Retrieval

• Working CheckMK REST API integration for historical performance data
• Support for all service metrics (response_time, response_size, time_http_headers, time_http_body)
• Rich data analysis with min/max/avg statistics over time periods
• Multiple time ranges supported: 1h, 4h, 24h, 7d, 30d

🔧 Technical Implementation

• Correct API Endpoint: POST domain-types/metric/actions/get/invoke
• Proper timestamp format: Datetime strings ('%Y-%m-%d %H:%M:%S')
• Response structure: Handle metrics list with data_points arrays
• Error handling: Filter None values for statistical calculations

🧪 Verified Working

Test Configuration:

• Host: www.google.de
• Service: HTTPS Webservice
• Metrics: All 4 available metrics successfully retrieving data
• Data: 60 data points over 1-hour periods

Example Usage:

{
    'name': 'vibemk_get_service_metrics',
    'arguments': {
        'host_name': 'www.google.de',
        'service_description': 'HTTPS Webservice',
        'metric_name': 'response_time',
        'time_range': '1h'
    }
}

🐛 Bug Fixes

• Fixed deprecated webapi.py endpoint (returned HTTP 410 Gone)
• Fixed Unix timestamp format rejection by CheckMK API
• Fixed response parsing expecting curves vs actual metrics structure
• Fixed points vs data_points field name mismatch

📝 Documentation Updates

• Complete API format examples in CLAUDE.md
• Working endpoint documentation
• Troubleshooting guides for common issues

🏷️ Previous Releases

• v0.1.x: Basic CheckMK integration with host/service status, folder operations, rule management
• v0.2.0: Added working performance metrics retrieval (this release)

---

Full Changelog: v0.1.0...v0.2.0