Skip to content
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

Support for OpAMP to manage fleet of Alloy agents #1236

Open
X4mp opened this issue Jul 9, 2024 · 3 comments
Open

Support for OpAMP to manage fleet of Alloy agents #1236

X4mp opened this issue Jul 9, 2024 · 3 comments
Labels
enhancement New feature or request needs-attention

Comments

@X4mp
Copy link

X4mp commented Jul 9, 2024

Request

Hi,
It would be a great addition to the Grafana ecosystem if it would be possible to manage a fleet of Alloy agents via the Open Agent Management Protocol (OpAMP).
Being able to have a central management interface to manage all agents and their respective configurations would reduce the operational cost of running dozens or hundreds of Alloy agents across a large infrastructure.

Use case

We want to manage hundreds of telemetry agents via a central agent management service. This OpAMP server should allow to list all deployed agents and their active configuration as well as the bandwidth for ingested data to the Metric TSDB. A reference for this would be Splunk's Deployment Server or ObservIQ Bindplane. Latter one is a server implementation of OpAMP, but only provides support for their own telemetry collector.

Without a central management service, we are bound to Ansible to rollout and manage our agents. This works, but doesn't provide the same operational quality to immediately see the status of all agents and troubleshoot problems.

@X4mp X4mp added the enhancement New feature or request label Jul 9, 2024
@tpaschalis
Copy link
Member

Hey there @X4mp 👋

This is on our radar. We're experimenting the addition remote configuration/fleet management capabilities to Alloy with the remotecfg block.

As you've probably seen, the scope of OpAmp is really vast, so to to get us quickly off the ground we're using a custom Open Source protocol available over at https://github.com/grafana/alloy-remote-config. It only contains a single GetConfig endpoint right now, but will be a stepping stone to properly evaluating OpAmp for production workloads.

@X4mp
Copy link
Author

X4mp commented Jul 11, 2024

Hey @tpaschalis
That is incredible to hear. Thank you very much for being open and providing this understandable response.
Indeed have I seen the scope of OpAmp and I fully support your decision of going with the remote-config route. Even without full OpAmp support at the beginning, this will be a super important feature for us to remotely manage our Alloy agents!

Can you provide us with a rough estimate when we can expect the first parts being implemented and released with Alloy?
Really looking forward to this!

Best regards,
Roland

Copy link
Contributor

This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-attention
Projects
None yet
Development

No branches or pull requests

2 participants