Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that service.* conventions apply to all telemetry sources #630

Merged
merged 4 commits into from
Jan 10, 2024
Merged

Clarify that service.* conventions apply to all telemetry sources #630

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
01c1b55
Clarify that service.* conventions apply to all telemetry sources
jack-berg Jan 8, 2024
0beacc2
Add changelog entry
jack-berg Jan 8, 2024
e39a484
Merge branch 'main' into clarify-service-applicability
joaopgrassi Jan 9, 2024
17ab7e3
Merge branch 'main' into clarify-service-applicability
joaopgrassi Jan 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,9 @@ 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
Expand Down
4 changes: 2 additions & 2 deletions docs/resource/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet

**type:** `service`

**Description:** A service instance.
**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.

<!-- semconv service -->
| Attribute | Type | Description | Examples | Requirement Level |
Expand All @@ -94,7 +94,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet

**type:** `service`

**Description:** Additions to service instance.
**Description:** Experimental additions to service.

<!-- semconv service_experimental -->
| Attribute | Type | Description | Examples | Requirement Level |
Expand Down
7 changes: 6 additions & 1 deletion model/resource/service.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,12 @@ groups:
prefix: service
type: resource
brief: >
A service instance.
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.
attributes:
- id: name
type: string
Expand Down
2 changes: 1 addition & 1 deletion model/resource/service_experimental.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ groups:
prefix: service
type: resource
brief: >
A service instance.
Experimental additions to service.
attributes:
- id: namespace
type: string
Expand Down
Loading