Closed StefanKurek closed 2 months ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
To clarify, this attribute would be applied to all resources emitted by the receiver, because all the components described are always associated with one data center. Is that right?
If so, this makes sense to me. We need to add it first as an optional resource attribute and can enable it by default in a future version. Same mechanism as https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/24071#issuecomment-2066775491 should be used.
@djaglowski yep, right now I think it makes the most sense to put it on every single resource type. I can update the related PR to do as you suggested with the optional resource attribute.
@djaglowski You mention a warning log in the linked issue with a version (when is this log emitted?). Is this relevant to this attribute as well?
Yes, we'll have to do it before enabling the attribute by default. Adding it immediately seems fine to me.
Component(s)
receiver/vcenter
What happened?
Description
Currently, when collecting against any environment, none of the existing resources have resource attributes that define which datacenter they belong to. If there were multiple datacenters, this could cause confusion and even allow for the possibility of two resources with the exact same resource attribute key/values.
Steps to Reproduce
Collect against any vCenter environment.
Expected Result
All returned resources have a
vcenter.datacenter.name
resource attributeActual Result
No returned resources have resource attributes related to datacenter
Collector version
v1.5.0/v0.98.0
Environment information
No response
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response