* Prohibit usage of retired names in semantic conventions
This change adds a prohibition clause that requires that no old
metric or attribute name is used for a new attribute.
This is important to ensure reversibility of schema transformation
(converting from a new version to an old version of schema).
Without this restriction the following is possible:
Schema version 1. Attribute A exists.
Schema version 2. Attribute A is renamed to B. Appropriate schema file is created.
Schema version 3. Attribute A is introduced (a completely different new attribute).
Now attempting to go from Version 3 to version 1 is impossible since it requires
renaming B to A (for the change in version 2), but a different attribute A already exists.
* Fix based on comments
* Add changelog entry
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
Add a missing `</a>` closing tag for the `<a name="nettransport-attribute">` element. Without the closing tag, then entire page after that is taken as content of the anchor, which isn't correct and it breaks table formatting on the website.
Fixes#1760
## Changes
Removes `db.cassandra.keyspace` and `db.hbase.namespace` (in preference for using `db.name`).
Clarifies `db.name` in the case where a database product provides multiple concepts that could be mapped to `db.name`.
* 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>
* 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>
Armin Ruech