Skip to content

Commit

Permalink
Add one more example
Browse files Browse the repository at this point in the history
  • Loading branch information
tigrannajaryan committed Jan 26, 2024
1 parent c37492c commit 7abfc10
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/resource/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
|---|---|---|---|---|
| `service.instance.id` | string | The string ID of the service instance. [1] | `my-k8s-pod-deployment-1`; `627cc493-f310-47de-96bd-71410b7dec09` | Recommended |
| `service.namespace` | string | A namespace for `service.name`. [2] | `Shop` | Recommended |
| `service.type` | string | The service type in reverse domain name notation. [3] | `io.opentelemetry.collector`; `io.redis`; `org.apache.kafka` | Recommended |
| `service.type` | string | The service type in reverse domain name notation. [3] | `io.opentelemetry.collector`; `io.redis`; `org.apache.kafka`; `com.yourcompany.productname` | Recommended |

**[1]:** MUST be unique for each instance of the same `service.namespace,service.name` pair (in other words `service.namespace,service.name,service.instance.id` triplet MUST be globally unique). The ID helps to distinguish instances of the same service that exist at the same time (e.g. instances of a horizontally scaled service). It is preferable for the ID to be persistent and stay the same for the lifetime of the service instance, however it is acceptable that the ID is ephemeral and changes during important lifetime events for the service (e.g. service restarts). If the service has no inherent unique ID that can be used as the value of this attribute it is recommended to generate a random Version 1 or Version 4 RFC 4122 UUID (services aiming for reproducible UUIDs may also use Version 5, see RFC 4122 for more recommendations).

Expand Down
2 changes: 1 addition & 1 deletion model/resource/service_experimental.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -46,4 +46,4 @@ groups:
will typically have a distinct `service.name` to help identify the
logical role of the particular deployment, however their
`service.type` will be the same and will help identify the deployed product.
examples: ["io.opentelemetry.collector", "io.redis", "org.apache.kafka"]
examples: ["io.opentelemetry.collector", "io.redis", "org.apache.kafka", "com.yourcompany.productname"]

0 comments on commit 7abfc10

Please sign in to comment.