[O11y][Vsphere] Migrate VMs Overview dashboard visualizations to lens in kibana 8.7.0

[rajvi-patel-22]

• Enhancement

What does this PR do?

• Migrate visualizations to lens for Vsphere integration package

• Statistics for Vsphere VMs Overview Lens migration:

VSphere dashboard	Before Migration		After Migration
	Lens	Visualization	Lens	Visualization
[Metrics VSphere] VMs overview	0	5	5	0
	0	5	5	0

Checklist

• I have added an entry to my package's changelog.yml file.
• I have verified that panels are populated with data.
• I have verified that panels are not distorted after being migrated to lens.
• I have updated screenshots of dashboard.
• I have verified that data count are matching and panel aggregations are same as before.

Author's Checklist

• Migrated panels should be removed from visualization folder.
• Migrated visualizations are populating in current Kibana version 8.7.0 itself.

Related issues

• Relates Lens Migration of OBS integrations #5221

Note: Screenshot of before migration dashboard is not synced with Kibana files. Please find below screenshot to compare the migrated visualizations.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-04-10T05:43:42.157+0000

• Duration: 17 min 12 sec

Test stats 🧪

Test	Results
Failed	0
Passed	17
Skipped	0
Total	17

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (1/1)	💚
Classes	100.0% (1/1)	💚
Methods	100.0% (18/18)	💚
Lines	89.13% (41/46)	👍
Conditionals	100.0% (0/0)	💚

[agithomas]

1. The Memory value is represented in Human readable format in Old vis but not in New Vis.
   Can this be addressed. If not, i would recommend keeping the old vis
2. What is the default sort order followed in the table?

[rajvi-patel-22]

1. The Memory value is represented in Human readable format in Old vis but not in New Vis.
   Can this be addressed. If not, i would recommend keeping the old vis
2. What is the default sort order followed in the table?

@agithomas ,

1. I have mentioned in the PR description that Kibana files and dashboards are not synced and also uploaded the before migration screenshot. In that the Memory value is not represented in Human readable format.
2. Sorting orders are as below:

• Name: Descending order by count
  
• Used CPU: Descending order by Maximum of vsphere.virtualmachine.cpu.used.mhz
  
• Total RAM: Descending order by Maximum of vsphere.virtualmachine.memory.total.guest.bytes
  
• Networks: Descending order by count
  

[agithomas]

Is it possible to make the changes in the new layout, so that it appears more human readable (representing in MB/ GB) ?

[rajvi-patel-22]

Is it possible to make the changes in the new layout, so that it appears more human readable (representing in MB/ GB) ?

Yes @agithomas, It is possible. I'll update the PR.

[rajvi-patel-22]

Is it possible to make the changes in the new layout, so that it appears more human readable (representing in MB/ GB) ?

@agithomas, I have updated the PR with mentioned changes.

[agithomas]

LGTM!

[elasticmachine]

Package vsphere - 1.5.0 containing this change is available at https://epr.elastic.co/search?package=vsphere