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 Elastic Agent condition (and Kubernetes Leader Election) #916

Open
BenB196 opened this issue Apr 18, 2024 · 0 comments
Open

Support Elastic Agent condition (and Kubernetes Leader Election) #916

BenB196 opened this issue Apr 18, 2024 · 0 comments

Comments

@BenB196
Copy link

BenB196 commented Apr 18, 2024

(I'm not 100% sure this is the correct repo, but I think its probably the best starting point to at least be moved to the correct spot).

Request

It would be nice if Synthetic monitors assigned to a Private location could leverage Elastic Agent conditions. (This would also support things like Leader Election)

Use Cases

  1. As an operator of Kubernetes clusters, I'd like to have a synthetic monitor running on each cluster that reaches out to some endpoint to validate connectivity. To reduce management overhead, I'd like to have one Fleet Managed Elastic Agent per Kubernetes cluster node. To achieve this, I'd need to set a Synthetic private location on my Agent policy, and to not have this monitor run on all my nodes, I'd like to use the condition + leader election to only run the monitor on the currently elected leader.
  2. As an operator of multiple Private locations that run in Kubernetes environments, I'd like to be able to define which environments specific monitors run via conditions, while still using the same private location for all monitors.

The lack of this functionality is currently limiting our want to adopt this part of the product.

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