Skip to content

Commit 31f5861

Browse files
Add one more example
1 parent ab2c0b1 commit 31f5861

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/resource/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
101101
|---|---|---|---|---|
102102
| `service.instance.id` | string | The string ID of the service instance. [1] | `my-k8s-pod-deployment-1`; `627cc493-f310-47de-96bd-71410b7dec09` | Recommended |
103103
| `service.namespace` | string | A namespace for `service.name`. [2] | `Shop` | Recommended |
104-
| `service.type` | string | The service type in reverse domain name notation. [3] | `io.opentelemetry.collector`; `io.redis`; `org.apache.kafka` | Recommended |
104+
| `service.type` | string | The service type in reverse domain name notation. [3] | `io.opentelemetry.collector`; `io.redis`; `org.apache.kafka`; `com.yourcompany.productname` | Recommended |
105105

106106
**[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).
107107

model/resource/service_experimental.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -46,4 +46,4 @@ groups:
4646
will typically have a distinct `service.name` to help identify the
4747
logical role of the particular deployment, however their
4848
`service.type` will be the same and will help identify the deployed product.
49-
examples: ["io.opentelemetry.collector", "io.redis", "org.apache.kafka"]
49+
examples: ["io.opentelemetry.collector", "io.redis", "org.apache.kafka", "com.yourcompany.productname"]

0 commit comments

Comments
 (0)