Skip to content

feat(asb): profiling#1130

Open
binarybaron wants to merge 1 commit into
masterfrom
claude/asb-pyroscope-profiling
Open

feat(asb): profiling#1130
binarybaron wants to merge 1 commit into
masterfrom
claude/asb-pyroscope-profiling

Conversation

@binarybaron

Copy link
Copy Markdown

No description provided.

Serve jemalloc heap and pprof CPU profiles from the ASB metrics server at
/debug/pprof/{heap,profile} behind a network.profiling flag, with an opt-in
orchestrator Alloy agent that scrapes them into Grafana Pyroscope.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit e2ab80c. Configure here.

build_alloy_config(pyroscope, recipe.ports.asb_metrics_port),
)
.expect("Failed to write alloy.alloy");
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pyroscope skips config patch

Medium Severity

Enabling Pyroscope via the orchestrator writes alloy.alloy and compose changes but does not update an existing ASB config.toml with network.profiling or prometheus_port. The metrics HTTP server stays off or serves without pprof routes, so Alloy scrapes fail while profiling appears enabled.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit e2ab80c. Configure here.

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