* Avoid using gRPC when generic RPC systems have same properties
The concept of "streaming" is supported by multiple protocols including gRPC, but also others.
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
* Update specification/trace/semantic_conventions/rpc.md
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
* added spec changes per #1647
* added 'wired' as possible value to `net.host.connection_type`
* fixed spacing in CHANGELOG.md
* added mobile carrier attributes to semantic_conventions/trace/general.yaml
* fixed issue revealed by
* reverted extra space per markdownlint
* made connection_type allow custom values
* added additional space
* removed manually added table & ran generator tool
* separated connection.type & connection.subtype
* updated changelog to reflect iteration
* added literal radio tech to connection.subtype table
* added as option for connect.type
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
* Remove rpc.jsonrpc.method, clarify rpc.method instead.
* Add PR#.
* Clarify client side code.namespace/function.
* Use "ref" instead of "constraint: any_of".
This should be changed back once
https://github.com/open-telemetry/build-tools/issues/33
is resolved & the updated build tools available.
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
This adds some minimal sanity checks to make sure we don't forget
to add the schema file when we make a release. The checks are tied
to the CHANGELOG.md.
In the future we can do more thorough verifications, e.g. parse the content
of the schema YAML file and ensure it includes the changes that we can
detect by looking at the changes at the semantic convention files.
* Add Device (Mobile) and OS Version Resource Semantic Attributes
* Added OS Name (iOS) and OS Version (14.4) to `os`.
* Added Device Identifier and Model Identifier to a newly created `device` group.
* Have consistent formatting for semantic convention enums
Currently, semantic convention enum values are not consistent.
For example, os.type values are all capitals whereas
cloud.infrastructure_service values are underscored lowercase.
This change improves the inconsistencies.
We also expect language implementations to autogenerate code
from enum values. Each language has their own conventions for
constant variable identifiers and we expect the consistent
formatting is going to help the language implementors.
Fixes#1519.
* Fix Azure Member Brief
Azure currently has an incorrect description associated with it. This fixes it 😄
* Update faas.md
Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com>
* Avoid using "infrastructure" terminology for all cloud
Infrastructure in cloud has a specific connotation for concepts
explained in Infrastructure-as-a-Service (IaaS). Avoid this
termilogy because it's exclusive of some other services/platforms
that is represented by the "cloud" namespace.
Renaming "infrastructure_service" to "service" also due to the new
key length limits we are considering and infrastructure_service is
a lengthy choice.
Bogdan Drutu