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

Make kubernetes autodiscover and metadata work for other resources #14044

Closed
exekias opened this issue Oct 14, 2019 · 1 comment · Fixed by #14738
Closed

Make kubernetes autodiscover and metadata work for other resources #14044

exekias opened this issue Oct 14, 2019 · 1 comment · Fixed by #14738
Labels
autodiscovery containers Related to containers use case enhancement libbeat Team:Integrations Label for the Integrations team

Comments

@exekias
Copy link
Contributor

exekias commented Oct 14, 2019

As of today, both kubernetes autodiscover provider and add_kubernetes_metadata processor only work with Pods. We want to extend their support so we can do both autodiscover and enrichment based on other kinds of resources (for instance, nodes, services, namespaces...).

A configuration like this could be a good fit (up to discussion):

metricbeat.autodiscover:
  - providers: kubernetes
    resource: node
    ...

This would make autodiscover launch configurations based on cluster nodes.

About add_kubernetes_metadata, we need to figure out what's the best approach for the config

cc @vjsamuel @sorantis @odacremolbap @ChrsMark

@exekias
Copy link
Contributor Author

exekias commented Oct 14, 2019

One of the things that we could base on this: #13873

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autodiscovery containers Related to containers use case enhancement libbeat Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants