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

[Metricbeat] Add reservation metrics to VMWare integration #26149

Closed
sorantis opened this issue Jun 4, 2021 · 2 comments · Fixed by #26167
Closed

[Metricbeat] Add reservation metrics to VMWare integration #26149

sorantis opened this issue Jun 4, 2021 · 2 comments · Fixed by #26167
Assignees
Labels
enhancement Metricbeat Metricbeat Team:Integrations Label for the Integrations team

Comments

@sorantis
Copy link
Contributor

sorantis commented Jun 4, 2021

Users are missing reservation metrics from the VMWare module. Add the following metrics to VMWare module:

  • staticCpuEntitlement , this will give CPU reservation VM
  • staticMemoryEntitlement, this will give Memory Reservation of VM
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 4, 2021
@sorantis sorantis added the Team:Integrations Label for the Integrations team label Jun 4, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 4, 2021
@sorantis sorantis added Metricbeat Metricbeat needs_team Indicates that the issue/PR needs a Team:* label labels Jun 4, 2021
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 4, 2021
@botelastic
Copy link

botelastic bot commented Jun 4, 2021

This issue doesn't have a Team:<team> label.

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

Successfully merging a pull request may close this issue.

3 participants