Semantic conventions for virtual machine resources - Githubissues

open-telemetry / semantic-conventions

Defines standards for generating consistent, accessible telemetry across a variety of domains

Apache License 2.0

256 stars 165 forks source link

Semantic conventions for virtual machine resources #1084

Open thompson-tomo opened 4 months ago

thompson-tomo commented 4 months ago

Area(s)

area:new

Is your change request related to a problem? Please describe.

I want to know details about the VM resources being utilised in a vendor agnostic manner

Describe the solution you'd like

I would like a clear definition of semantic conventions which describe a VM provider

vmhost.provider ie esxi, hyper-v
vmhost.version
vmhost.address

Should be checked if any vendor specific VM fields would make sense to be moved.

Describe alternatives you've considered

Do not have it stsndardised

Additional context

No response

gberche-orange commented 1 day ago

Compute Instance/Host includes some limited virtual machines related data:

https://github.com/open-telemetry/semantic-conventions/blob/96f8bda9bab363cb01e2441820bc83a5dad15801/docs/resource/host.md?plain=1#L24-L28

Cloud specific conventions such as GCP are being defined https://github.com/open-telemetry/semantic-conventions/blob/96f8bda9bab363cb01e2441820bc83a5dad15801/docs/resource/cloud-provider/gcp/gce.md?plain=1#L17-L20

I did not yet find the hypervisor semantics (say related to host.type such as AWS n1-standard-1) such as vCPU/Memory/storage/networking capacity

The cloud provider environment are defined in https://github.com/open-telemetry/semantic-conventions/blob/main/docs/resource/cloud.md but does not seem to cover private cloud stacks such as vmware/openstack/... https://github.com/open-telemetry/semantic-conventions/blob/96f8bda9bab363cb01e2441820bc83a5dad15801/docs/resource/cloud.md?plain=1#L17-L24

https://github.com/open-telemetry/semantic-conventions/pull/1413 adds model for a physical datacenter (typically in a private cloud)