Clayton Cornell

@mattdurham What should we do with this PR? It depended on https://github.com/grafana/river/pull/42 but it looks like things have moved (will move?) over to Alloy?

Docs look ok Someone from @grafana/grafana-agent-maintainers shoudl take a quick look at this before we merge.

Doc content looks OK to me. It's over to @grafana/grafana-alloy-maintainers for code review now :-)

Ping for review? @grafana/grafana-agent-maintainers

> Has this change been released? I don't see it in the docs or the changelogs. It is in the `next` release, so for docs, you find the new content...

I've triggered a rebase to pull in the newly added shared community notifcation. The shortcode for the notification is included in a review suggestion. The rendered output looks like this:...

Looks like this has received an update now... https://grafana.com/docs/grafana-cloud/monitor-infrastructure/integrations/troubleshoot/install-troubleshoot-linux-alloy/ is the new URL @grvsoni does this cover what you were asking for?

Looks good. I know the descriptions in the shared content are unlikely to be seen anywhere, but... good habit to be consistent if we can and you never know what...

> We may want to mention, that for alloy, users need extra argument `--stability.level=public-preview` Good point. Both `pyroscope.write` and `pyroscope.scrape` are in Public preview. If you don't set the `stability.level`...

> > We may want to mention, that for alloy, users need extra argument `--stability.level=public-preview` > > Would users need to use this flag every time they start Alloy? Is...