[editorial] service.md: normalize link to process.md (#883)
Co-authored-by: Joao Grassi <5938087+joaopgrassi@users.noreply.github.com> Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
This commit is contained in:
parent
262271ffb3
commit
14c8e5291e
|
|
@ -40,7 +40,7 @@ However, Collectors can set the `service.instance.id` if they can unambiguously
|
|||
for that telemetry. This is typically the case for scraping receivers, as they know the target address and
|
||||
port.
|
||||
|
||||
**[2]:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md#process), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
|
||||
**[2]:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
|
||||
|
||||
**[3]:** A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. `service.name` is expected to be unique within the same namespace. If `service.namespace` is not specified in the Resource then `service.name` is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace.
|
||||
<!-- endsemconv -->
|
||||
<!-- endsemconv -->
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
|
|||
| [`service.name`](../attributes-registry/service.md) | string | Logical name of the service. [1] | `shoppingcart` | `Required` |  |
|
||||
| [`service.version`](../attributes-registry/service.md) | string | The version string of the service API or implementation. The format is not defined by these conventions. | `2.0.0`; `a01dbef8a` | `Recommended` |  |
|
||||
|
||||
**[1]:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md#process), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
|
||||
**[1]:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
|
||||
<!-- endsemconv -->
|
||||
|
||||
## Service (Experimental)
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ groups:
|
|||
note: >
|
||||
MUST be the same for all instances of horizontally scaled services.
|
||||
If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated
|
||||
with [`process.executable.name`](process.md#process), e.g. `unknown_service:bash`.
|
||||
with [`process.executable.name`](process.md), e.g. `unknown_service:bash`.
|
||||
If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
|
||||
examples: ["shoppingcart"]
|
||||
stability: stable
|
||||
|
|
|
|||
Loading…
Reference in New Issue