[vSphere][datastore] Add support for additional metrics#10911
[vSphere][datastore] Add support for additional metrics#10911lucian-ioan merged 30 commits intoelastic:mainfrom
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
What about stack version dependancy? Also release version we need to use next. |
|
I have shared the details of how we can handle versioning here. |
|
@agithomas : Keeping TSDB in mind, can you check and suggest if any of these need to be added for TSDB? |
|
@agithomas @ishleenk17 I think Do you think using the fingerprint processor is unnecessary here? |
Going with the description of |
Yes, one datastore can have multiple hosts associated. |
|
@ishleenk17 , if a specific datastore is mapped with more than one hosts, will it create multiple documents or it will be a single document having This decides - if |
Single document with host.name/vm.name as an array in it. Sample json |
|
Updated the integration with all the recent changes from elastic/beats. Will rerun system tests, but I don't think any other changes are needed. |
|
Period is not removed from the main manifest file and upgrade the kibana version to 8.15.2 |
packages/vsphere/changelog.yml
Outdated
| @@ -1,4 +1,9 @@ | |||
| # newer versions go on top | |||
| - version: "1.14.0-next" | |||
There was a problem hiding this comment.
Update the version to 1.15.0-next
| description: > | ||
| Rate of writing data to the datastore. | ||
| format: bytes | ||
| - name: write.latency.total.ms |
There was a problem hiding this comment.
I don't think this is resolved still ?
| 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. | ||
| default: 20s | ||
| - name: tags |
There was a problem hiding this comment.
Tags is not added to hbs file.
|
Can we add pipeline tests as well ? |
|
The fields in the commit description are not updated to the latest ones |
|
💚 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#40441, the following metrics need integration update:
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues