semantic-conventions
semantic-conventions copied to clipboard
open-telemetry
DataCenter Resource
What are you trying to achieve? Being able to track data center related information for anything running outside of a Cloud Provider.
What did you expect to see? Semantic Conventions around DataCenters. I'm not sure if this should be merged somehow with the cloud provider.
Additional context.
When running in a Hybrid environment I should be able to track things whether they are in corporate datacenters owned by the company or datacenters managed by a cloud provider it should largely be interchangeable where possible.
Which information do you want to track about the datacenter? I feel like it would make sense to add it to the host semantic conventions at https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/host.md. If it's just a single identifier, maybe host.datacenter_id or host.location.
@Oberon00 I put together a draft because. I feel like you might be right about the fact that maybe it should go on the host potentially, but then also would we want to have that true of the cloud.md ?
but then also would we want to have that true of the
cloud.md?
What do you mean? If the attribute should apply to things hosted in the cloud too? I think so. E.g. host.type is also rather cloud-specific. When hosted in the cloud, you should probably fill in the availability zone (as opposed to just the region) in the datacenter attribute.
I guess my question is around an application which is running across both on premises would conceptually the host could run in either a "cloud" or "my" DC or even "my" Colo. I understand that there should be some special fields for cloud related things, but at some level there is overlap between an owned host, a colocated host and a cloud host.
I think that host.type actually can be used. I know that in our infrastructure we allocate many of specific builds similar in concept to what you might see so you might have a "standard", "memory",etc. focused server. and that could slot into there just fine.
However when talking about being able to aggregate across different slices I wonder if it makes sense to have something that cuts equally between different hosting environments. Certain things in cloud don't necessarily matter that will in Owned or Colocated scenarios. However I don't know that the tags should be so different for everything. Giving the user an ability to contrast across metrics (or traces, etc) regarding the hosting scenario.
So what i am thinking is introducing the following
device.chasis.idwith the option of also offeringdevice.chasis.name,device.chasis.ip,device.chasis.macattributesdevice.geo.*to describe where the device is located hence uses the geo namespace
Extensions for geo are described in #2371
