Revert "Clarify that service.* conventions apply to all telemetry sources" (#638)
This commit is contained in:
parent
de9ef07a0a
commit
e37eac7994
|
|
@ -23,9 +23,6 @@ release.
|
||||||
|
|
||||||
### Fixes
|
### Fixes
|
||||||
|
|
||||||
- Clarify that `service.*` attributes apply to all telemetry sources.
|
|
||||||
([#630](https://github.com/open-telemetry/semantic-conventions/pull/630))
|
|
||||||
|
|
||||||
## v1.24.0 (2023-12-15)
|
## v1.24.0 (2023-12-15)
|
||||||
|
|
||||||
### Breaking
|
### Breaking
|
||||||
|
|
|
||||||
|
|
@ -77,7 +77,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
|
||||||
|
|
||||||
**type:** `service`
|
**type:** `service`
|
||||||
|
|
||||||
**Description:** A telemetry source. OpenTelemetry has adopted a broad interpretation such that every telemetry source is a service. Examples include, but are not limited to: web services, hosts, mobile applications, browser application, edge computing devices, functions as a service, databases, message brokers, etc. Specific types of telemetry sources may have additional conventions defining domain specific information, but the `service` conventions are applicable to all telemetry sources.
|
**Description:** A service instance.
|
||||||
|
|
||||||
<!-- semconv service -->
|
<!-- semconv service -->
|
||||||
| Attribute | Type | Description | Examples | Requirement Level |
|
| Attribute | Type | Description | Examples | Requirement Level |
|
||||||
|
|
@ -94,7 +94,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
|
||||||
|
|
||||||
**type:** `service`
|
**type:** `service`
|
||||||
|
|
||||||
**Description:** Experimental additions to service.
|
**Description:** Additions to service instance.
|
||||||
|
|
||||||
<!-- semconv service_experimental -->
|
<!-- semconv service_experimental -->
|
||||||
| Attribute | Type | Description | Examples | Requirement Level |
|
| Attribute | Type | Description | Examples | Requirement Level |
|
||||||
|
|
|
||||||
|
|
@ -3,12 +3,7 @@ groups:
|
||||||
prefix: service
|
prefix: service
|
||||||
type: resource
|
type: resource
|
||||||
brief: >
|
brief: >
|
||||||
A telemetry source. OpenTelemetry has adopted a broad interpretation such that every
|
A service instance.
|
||||||
telemetry source is a service. Examples include, but are not limited to: web services,
|
|
||||||
hosts, mobile applications, browser application, edge computing devices, functions as
|
|
||||||
a service, databases, message brokers, etc. Specific types of telemetry sources may have
|
|
||||||
additional conventions defining domain specific information, but the `service`
|
|
||||||
conventions are applicable to all telemetry sources.
|
|
||||||
attributes:
|
attributes:
|
||||||
- id: name
|
- id: name
|
||||||
type: string
|
type: string
|
||||||
|
|
|
||||||
|
|
@ -3,7 +3,7 @@ groups:
|
||||||
prefix: service
|
prefix: service
|
||||||
type: resource
|
type: resource
|
||||||
brief: >
|
brief: >
|
||||||
Experimental additions to service.
|
A service instance.
|
||||||
attributes:
|
attributes:
|
||||||
- id: namespace
|
- id: namespace
|
||||||
type: string
|
type: string
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue