You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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!
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!
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.
The text was updated successfully, but these errors were encountered: