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

Elastic Agent to save selective monitor data [Support Selective Monitoring for Kubernetes] #1349

Open
gizas opened this issue Sep 28, 2022 · 0 comments
Labels
Team:Elastic-Agent Label for the Agent team Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Comments

@gizas
Copy link
Contributor

gizas commented Sep 28, 2022

Describe the enhancement:
As part of #614 , we would like to implement the selective autodiscovery (hints based) feature in the Managed Elastic Agent scenario. For more information about hints autodiscovery you can see here

!!!! The specific feature might not be required if the saving of data from agent is done directly to Elasticsearch and all the checks of changes are handled as part of #1347

We need to verify where the hints block configuration will be saved with additional metadata of agent that refers to and package policy that is bound. Then this data can be used from Fleet to make needed List of Actions as described #1347

Describe a specific use case for the enhancement or feature:
Example provided for use case that user defines a Redis hint to be discovered. The user has enabled auto-discover-hints (hints.enabled:true) on managed agent configuration.

Workflow will be the following:

1.Customer defines following hints block configuration, inside a specific kubernetes pod, under annotations block:

co.elastic.metrics/package: redis
co.elastic.metrics/host: http://localhost:6379
co.elastic.metrics/period: 10s 
  1. This annotations config is discovered by kubernetes provider and will be emitted eventually to agent's data to be sent

This is where the feature starts:
Above data with specific annotations defined, will be saved in
a) a predefined place. (To be defined if we save things to Fleet Server or to Elasticsearch)
b) with a predefined format to be able to picked up from

Below step will be handled by new feature #1347
4. Fleet will monitor index updates and if an update-event includes hints block configuration, this will trigger Fleet to perform specific actions needed for the new package installation as described #1347

Note:
The choice of the place where to save the info can affect the way we make checks before we want to proceed with policy updates

Relevant Links:

cc @ChrsMark , @kpollich

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent Label for the Agent team Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

No branches or pull requests

2 participants