🚀 Quick Start Guide: Monitoring Specialist - CODI2 Core Development

Session Type: MONITORING-SPECIALIST (Primary Agent)
Focus Areas: CODI2 Monitoring System Core Functionality
File Boundaries: codi2/src/, codi2/metrics/, codi2/collectors/
Session Pattern: MONITORING-SPECIALIST-SESSION-$(date +%Y-%m-%d)-CODI2

⚡ Instant Session Startup

1. terminal Setup (30 seconds)

# Navigate to v4 root
cd /home/halcasteel/coditect.foundationdb.0001/build/decisions/v4

# Set unique session identity 
export SESSION_ID="MONITORING-SPECIALIST-SESSION-$(date +%Y-%m-%d)-CODI2"
source .codi/scripts/set-session-identity.sh "$SESSION_ID"

# Start monitoring infrastructure
source .codi/scripts/infrastructure/session-start-hook.sh

# Navigate to CODI2 directory
cd codi2

# Log session start
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: Starting CODI2 core development session" "SESSION_START"

2. Claim Your Domain (15 seconds)

# Claim primary file areas
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID claiming codi2/src/ for core CODI2 development" "FILE_CLAIM"
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID claiming codi2/metrics/ for metrics collection" "FILE_CLAIM"
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID claiming codi2/collectors/ for data aggregation" "FILE_CLAIM"

3. Read Core Documentation (2 minutes)

# Your primary agent guide
cat ../agents/coditect/monitoring-specialist.md

# CODI2 specific guidance
cat CLAUDE.md

# Current status and progress
cat ../ORCHESTRATOR-SESSION-STATUS-AGENT-REORGANIZATION.md | grep -A10 "CODI2"

🎯 Your Mission: CODI2 Core Functionality

Primary Responsibilities

Metrics Collection Engine: Real-time system metrics and performance data
Data Aggregation: Efficient processing and storage of monitoring data
API Endpoints: Metrics exposure for dashboards and alerts
Performance Optimization: < 1ms overhead, < 50MB memory usage

Quality Gates

✅ Metrics overhead < 1ms
✅ Memory usage < 50MB
✅ 99.9% uptime SLA
✅ Real-time data accuracy
✅ 95% test coverage

🤖 Sub-Agent Delegation Patterns

For Complex Rust Implementation

// When you need advanced Rust patterns
Task(
    description="Implement CODI2 metrics collection engine",
    prompt="Design efficient Rust binary for real-time metrics collection using tokio async patterns, FoundationDB integration, and concurrent data processing with minimal overhead.",
    subagent_type="rust-expert-developer"
)

For Performance Optimization

// When you need performance analysis
Task(
    description="Optimize CODI2 performance for production",
    prompt="Review memory usage patterns, CPU efficiency, async task scheduling, and concurrent processing. Focus on zero-copy deserialization and lock-free data structures.",
    subagent_type="rust-qa-specialist"
)

For Comprehensive Testing

// When you need testing strategy
Task(
    description="Create comprehensive CODI2 test suite",
    prompt="Design integration tests for metrics accuracy, load testing for high-volume scenarios, and reliability tests for system failures. Include FoundationDB integration tests.",
    subagent_type="testing-specialist"
)

📁 Key File Locations

Core CODI2 Source

codi2/src/
├── main.rs         # CLI entry point
├── lib.rs          # Core library
├── audit/          # Audit logging system
├── monitor/        # File monitoring
├── cli/            # Command handlers
├── metrics/        # Metrics collection (YOUR FOCUS)
├── collectors/     # Data aggregation (YOUR FOCUS)
└── server/         # API server components

Metrics System (NEW - Your Implementation)

codi2/metrics/
├── collector.rs    # Metrics collection engine
├── aggregator.rs   # Data aggregation
├── storage.rs      # FoundationDB integration
├── exporters/      # Prometheus, JSON exporters
└── schemas/        # Metrics data models

Data Collectors (NEW - Your Implementation)

codi2/collectors/
├── system.rs       # System metrics (CPU, memory)
├── application.rs  # App-specific metrics
├── network.rs      # Network performance
├── fdb.rs          # FoundationDB metrics
└── custom.rs       # User-defined metrics

🛠️ Essential Commands

Development Workflow

# Build CODI2 with metrics features
cargo build --features "metrics,collectors"

# Run with metrics collection
./codi2-latest monitor --metrics --collectors system,application

# Test metrics endpoints
curl http://localhost:8080/metrics

# Check performance
cargo bench --package codi2-metrics

Testing Commands

# Run metrics-specific tests
cargo test metrics::

# Integration tests with FoundationDB
cargo test --test integration_metrics -- --test-threads=1

# Performance benchmarks
cargo bench metrics_collection

Coordination Commands

# Check other active sessions
grep "SESSION_START" ../.codi/logs/codi-ps.log | tail -10

# Coordinate with API development
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: Metrics endpoints ready for API integration" "COORDINATE"

# Hand off completed modules
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: System metrics collector complete, ready for testing" "HANDOFF"

📊 Progress Tracking

Log Your Implementation Milestones

# Starting new metrics components
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: Implementing real-time metrics collection engine" "CREATE"

# Performance achievements
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: Metrics overhead 0.8ms, memory usage 45MB" "PERFORMANCE"

# Integration success
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: FoundationDB metrics storage integrated successfully" "INTEGRATE"

# Testing results
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: Load testing passed 10K metrics/sec" "TEST_PASS"

🔗 Integration Points

With RUST-DEVELOPER (API+WASM)

Metrics API: Provide /api/metrics endpoints for frontend consumption
WebSocket Metrics: Real-time metrics streaming
Authentication: Secure metrics access control

With ORCHESTRATOR

System Health: Overall platform monitoring
Quality Metrics: Development process tracking
Alert Coordination: Cross-system alert management

📈 Current CODI2 Status (Your Starting Point)

✅ Already Complete (Build On This)

Core binary v0.2.0 functional
FoundationDB integration working
File monitoring system active
WebSocket server operational
Basic CLI commands functional

🚧 Your Implementation Areas (0% Complete)

Metrics Collection Engine - Design and implement from scratch
Performance Monitoring - CPU, memory, network collectors
Data Aggregation - Efficient processing and storage
Export Interfaces - Prometheus, JSON, dashboard APIs
Real-time Streaming - Live metrics via WebSocket

📋 Implementation Roadmap

Phase 1: Metrics Foundation (Week 1)

Design metrics data models
Implement basic collection engine
FoundationDB storage integration
Unit tests for core functionality

Phase 2: Collectors (Week 2)

System metrics collector
Application metrics collector
Network performance collector
Custom metrics framework

Phase 3: Aggregation & Export (Week 3)

Data aggregation engine
Prometheus exporter
JSON API endpoints
Real-time WebSocket streaming

Phase 4: Production Ready (Week 4)

Performance optimization
Load testing validation
Production deployment
Monitoring dashboard integration

🚨 Emergency Procedures

Session Recovery

# If session gets disconnected
export SESSION_ID="MONITORING-SPECIALIST-SESSION-$(date +%Y-%m-%d)-CODI2"
cd /home/halcasteel/coditect.foundationdb.0001/build/decisions/v4/codi2
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: Session recovered, resuming CODI2 development" "SESSION_RECOVER"

Build Issues

# Log build problems
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: CODI2 build failed, investigating feature dependencies" "ERROR"

# Check dependencies
cargo check --features "metrics,collectors"

Performance Issues

# Log performance problems
../.codi/scripts/logging/actors/codi-log-ai.sh "$SESSION_ID: Metrics overhead exceeding 1ms target, optimizing" "OPTIMIZE"

🎯 Success Criteria

Your session is successful when:

✅ Metrics collection engine processes data with < 1ms overhead
✅ Memory usage stays under 50MB during operation
✅ System achieves 99.9% uptime during testing
✅ Real-time metrics stream accurately via WebSocket
✅ Integration tests pass with 95% coverage
✅ Prometheus export format validates correctly

Ready to revolutionize CODITECT monitoring? Start with terminal Setup and begin implementing!

⚡ Instant Session Startup​

1. terminal Setup (30 seconds)​

2. Claim Your Domain (15 seconds)​

3. Read Core Documentation (2 minutes)​

🎯 Your Mission: CODI2 Core Functionality​

Primary Responsibilities​

Quality Gates​

🤖 Sub-Agent Delegation Patterns​

For Complex Rust Implementation​

For Performance Optimization​

For Comprehensive Testing​

📁 Key File Locations​

Core CODI2 Source​

Metrics System (NEW - Your Implementation)​

Data Collectors (NEW - Your Implementation)​

🛠️ Essential Commands​

Development Workflow​

Testing Commands​

Coordination Commands​

📊 Progress Tracking​

Log Your Implementation Milestones​

🔗 Integration Points​

With RUST-DEVELOPER (API+WASM)​

With ORCHESTRATOR​

📈 Current CODI2 Status (Your Starting Point)​

✅ Already Complete (Build On This)​

🚧 Your Implementation Areas (0% Complete)​

📋 Implementation Roadmap​

Phase 1: Metrics Foundation (Week 1)​

Phase 2: Collectors (Week 2)​

Phase 3: Aggregation & Export (Week 3)​

Phase 4: Production Ready (Week 4)​

🚨 Emergency Procedures​

Session Recovery​

Build Issues​

Performance Issues​

🎯 Success Criteria​