feat: implement ow-exporter for Overwatch 2 profile statistics

[lexfrei]

Implement ow-exporter for Overwatch 2 Profile Statistics

Overview

Create a new Overwatch 2 statistics exporter that scrapes player profiles and exposes metrics via Prometheus. This replaces the old OW1 exporter that was removed.

Analysis Completed ✅

• Downloaded and analyzed two sample profiles
• Identified platform separation (PC/Console)
• Found game mode separation (Quick Play/Competitive)
• Mapped 15 core metrics with CSS selectors
• Confirmed HTML parsing approach (no headless browser needed)

Technical Requirements

Architecture

cmd/ow-exporter/
├── main.go                    # HTTP server + CLI
├── api/                      # REST API for user management
├── scraper/                  # HTML parsing and HTTP client  
├── storage/                  # SQLite for users, memory cache for stats
├── metrics/                  # Prometheus exporter
├── models/                   # Data structures
└── config/                   # Configuration

Features

• Platform support (PC/Console)
• Game mode support (Quick Play/Competitive)
• 15 hardcoded metrics (time played, win rate, etc.)
• REST API for user management
• SQLite storage for persistence
• Prometheus metrics export
• Background scheduler (5min intervals)
• Rate limiting and error handling

Prometheus Labels

ow_hero_time_played_seconds{
    username="player1",
    hero="mercy", 
    platform="pc",        # "pc" | "console"
    gamemode="competitive" # "quickplay" | "competitive"
}

API Endpoints

• GET /api/users - list users
• POST /api/users - add user (username + profile_id)
• PUT /api/users/{username} - update user
• DELETE /api/users/{username} - remove user
• GET /metrics - Prometheus metrics
• GET /health - health check

Implementation Plan

1. Create basic project structure
2. Implement HTML parser with platform support
3. Add SQLite storage for user management
4. Create REST API endpoints
5. Implement Prometheus metrics exporter
6. Add background scheduler
7. Add error handling and rate limiting
8. Update container build configuration
9. Add documentation and examples

Success Criteria

• Can add users via REST API
• Automatically scrapes profiles every 5 minutes
• Exports Prometheus metrics with platform/gamemode labels
• Handles both PC and Console statistics
• Supports Quick Play and Competitive modes
• Works with current Overwatch 2 profile URLs

Test Profile URLs

• https://overwatch.blizzard.com/en-us/career/de5bb4aca17492e0bba120a1d1%7Ca92a11ef8d304356fccfff8df12e1dc6/
• https://overwatch.blizzard.com/en-us/career/c14aad9eba729abefdf565bdd606a600%7C20e30637fb9054272d5bf9529de8bc70/

This issue will track the complete implementation of the new ow-exporter.

[lexfrei]

🚀 Progress Update: Initial Implementation Started

✅ Completed Steps

Branch & PR Created:

• Created feature branch:
• Created PR feat: implement ow-exporter for Overwatch 2 statistics #440 with initial implementation structure
• Added comprehensive project documentation

Analysis Phase Complete:

• Downloaded and analyzed 2 sample Overwatch profiles
• Identified platform separation: PC (mouseKeyboard-view) vs Console (controller-view)
• Found game mode separation: Quick Play vs Competitive
• Mapped 15 core metrics with CSS selectors and Prometheus names
• Confirmed HTML parsing approach (no headless browser needed)

Project Structure:

🎯 Next Implementation Phase

Core Components to Build:

1. REST API - User management endpoints ()
2. SQLite Storage - Persistent user database
3. Background Scheduler - 5-minute profile scraping intervals
4. Prometheus Exporter - endpoint with full labels
5. Rate Limiting - Blizzard-friendly request throttling

Prometheus Labels Preview:

📋 Implementation Checklist

• Platform analysis and CSS selector mapping
• Project structure and documentation
• HTML parser architecture
• REST API implementation
• SQLite user storage
• Background profile scraper
• Prometheus metrics exporter
• Container build configuration

PR Ready for Review: #440
Continue tracking progress here for each implementation milestone.

[lexfrei]

✅ Compilation Issues Fixed

Fixed compilation errors:

• Resolved main function conflict between main.go and parser.go
• Removed unused variables in parser example
• Added missing dependencies via go mod tidy
• Added goquery dependency for HTML parsing

Build Status: ✅ Successfully compiles and runs

Dependencies Added:

• github.com/PuerkitoBio/goquery v1.10.3 - HTML parsing
• github.com/andybalholm/cascadia v1.3.3 - CSS selector support

PR Updated: #440 now has clean compilation with no errors.

Ready for next phase: REST API implementation and SQLite storage.

[lexfrei]

🎯 Major Progress: REST API Server Implementation Complete

✅ HTTP Server with Echo Framework

Implemented full REST API server using Echo (already in project dependencies) with slog structured logging.

Features Added:

• Echo Web Framework: Following project standards (same as me-site)
• Structured Logging: Using slog with JSON output
• Graceful Shutdown: Signal handling with 10s timeout
• Middleware Stack: Logger, Recovery, CORS
• Environment Config: PORT env var support (default: 9420)

🔗 API Endpoints Implemented

📊 Server Logs (slog structured)

✅ Quality Improvements

• No Binary Commits: Added ow-exporter to .gitignore
• Project Standards: Consistent with me-site Echo usage
• Clean Dependencies: Added only required Echo middleware via go mod vendor

🚀 Next Implementation Phase

1. SQLite Storage - User persistence layer
2. Background Scraper - Periodic profile fetching
3. Real Prometheus Metrics - Hero statistics export
4. Rate Limiting - Blizzard-friendly requests

Current Status: Fully functional HTTP API server ready for business logic implementation.

PR Updated: #440 with working REST API server

[lexfrei]

🐳 Containerization Complete

✅ Container Build System

Added complete containerization following project standards:

Containerfile Features:

• Base Images: golang:1.25.1-alpine3.22 → scratch
• Security: Runs as nobody user (non-root)
• Compression: UPX with --best --lzma for minimal size
• SSL Support: Includes CA certificates for HTTPS API calls
• Port: 9420 exposed for HTTP server

🔄 CI/CD Pipeline

GitHub Actions Workflow (.github/workflows/ow-exporter.yaml):

• Multi-platform: linux/amd64, linux/arm64
• Registry: GitHub Container Registry (ghcr.io/lexfrei/ow-exporter)
• Triggers: Changes to cmd/ow-exporter/, build/ow-exporter/, go.mod, go.sum
• Conditional Push: Only on master branch (PRs build but don't push)

📦 Container Usage

30238da2f6964febced66d28205ff1e1ac27cfc27c1d12771df4981730c25135

📚 Documentation Updates

• cmd/ow-exporter/README.md: Added Docker usage examples
• Main README.md: Added ow-exporter to Web Services section
• Status: 🚧 Development (consistent with current implementation)

🚀 Ready for Production

• ✅ Automated builds on every commit
• ✅ Multi-platform support (ARM64 + AMD64)
• ✅ Security best practices (scratch base, non-root user)
• ✅ Minimal footprint (compressed Go binary)
• ✅ Environment configuration (PORT env var)

Next Phase: SQLite storage and background scraper implementation

Container Registry: ghcr.io/lexfrei/ow-exporter