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.

Sign up for GitHub

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

Jump to bottom

Update Metricbeat Kubernetes modules to use Reporter methods #9190

Closed
ruflin opened this issue Nov 21, 2018 · 1 comment
Closed

Update Metricbeat Kubernetes modules to use Reporter methods #9190

ruflin opened this issue Nov 21, 2018 · 1 comment
Labels
containers Related to containers use case Metricbeat Metricbeat module Team:Integrations Label for the Integrations team

Comments

@ruflin
Copy link
Member

ruflin commented Nov 21, 2018 •
edited
Loading

The current Kubernetes modules uses the old Fetch methods instead of Reporters. Reports has several advantages as it also uses the beat.Event object which makes it easier to set global fields. As k8s is one of our most popular modules it should be converted to using the reporter methods.
@ruflin ruflin added module Metricbeat Metricbeat containers Related to containers use case v7.0.0 labels Nov 21, 2018
This was referenced Nov 21, 2018
Closed
Merged
@alvarolobato alvarolobato added the Team:Integrations Label for the Integrations team label Nov 21, 2018
@ruflin ruflin changed the title Update Metricbeat Kubernetes modules to use Reporter methods and introduce services Update Metricbeat Kubernetes modules to use Reporter methods Jan 8, 2019
@exekias
Copy link
Contributor

exekias commented Dec 20, 2019

Closing as this was done already

@exekias exekias closed this as completed Dec 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
containers Related to containers use case Metricbeat Metricbeat module Team:Integrations Label for the Integrations team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ruflin @exekias @alvarolobato