-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resource attributes for network addresses of a host #131
Comments
Hey @mx-psi! Regarding the distinction of IPv4 and IPV6 I like the idea of being more specific. About the second question: From infrastructure perspective I would consider Another thing that we might consider here related to the second question is if it would make sense to report system metrics under the |
Filed #203 for the IPv4 and IPv6 addresses case. |
AFAIK, we intentionally left out these attributes because we want to delay defining them until after we sort out how to implement mutable/added-after-start resource attributes: open-telemetry/opentelemetry-specification#1298 |
Closing this since we now have |
The Elastic Common Schema defines the semantic conventions
host.ip
andhost.mac
, that state, respectively, the known IP and MAC addresses of a given host.This issue tracks incorporating them into the OpenTelemetry semantic conventions. There are two open questions or clarifications that I feel need to be resolved before adding these to OpenTelemetry:
host
namespace of is this a network semantic convention that should be under thesystem.network
namespace?These may be part of open-telemetry/opentelemetry-specification#3556 if approved.
The text was updated successfully, but these errors were encountered: