This PR clarifies semantic conventions for HTTP retries and redirects and defines a span structure and linking as well as span attributes for retries. Changes were discussed recently at Instrumentation SIG meetings.
This change addresses a scenario which is in the scope for bringing the existing HTTP semantic conventions for tracing to an initial stable state, see related [otep #174](https://github.com/open-telemetry/oteps/pull/174).
* [editorial] Use `npx` to run npm cmds, not hardcoded paths
* Update Makefile based on feedback
* Use --no-install option for npx
* Add `npm install` to markdown-check workflows
* Pin markdownlint-cli at 0.31.0
* Run `npm install` as a separate workflow step
* Use name 'install dependencies' for npm install cmd
* CONTRIBUTING: clarify that you install the tools once
* make: add `install-tools` as dependency to `all`
* Add install check line to `mardown*` targets
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
Make all performs roughly the same steps as the alrady existing github actions. The only
exception is yamllint which I was not able to make work on my Mac after quite some time
and had to skip. If anyone knows how to make it work on a Mac please submit a follow-up PR.
Note that the checks can run in parallel to speed up, e.g. `make -j4`.
* Change golang namespace to 'go', rather than 'gc'
* Specify common process.runtime.* attributes for Go
* Add link to runtime.Compiler
* Remove static descriptions
* Add table of descriptions for golang runtime names
* Add context to go examples
Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com>
* 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>
Logs are transmitted via several common media, such as files and
iostreams. This PR establishes semantic conventions for describing the
file or iostream from which a log was read. Notably, these attributes
are not resource attributes, as the medium used to tranmit a log is not
considered to be the originator of the log.
Carlos Alberto Cortez