fix(web-probe): correlate CPU samples with performance windows

This commit is contained in:
Codex
2026-07-02 15:41:39 +00:00
parent d9b3fc79e1
commit 225e3e6836
5 changed files with 725 additions and 31 deletions
@@ -2,7 +2,7 @@
// Responsibility: Analyzer recent-window, page provenance, and Navigation Timing API performance source fragment.
export function nodeWebObserveAnalyzerWindowPageSource(): string {
return String.raw`function buildRecentAnalysisWindow({ samples, control, network, consoleEvents, errors, artifacts, browserProcessRows, performanceRows, manifest }) {
return String.raw`async function buildRecentAnalysisWindow({ samples, control, network, consoleEvents, errors, artifacts, browserProcessRows, performanceRows, manifest }) {
const latestSampleMs = latestTimestampMs(samples);
const windowMs = 5 * 60 * 1000;
const fromMs = Number.isFinite(latestSampleMs) ? latestSampleMs - windowMs : Number.NEGATIVE_INFINITY;
@@ -27,7 +27,7 @@ export function nodeWebObserveAnalyzerWindowPageSource(): string {
const runtimeAlerts = buildRuntimeAlerts(windowSamples, control, windowNetwork, windowConsole, windowErrors);
const apiDomLag = buildApiDomLagReport(windowSamples, windowNetwork);
const browserProcess = buildBrowserProcessReport(windowBrowserProcessRows);
const frontendPerformance = buildFrontendPerformanceReport(windowPerformanceRows, windowArtifacts, windowSamples, windowNetwork);
const frontendPerformance = await buildFrontendPerformanceReport(windowPerformanceRows, windowArtifacts, windowSamples, windowNetwork);
const findings = buildFindings(windowSamples, control, windowNetwork, windowErrors, sampleMetrics, promptNetwork, runtimeAlerts, pagePerformance, requestRate, pageProvenance, [], {}, apiDomLag, browserProcess, frontendPerformance);
return {
summary: {