* 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>
* Rename extra dimensions to extra attributes
* Moar
Co-authored-by: Reiley Yang <reyang@microsoft.com>
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
A 'process.runtime' namespace is currently defined in the resource
semantic conventions. The metric semantic conventions suggest that
runtime metrics use a 'runtime' namespace. Since the runtime metrics
are directly related to the runtime resources, they ought to share a
common namespace.
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.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.
* Add metric for currently-in-flight HTTP requests
* Update name to active_requests
* Fix missing rename noticed by anuraaga
* Clarify `active_requests` are in-flight
Co-authored-by: Reiley Yang <reyang@microsoft.com>
* Switch to UpDownSumObserver
Co-authored-by: Reiley Yang <reyang@microsoft.com>
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
* add http metric label spec
* typo
* update attribute locations and clarify which to inlcude, alter and exclude
* add metric instruments list
* simplify intro sections, add requirement columns, clarify labels, fix normative directives and more
* fix HTTP strings
* add count metric instrument and shorten duration metric name
* remove dependency on http.md, add more notes and examples and general cleanup
* replace span.kind with type
* add missing labels and cleanup links
* substitution->alternatives and remove section not needed
* make request count metric instrument plural
* formatting
* clarify type column
* update intro and fix units
* breakout metric instrument table
* remove http.route since it is the same as http.target after http.target is simplified
* update net labels to link to definition
* add lowercase requirement to http.scheme
* formatting
Co-authored-by: gfuller <gfuller@newrelic.com>
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
Fabian Stäber