elastic / elastic/integrations

[VMware vSphere]: Field type conflict with System package

Open
#13,580 7 comments 0 reactions 0 assignees View on GitHub
Integration:vsphere needs:triage Stalled Team:Obs-InfraObs
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

### Integration Name

VMware vSphere [vsphere]

### Dataset Name

vsphere.host

### Integration Version

1.18.2

### Agent Version

8.17.3

### Agent Output Type

logstash

### Elasticsearch Version

8.17.3

### OS Version and Architecture

RHEL 9.5

### Software/API Version

_No response_

### Error Message

![Image](https://github.com/user-attachments/assets/adc42882-87d4-4e8e-965d-44b5f89ef189)

### Event Original

_No response_

### What did you do?

Installed both integrations

### What did you see?

There is a field conflict between the two integrations. It is because the vSphere integration uses a `.bytes` field suffix for it's metrics.

### What did you expect to see?

They both use the same field to store the data and not cause conflicts.

### Anything else?

As far as I can tell, it's supposed to be stored at the "root" field, aka without the `.bytes` suffix.
There is also no ECS field reference for the `system.*` metricset that I could find, the only thing I found was a reference set for [metricbeat](https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-metricset-system-memory).
Also the chosen integration is Carbon Black because there is no vSphere in the dropdown menu.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.