Skip to content

Commit 276a42b

Browse files
starlightknownvitorvascchalin
authored
add entity definition in glossary (#7386)
Co-authored-by: Vitor Vasconcellos <[email protected]> Co-authored-by: Patrice Chalin <[email protected]>
1 parent c36405f commit 276a42b

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

content/en/docs/concepts/glossary.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -122,6 +122,13 @@ See [Distributed tracing][distributed tracing].
122122
A distribution is a wrapper around an upstream OpenTelemetry repository with
123123
some customizations. See [Distributions].
124124

125+
### Entity
126+
127+
A collection of [attributes](#attribute) that identify and describe a physical
128+
or logical object. Entities are typically associated with telemetry. For
129+
example, a CPU entity describes a physical CPU, while a service entity describes
130+
a logical grouping of processes that compose an HTTP or other service.
131+
125132
### Event
126133

127134
An Event is a [Log Record](#log-record) with an event name and a well-known
@@ -305,11 +312,8 @@ See [Distributed Tracing](#distributed-tracing).
305312

306313
### Resource
307314

308-
Captures information about the entity producing telemetry as
309-
[Attributes](#attribute). For example, a process producing telemetry that is
310-
running in a container on Kubernetes has a process name, a pod name, a
311-
namespace, and possibly a deployment name. All these attributes can be included
312-
in the `Resource`.
315+
A collection of [entities](#entity) or [attributes](#attribute) that identify or
316+
describe a physical or logical object that produces telemetry.
313317

314318
### REST
315319

0 commit comments

Comments
 (0)