Skip to content

Commit 254de0a

Browse files
[chore] Use generic/ficticious example for conditionaly required attributes (#2911)
Co-authored-by: Liudmila Molkova <[email protected]>
1 parent 263e574 commit 254de0a

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

docs/general/attribute-requirement-level.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -92,9 +92,8 @@ the `Opt-In` requirement level on the attribute.
9292

9393
<!-- TODO(jsuereth) - make examples not break on changes to semconv -->
9494

95-
For example, `server.address` is `Conditionally Required` by the
96-
[Database convention](../database/README.md) when available. When
97-
`network.peer.address` is available instead, instrumentation can do a DNS
95+
For example, `server.address` is `Conditionally Required` by a convention. When
96+
server IP address is available instead, instrumentation can do a DNS
9897
lookup, cache and populate `server.address`, but only if the user explicitly
9998
enables the instrumentation to do so, considering the performance issues that
10099
DNS lookups introduce.

0 commit comments

Comments
 (0)