33 lines
1.5 KiB
Markdown
33 lines
1.5 KiB
Markdown
# Deployment
|
|
|
|
<!-- semconv resource.deployment -->
|
|
<!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
|
|
<!-- see templates/registry/markdown/snippet.md.j2 -->
|
|
<!-- prettier-ignore-start -->
|
|
<!-- markdownlint-capture -->
|
|
<!-- markdownlint-disable -->
|
|
|
|
|
|
**Status:** 
|
|
|
|
**type:** `deployment`
|
|
|
|
**Description:** The software deployment.
|
|
|
|
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
|
|---|---|---|---|---|---|
|
|
| [`deployment.environment.name`](/docs/attributes-registry/deployment.md) | string | Name of the [deployment environment](https://wikipedia.org/wiki/Deployment_environment) (aka deployment tier). [1] | `staging`; `production` | `Recommended` |  |
|
|
|
|
**[1] `deployment.environment.name`:** `deployment.environment.name` does not affect the uniqueness constraints defined through
|
|
the `service.namespace`, `service.name` and `service.instance.id` resource attributes.
|
|
This implies that resources carrying the following attribute combinations MUST be
|
|
considered to be identifying the same service:
|
|
|
|
- `service.name=frontend`, `deployment.environment.name=production`
|
|
- `service.name=frontend`, `deployment.environment.name=staging`.
|
|
|
|
<!-- markdownlint-restore -->
|
|
<!-- prettier-ignore-end -->
|
|
<!-- END AUTOGENERATED TEXT -->
|
|
<!-- endsemconv -->
|