blaze-performance-tester 3.1.39 → 3.1.41
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli.js +9 -6
- package/dist/index.win32-x64-msvc.node +0 -0
- package/package.json +1 -1
package/dist/cli.js
CHANGED
|
@@ -98,7 +98,7 @@ async function generateGeminiRCA(history, finalSummary, errorLogs) {
|
|
|
98
98
|
).join("\n");
|
|
99
99
|
const uniqueLogs = Array.from(new Set(errorLogs)).slice(0, 10).join("\n");
|
|
100
100
|
const prompt = `
|
|
101
|
-
You are an expert Performance & Systems Reliability Engineer. Analyze the following load test execution telemetry and logs:
|
|
101
|
+
You are an expert Performance & Systems Reliability Engineer. Analyze the following load test execution telemetry and logs to compose a full Root Cause Analysis (RCA) report featuring a Generative Incident Narrative timeline:
|
|
102
102
|
|
|
103
103
|
[LOAD SUMMARY METRICS]
|
|
104
104
|
- Unified Blaze Health Score: ${finalSummary.healthScore}/100
|
|
@@ -112,10 +112,13 @@ ${formattedHistory}
|
|
|
112
112
|
[UNIQUE LOG SAMPLES EXPLORATION]
|
|
113
113
|
${uniqueLogs || "No unique structural exceptions encountered."}
|
|
114
114
|
|
|
115
|
-
Provide a
|
|
116
|
-
|
|
117
|
-
Paragraph
|
|
118
|
-
|
|
115
|
+
Provide a comprehensive, highly technical Root Cause Analysis (RCA) report structured exactly as follows:
|
|
116
|
+
|
|
117
|
+
Paragraph 1 - GENERATIVE INCIDENT NARRATIVE: Write a clean, plain-English story of the incident that builds a chronological timeline of the failure event (e.g., "At 00:12s, traffic spiked by 40%. This caused database connection pool exhaustion, which triggered a cascading series of 504 errors on the checkout endpoint, ultimately hitting a knee-point crash at 500 virtual users."). Translate raw logs and metrics trends directly into an easy-to-read chronological story.
|
|
118
|
+
|
|
119
|
+
Paragraph 2 - TECHNICAL BOTTLENECK DIAGNOSIS: Diagnose the exact bottleneck point (CPU saturation, socket pool exhaustion, database lock contention, etc.) indicated by how latency changes dynamically alongside concurrency, and correlate unique structural exception/error patterns directly to the performance drops.
|
|
120
|
+
|
|
121
|
+
Paragraph 3 - ARCHITECTURAL SIZING RECOMMENDATIONS: Give concrete, infrastructure sizing or cloud architecture remediation recommendations based on the stress points found.
|
|
119
122
|
|
|
120
123
|
CRITICAL: Return ONLY plain paragraph text. Do not use markdown headers (###). If you use bold text, use standard HTML <strong> tags. Wrap lines cleanly.
|
|
121
124
|
`;
|
|
@@ -637,7 +640,7 @@ function exportHtmlDashboard(history, config, verdictReason, semanticReport, res
|
|
|
637
640
|
<td style="padding: 1.25rem 0.75rem; font-size: 1.2rem; font-weight: bold; color: #f8fafc;">${c.count}</td>
|
|
638
641
|
<td style="padding: 1.25rem 0.75rem; color: ${catColor}; font-weight: 600; font-size: 0.95rem;">${c.category}</td>
|
|
639
642
|
<td style="padding: 1.25rem 0.75rem;">
|
|
640
|
-
<span style="background: ${sevBg}; color: #ffffff; padding: 0.2rem 0.5rem; border-radius: 4px; font-size: 0.
|
|
643
|
+
<span style="background: ${sevBg}; color: #ffffff; padding: 0.2rem 0.5rem; border-radius: 4px; font-size: 0.7rem; font-weight: bold; letter-spacing: 0.05em;">${c.severity}</span>
|
|
641
644
|
</td>
|
|
642
645
|
<td style="padding: 1.25rem 0.75rem;">
|
|
643
646
|
<div style="background: #090d16; border-radius: 4px; padding: 0.6rem 0.8rem; border-left: 3px solid #1e293b; margin-bottom: 0.5rem;">
|
|
Binary file
|