Skip to content

Add per-phase Prometheus analysis and consistent phase logging to loa…#179

Open
akrzos wants to merge 1 commit into
redhat-performance:mainfrom
akrzos:phased-prometheus-analysis-and-logging
Open

Add per-phase Prometheus analysis and consistent phase logging to loa…#179
akrzos wants to merge 1 commit into
redhat-performance:mainfrom
akrzos:phased-prometheus-analysis-and-logging

Conversation

@akrzos

@akrzos akrzos commented Jun 18, 2026

Copy link
Copy Markdown
Member

Extract launch_prometheus_analysis() into shared utils/analysis.py module
used by both acm-deploy-load.py and acm-telco-core-load.py. Add phased
workload structure (Idle Baseline, Cluster Deployment, Soak Baseline) with
automatic background Prometheus analysis at phase boundaries for resource
consumption comparison testing. Align logging, report generation, and section
naming across both load tools.

  • Add -k/--kubeconfig and --no-prometheus-analysis CLI args to acm-deploy-load.py
  • Run 3 background analyses: idle-baseline, cluster-deployment, soak-baseline
  • Add periodic countdown logging during idle and soak baseline phases
  • Consolidate workload parameter logging into structured block matching telco-core pattern
  • Move telco-core inline report to generate_telco_core_report() in utils/output.py
  • Rename generate_report() to generate_deploy_load_report() for clarity
  • Rename "Deployed Cluster Orchestration" to "Workload Parameters" in report
  • Align report section names: Workload Parameters, Workload Duration Results, Workload Phases
  • Enrich deploy-load report Workload Parameters with phase durations, wait configs, and cluster details

@akrzos akrzos force-pushed the phased-prometheus-analysis-and-logging branch 25 times, most recently from 1a8dec2 to 6823578 Compare June 22, 2026 18:06
… load tools

Extract launch_prometheus_analysis() into shared utils/analysis.py module
used by both acm-deploy-load.py and acm-telco-core-load.py. Add phased
workload structure (Idle Baseline, Cluster Deployment, Soak Baseline) with
automatic background Prometheus analysis at phase boundaries for resource
consumption comparison testing. Align logging, report generation, and section
naming across both load tools.

- Add -k/--kubeconfig and --no-prometheus-analysis CLI args to acm-deploy-load.py
- Run 3 background analyses: idle-baseline, cluster-deployment, soak-baseline
- Add periodic countdown logging during idle and soak baseline phases
- Consolidate workload parameter logging into structured block matching telco-core pattern
- Move telco-core inline report to generate_telco_core_report() in utils/output.py
- Rename generate_report() to generate_deploy_load_report() for clarity
- Rename "Deployed Cluster Orchestration" to "Workload Parameters" in report
- Align report section names: Workload Parameters, Workload Duration Results, Workload Phases
- Enrich deploy-load report Workload Parameters with phase durations, wait configs, and cluster details

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@akrzos akrzos force-pushed the phased-prometheus-analysis-and-logging branch from 6823578 to 9f5568d Compare June 22, 2026 18:20
@akrzos akrzos marked this pull request as ready for review June 22, 2026 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant