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

Schedule Configuration Change for Agent in Central Agent Configuration #902

Open
benatbermejo opened this issue Feb 5, 2025 · 0 comments

Comments

@benatbermejo
Copy link

Is your feature request related to a problem? Please describe.
Currently, configuration changes must be applied immediately or manually at a later time. This can be inconvenient for users who need to apply changes during off-peak hours or at a specific time to minimize disruption.

Describe the solution you'd like
I would like to request a new feature in Kibana's Central Agent Configuration that allows users to schedule a configuration change for an agent at a specific date and time. This would improve flexibility and control over configuration changes, allowing users to plan and automate updates more efficiently.

Describe alternatives you've considered
An alternative solution could be to use external scheduling tools or scripts to apply configuration changes at the desired time. However, this approach lacks the integration and ease of use that a built-in scheduling feature would provide.

We have already implemented something similar integrated in Elastic. Using an index that contains the configuration changes schedule and a Watcher that applies the configuration using the Kibana API .

Image

Additional context
Adding a scheduling option in the Central Agent Configuration interface would ensure that scheduled changes are logged and can be reviewed or modified if necessary. This feature would greatly enhance the usability and efficiency of Kibana's Central Agent Configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant