Dev tracker: Load and performance testing toolkit

[kristopherjturner]

Solution: Load and Performance Testing Toolkit for Azure Local

Tracking issue for the overall development of the load testing toolkit.

Current Status

• Repository structure and standards (Plan 1)
• MkDocs Material documentation site deployed (Plan 2 — migrated from AsciiDoc)
• CI/CD with GitHub Actions (deploy-docs.yml)
• Vale linting integrated
• Documentation migrated from AsciiDoc to Markdown (26 files)
• Draw.io diagrams preserved in assets/diagrams/
• Core framework — src/core/ modules
• Infrastructure provisioning — VM deployment for load testing
• Tool integrations:
  • FIO (storage I/O benchmarking)
  • HammerDB (database load testing)
  • iPerf (network throughput testing)
  • stress-ng (CPU/memory stress testing)
  • VMFleet (storage fleet testing)
• Monitoring collectors and dashboards
• Report generation from test results
• Profile-based test configurations
• Credential management
• Pipeline integration examples
• Alerting thresholds and rules
• Documentation — tool-specific guides
• Documentation — operations runbooks

Architecture

Multi-tool load testing framework with centralized config, monitoring, and reporting:

• src/core/ — Core framework modules
• src/infrastructure/ — VM/resource provisioning
• config/ — Profiles, credentials, cluster configs
• monitoring/ — Collectors, dashboards, alerts
• reports/ — Templates and generated reports