[vSphere][virtualmachine] Add support for additional metrics - #10942
Conversation
🚀 Benchmarks reportTo see the full report comment with |
| Total CPU in Mhz. | ||
| - name: cpu.free.mhz | ||
| type: long | ||
| metric_type: gauge |
There was a problem hiding this comment.
Any reason to remove these metric_types?
There was a problem hiding this comment.
No, reverting, tested first with beats code directly.
| - name: name | ||
| type: keyword | ||
| # Reason to add as a dimension field: Each VM has Unique name assigned | ||
| dimension: true |
There was a problem hiding this comment.
@lucian-ioan : I suppose you are using the fields.yml directly from the beats code.
That would not be correct as we don't consider tsdb there.
Also, for any new fields please keep TSDB into consideration.
| @@ -59,37 +59,58 @@ | |||
| }, | |||
| "vsphere": { | |||
| "virtualmachine": { | |||
There was a problem hiding this comment.
Are these events autogenerated by system tests ?
Looks like these are being used from beats code ?
There was a problem hiding this comment.
Tested with beats code, regenerated it now.
| @@ -1,4 +1,9 @@ | |||
| # newer versions go on top | |||
| - version: "1.14.0-next" | |||
There was a problem hiding this comment.
Lets update this to latest 1.15.0-next
| type: long | ||
| metric_type: gauge | ||
| description: The number of snapshots of this virtualmachine. | ||
| - name: triggerd_alarms.* |
There was a problem hiding this comment.
This needs to incorporate the latest change of this name change yesterday.
"triggered_alamrs"
| - name: period | ||
| type: text | ||
| title: Period | ||
| description: The vSphere performance API allows for collecting host and datastore metrics at various intervals, including real-time (every 20 seconds), 5 minutes, or longer durations. Properly configuring the "period" parameter is crucial to manage usage restrictions and ensure accurate data collection. For more information on optimizing your data collection setup, refer to the [Data Collection Intervals](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-247646EA-A04B-411A-8DD4-62A3DCFCF49B.html) and [Data Collection Levels](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-25800DE4-68E5-41CC-82D9-8811E27924BC.html) documentation. |
There was a problem hiding this comment.
Change the description as discussed yesterday
|
@lucian-ioan Please add tags in hbs file. |
|
Update description of commit PR with the snapshot fields as well |
ishleenk17
left a comment
There was a problem hiding this comment.
Looks good!
Let the CI pass
Addressed changes, merging today.
|
💚 Build Succeeded
History
cc @lucian-ioan |
|
Package vsphere - 1.15.0 containing this change is available at https://epr.elastic.co/search?package=vsphere |




Proposed commit message
Following beats code changes in elastic/beats#40485, the following metrics need integration update:
Checklist
changelog.ymlfile.Author's Checklist
Author's Checklist
How to test this PR locally
Related issues
Screenshots