You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current specification for mapping fields in the logs data model recommends prefixing company-specific fields with FQDN-style identifiers, for example com.google.* for GCP-specific attributes.
So, to make this more consistent it would be nice if we could officially update the logs data model mappings to use that same style of prefix rather than the reverse-FQDN for cloud providers.
The text was updated successfully, but these errors were encountered:
Another example for abbreviated attributed prefixes is resource detection processor (it has e.g. Azure-related attributes that are not currently part of the specification)
The current specification for mapping fields in the logs data model recommends prefixing company-specific fields with FQDN-style identifiers, for example
com.google.*
for GCP-specific attributes.It was explained in the log sig meeting that this is based on the existing attribute naming conventions.
However, it would be easier to use abbreviated attribute prefixes for cloud providers, eg
gcp.*
,aws.*
,azure.*
, etc. There are already some conventions for doing this in logs for AWS and tracing. It is also noted elsewhere in the semantic conventions that cloud providers may have specific key names.So, to make this more consistent it would be nice if we could officially update the logs data model mappings to use that same style of prefix rather than the reverse-FQDN for cloud providers.
The text was updated successfully, but these errors were encountered: