-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
EC2 Autodiscover provider #12518
Labels
autodiscovery
enhancement
libbeat
Team:Integrations
Label for the Integrations team
Team:Platforms
Label for the Integrations - Platforms team
v7.7.0
Comments
exekias
added
enhancement
libbeat
Team:Integrations
Label for the Integrations team
autodiscovery
labels
Jun 12, 2019
Also, AWS ELB provider is already in progress: #12401, this should be pretty similar, with some opportunities for code sharing. |
andresrc
added
Team:Platforms
Label for the Integrations - Platforms team
[zube]: Inbox
[zube]: In Progress
v7.7.0
and removed
[zube]: Backlog
[zube]: Inbox
labels
Jan 27, 2020
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
autodiscovery
enhancement
libbeat
Team:Integrations
Label for the Integrations team
Team:Platforms
Label for the Integrations - Platforms team
v7.7.0
As a user, I may want to launch Metricbeat modules to monitor services running on AWS EC2 instances. For example:
service: mysql
.Autodiscover framework provides the right mechanism to support this kind of configurations, where the user can define module templates to launch based on conditions on the status of an external system.
We could add a new
aws_ec2
autodiscover provider to allow autodiscover to react to EC2 instances status, this information could be included in autodiscover events, to be used in autodiscover conditions:Autodiscover is able to enrich events coming out of modules it launches,
aws_ec2
should provide the common cloud metadataExample config:
The text was updated successfully, but these errors were encountered: