You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specs/agents/tracing-instrumentation-db.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,8 +32,6 @@ The following fields are relevant for database and datastore spans. Where possib
32
32
| <hr/> |<hr/>|<hr/>|
33
33
|`context.destination.address`|The hostname / address of the database.|:x:|
34
34
|`context.destination.port`|The port under which the database is accessible.|:x:|
35
-
|`context.destination.service.name`| The `destination.service.name` is used to denote "sameness" of the service. E.g. multiple instances of Oracle databases have all the same name `oracle`. For databases and storages the same value as for the `span.subtype` should be used.|:white_check_mark:|
36
-
|`context.destination.service.type`| Should be the same as the `span.type`. Value: `db`|:white_check_mark:|
37
35
|`context.destination.service.resource`| Used to detect unique destinations from each service. This field should contain all information that is needed to differentiate different database / storage instances (e.g. in the service map). See details below on how to set this field for specific technologies.|:white_check_mark:|
38
36
|`context.destination.cloud.region`| The cloud region in case the datastore is hosted in a public cloud or is a managed datasatore / database. E.g. AWS regions, such as `us-east-1`|:x:|
0 commit comments