Skip to content

Configure Alloy to collect profiling data in Docker Compose setups #227

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 25, 2025

Conversation

ppcano
Copy link
Collaborator

@ppcano ppcano commented Jul 24, 2025

This PR simplifies the configuration of the Grafana Cloud Docker Compose setup by removing the need to manually set the Pyroscope user, endpoint, and password.

It also aligns the setup with the usage of Alloy for collecting telemetry data.

We should review whether the changes to the Alloy configuration have any impact on Kubernetes deployments.
cc @theSuess @federicotdn

Update: I just noticed that the Kubernetes setup uses its own Alloy configuration here. So I believe it’s safe to merge this as-is.

@ppcano ppcano requested a review from a team as a code owner July 24, 2025 10:16
@ppcano ppcano force-pushed the pepe/alloy-pyroscope branch from 341fb7d to 9054510 Compare July 24, 2025 22:05
@theSuess
Copy link
Contributor

No impact on the demoinfra deployment, it uses its own alloy config.

As a general note: alloy configs no longer have the .river suffix but use .alloy instead

@ppcano ppcano merged commit 0e1aa3c into main Jul 25, 2025
13 checks passed
@ppcano ppcano deleted the pepe/alloy-pyroscope branch July 25, 2025 08:34
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.

3 participants