open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix lychee toml config (#1724) 

Co-authored-by: Joao Grassi <5938087+joaopgrassi@users.noreply.github.com>
This commit is contained in:
Trask Stalnaker 2025-01-08 03:59:10 -08:00 committed by GitHub
parent 45a90be887
commit f6cfb5b7c8
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
7 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.lychee.toml
View File

@ -1,15 +1,15 @@
include-fragments = true include_fragments = true
accept = ["200..=299", "403"] accept = ["200..=299", "403"]
exclude = [ exclude = [
"^https://www.foo.bar", "^https://www.foo.bar",
# excluding links to pull requests and issues is done for performance # excluding links to pull requests and issues is done for performance
"^https://github.com/open-telemetry/semantic-conventions/(pull|issue)/\\d+$" "^https://github.com/open-telemetry/semantic-conventions/(pull|issue)/\\d+$"
] ]
# better to be safe and avoid failures # better to be safe and avoid failures
max-retries = 6 max_retries = 6
# insecure is currently needed for https://osi-model.com # insecure is currently needed for https://osi-model.com
insecure = true insecure = true

2
docs/general/naming.md
View File

@ -193,7 +193,7 @@ OpenTelemetry specification.
might include multiple values: the executable name and command arguments. might include multiple values: the executable name and command arguments.
- When an attribute represents a measurement, - When an attribute represents a measurement,
[Metric Name Pluralization Guidelines](./metrics.md#pluralization) SHOULD be [Name Pluralization Guidelines](./naming.md#pluralization) SHOULD be
followed for the attribute name. followed for the attribute name.
### Signal-specific Attributes ### Signal-specific Attributes

2
docs/hardware/README.md
View File

@ -7,7 +7,7 @@ linkTitle: Hardware
**Status**: [Experimental][DocumentStatus] **Status**: [Experimental][DocumentStatus]
This document describes instruments and attributes for common hardware level This document describes instruments and attributes for common hardware level
metrics in OpenTelemetry. Consider the [general metric semantic conventions](/docs/general/metrics.md#general-metric-semantic-conventions) metrics in OpenTelemetry. Consider the [general metric semantic conventions](/docs/general/metrics.md#general-guidelines)
when creating instruments not explicitly defined in the specification. when creating instruments not explicitly defined in the specification.
Semantic conventions for hardware are defined as following: Semantic conventions for hardware are defined as following:

4
docs/runtime/README.md
View File

@ -30,7 +30,7 @@ discussion.
Metrics specific to a certain runtime environment should be prefixed with Metrics specific to a certain runtime environment should be prefixed with
the runtime's top-level namespace `{environment}.*`, e.g., `jvm.*` and follow the the runtime's top-level namespace `{environment}.*`, e.g., `jvm.*` and follow the
[general metric semantic convention guidelines](/docs/general/metrics.md#general-metric-semantic-conventions). [general metric semantic convention guidelines](/docs/general/metrics.md#general-guidelines).
Authors of runtime instrumentations are responsible for the choice of Authors of runtime instrumentations are responsible for the choice of
`{environment}` to avoid ambiguity when interpreting a metric's name or values. `{environment}` to avoid ambiguity when interpreting a metric's name or values.
@ -42,7 +42,7 @@ such languages, consider using specific `{environment}` prefixes to avoid
ambiguity, like `cpython.*` and `pypy.*`. ambiguity, like `cpython.*` and `pypy.*`.
Also consider the Also consider the
[general metrics](/docs/general/metrics.md#general-metric-semantic-conventions), [general metrics](/docs/general/metrics.md#general-guidelines),
[system metrics](/docs/system/system-metrics.md) and [system metrics](/docs/system/system-metrics.md) and
[OS process metrics](/docs/system/process-metrics.md) [OS process metrics](/docs/system/process-metrics.md)
semantic conventions when instrumenting runtime environments. semantic conventions when instrumenting runtime environments.

2
docs/system/hardware-metrics.md
View File

@ -7,7 +7,7 @@ linkTitle: Hardware
**Status**: [Experimental][DocumentStatus] **Status**: [Experimental][DocumentStatus]
This document describes instruments and attributes for common hardware level This document describes instruments and attributes for common hardware level
metrics in OpenTelemetry. Consider the [general metric semantic conventions](/docs/general/metrics.md#general-metric-semantic-conventions) metrics in OpenTelemetry. Consider the [general metric semantic conventions](/docs/general/metrics.md#general-guidelines)
when creating instruments not explicitly defined in the specification. when creating instruments not explicitly defined in the specification.
This document is being converted to specific hardware metrics, parts of this document that have already been This document is being converted to specific hardware metrics, parts of this document that have already been

2
docs/system/process-metrics.md
View File

@ -8,7 +8,7 @@ linkTitle: Process
This document describes instruments and attributes for common OS process level This document describes instruments and attributes for common OS process level
metrics in OpenTelemetry. Also consider the [general metric semantic metrics in OpenTelemetry. Also consider the [general metric semantic
conventions](/docs/general/metrics.md#general-metric-semantic-conventions) when creating conventions](/docs/general/metrics.md#general-guidelines) when creating
instruments not explicitly defined in this document. OS process metrics are instruments not explicitly defined in this document. OS process metrics are
not related to the runtime environment of the program, and should take not related to the runtime environment of the program, and should take
measurements from the operating system. For runtime environment metrics see measurements from the operating system. For runtime environment metrics see

2
docs/system/system-metrics.md
View File

@ -8,7 +8,7 @@ linkTitle: System
This document describes instruments and attributes for common system level This document describes instruments and attributes for common system level
metrics in OpenTelemetry. Consider the [general metric semantic metrics in OpenTelemetry. Consider the [general metric semantic
conventions](/docs/general/metrics.md#general-metric-semantic-conventions) when creating conventions](/docs/general/metrics.md#general-guidelines) when creating
instruments not explicitly defined in the specification. instruments not explicitly defined in the specification.
The `system.*` namespace SHOULD be exclusively used to report hosts' metrics. The `system.*` namespace SHOULD be exclusively used to report hosts' metrics.