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
Is your feature request related to a problem? Please describe.
I’m currently using Fluent Bit in an environment where remote configuration management and control over telemetry data are essential. However, Fluent Bit lacks native support for the Open Agent Management Protocol (OpAMP), which would enable centralized control, configuration, and monitoring of telemetry agents in real time. Without OpAMP, managing configurations across distributed agents becomes challenging, as I have to rely on manual updates or less dynamic methods.
Describe the solution you'd like
I’d like to see Fluent Bit natively support the OpAMP protocol to allow more streamlined, centralized management of agents. With OpAMP integration, Fluent Bit could automatically receive configuration updates, monitor its status, and be managed from a single OpAMP-compatible server. This would significantly enhance Fluent Bit’s usability in large-scale environments where central management of telemetry agents is critical.
Describe alternatives you've considered
I have explored other methods for centralized management, such as leveraging custom scripts for configuration updates or using alternative protocols. However, these approaches lack the real-time capabilities and seamless integration that OpAMP would provide. I also considered using other telemetry agents that support OpAMP, but they don’t meet Fluent Bit’s performance and flexibility standards.
Additional context
This feature would enable smoother management of Fluent Bit in dynamic environments, particularly in setups with distributed microservices that require frequent updates to telemetry configurations. Centralized control through OpAMP would reduce operational overhead and allow better resource usage by eliminating the need for manual agent updates.
The text was updated successfully, but these errors were encountered:
Wudadada
changed the title
Need support for support for the Open Agent Management Protocol (OpAMP)
Need support for the Open Agent Management Protocol (OpAMP)
Oct 30, 2024
Is your feature request related to a problem? Please describe.
I’m currently using Fluent Bit in an environment where remote configuration management and control over telemetry data are essential. However, Fluent Bit lacks native support for the Open Agent Management Protocol (OpAMP), which would enable centralized control, configuration, and monitoring of telemetry agents in real time. Without OpAMP, managing configurations across distributed agents becomes challenging, as I have to rely on manual updates or less dynamic methods.
Describe the solution you'd like
I’d like to see Fluent Bit natively support the OpAMP protocol to allow more streamlined, centralized management of agents. With OpAMP integration, Fluent Bit could automatically receive configuration updates, monitor its status, and be managed from a single OpAMP-compatible server. This would significantly enhance Fluent Bit’s usability in large-scale environments where central management of telemetry agents is critical.
Describe alternatives you've considered
I have explored other methods for centralized management, such as leveraging custom scripts for configuration updates or using alternative protocols. However, these approaches lack the real-time capabilities and seamless integration that OpAMP would provide. I also considered using other telemetry agents that support OpAMP, but they don’t meet Fluent Bit’s performance and flexibility standards.
Additional context
This feature would enable smoother management of Fluent Bit in dynamic environments, particularly in setups with distributed microservices that require frequent updates to telemetry configurations. Centralized control through OpAMP would reduce operational overhead and allow better resource usage by eliminating the need for manual agent updates.
The text was updated successfully, but these errors were encountered: