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

Refactor kubernetes metricsets to use single calls per endpoint #24869

Closed
ChrsMark opened this issue Mar 31, 2021 · 1 comment · Fixed by #25782
Closed

Refactor kubernetes metricsets to use single calls per endpoint #24869

ChrsMark opened this issue Mar 31, 2021 · 1 comment · Fixed by #25782
Assignees
Labels
Team:Integrations Label for the Integrations team

Comments

@ChrsMark
Copy link
Member

Refactor kubernetes metricsets to use single calls per endpoint to improve performance. For instance, state_* metricsets fetch the same amount of data to only store some of them according the target k8s object. This can be improved if metricsets can share the input. Some goes for pod, node, volume, container and system metricsets that get the same input from Kubelet's api.

We can find useful the implementation of cloudfoundry integration which behaves like this.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 31, 2021
@ChrsMark ChrsMark added the Team:Integrations Label for the Integrations team label Mar 31, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

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

Successfully merging a pull request may close this issue.

2 participants