Configure Alloy to collect profiling data in Docker Compose setups#227
Merged
Configure Alloy to collect profiling data in Docker Compose setups#227
Conversation
ppcano
force-pushed
the
pepe/alloy-pyroscope
branch
from
341fb7d to
9054510
Compare
Contributor
|
No impact on the demoinfra deployment, it uses its own alloy config. As a general note: alloy configs no longer have the |
Lantero
approved these changes
Jul 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.