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

Revert "Clarify that service.* conventions apply to all telemetry sources" (#638)

This commit is contained in:
Joao Grassi 2024-01-12 14:01:13 -03:00 committed by GitHub
parent de9ef07a0a
commit e37eac7994
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 4 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
CHANGELOG.md
View File

@ -23,9 +23,6 @@ release.
### 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)
### Breaking

4
docs/resource/README.md
View File

@ -77,7 +77,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
**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 -->
| Attribute | Type | Description | Examples | Requirement Level |
@ -94,7 +94,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
**type:** `service`
**Description:** Experimental additions to service.
**Description:** Additions to service instance.
<!-- semconv service_experimental -->
| Attribute | Type | Description | Examples | Requirement Level |

7
model/resource/service.yaml
View File

@ -3,12 +3,7 @@ groups:
prefix: service
type: resource
brief: >
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.
A service instance.
attributes:
- id: name
type: string

2
model/resource/service_experimental.yaml
View File

@ -3,7 +3,7 @@ groups:
prefix: service
type: resource
brief: >
Experimental additions to service.
A service instance.
attributes:
- id: namespace
type: string