diff --git a/content/en/docs/concepts/instrumentation/_index.md b/content/en/docs/concepts/instrumentation/_index.md index f9a7e3b73768..39ae1d73d907 100644 --- a/content/en/docs/concepts/instrumentation/_index.md +++ b/content/en/docs/concepts/instrumentation/_index.md @@ -5,8 +5,6 @@ aliases: [instrumenting] weight: 15 --- -![ Native Instrumentation vs instrumentation libraries](native-vs-libraries.svg) - In order to make a system observable, it must be **instrumented**: That is, code from the system's components must emit [traces](/docs/concepts/signals/traces/), [metrics](/docs/concepts/signals/metrics/), and diff --git a/content/en/docs/concepts/instrumentation/libraries.md b/content/en/docs/concepts/instrumentation/libraries.md index 7ef1ddcf74ff..c697ea9739c9 100644 --- a/content/en/docs/concepts/instrumentation/libraries.md +++ b/content/en/docs/concepts/instrumentation/libraries.md @@ -22,7 +22,7 @@ and document hooks. Other advantages provided by native instrumentation include: various consumption scenarios using a wide variety of well-documented OpenTelemetry extensibility points. -![ Native Instrumentation vs instrumentation libraries](/img/libraries-instrumentation.svg) +![ Native Instrumentation vs instrumentation libraries](../native-vs-libraries.svg) ## Semantic conventions diff --git a/content/en/docs/concepts/instrumentation/native-vs-libraries.svg b/content/en/docs/concepts/instrumentation/native-vs-libraries.svg index 9f3de2ca0ece..f7afa432b2d6 100755 --- a/content/en/docs/concepts/instrumentation/native-vs-libraries.svg +++ b/content/en/docs/concepts/instrumentation/native-vs-libraries.svg @@ -1,5 +1,5 @@ - +