@@ -5,8 +5,8 @@ aliases: [instrumenting]
5
5
weight : 15
6
6
---
7
7
8
- For a system to be [ observable] , it must be ** instrumented** : that is, code from the
9
- system's components must emit [ signals] , such as [ traces] , [ metrics] , and
8
+ For a system to be [ observable] , it must be ** instrumented** : that is, code from
9
+ the system's components must emit [ signals] , such as [ traces] , [ metrics] , and
10
10
[ logs] .
11
11
12
12
Using OpenTelemetry, you can instrument your code in two primary ways:
@@ -36,8 +36,8 @@ solutions. The following things are also a part of OpenTelemetry:
36
36
- Libraries can leverage the OpenTelemetry API as a dependency, which will have
37
37
no impact on applications using that library, unless the OpenTelemetry SDK is
38
38
imported.
39
- - For each of the [ signals] you have several methods at your disposal to
40
- create, process, and export them.
39
+ - For each of the [ signals] you have several methods at your disposal to create,
40
+ process, and export them.
41
41
- With [ context propagation] ( ../context-propagation/ ) built into the
42
42
implementations, you can correlate signals regardless of where they are
43
43
generated.
0 commit comments