Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website_docs/manual_instrumentation.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,4 +136,4 @@ After configuring context propagation, you'll most likely want to use automatic

[OpenTelemetry Specification]: {{< relref "/docs/reference/specification" >}}
[Trace semantic conventions]: {{< relref "/docs/reference/specification/trace/semantic_conventions" >}}
[instrumentation library]: using_instrumentation_libraries
[instrumentation library]: {{< relref "using_instrumentation_libraries" >}}
4 changes: 2 additions & 2 deletions website_docs/using_instrumentation_libraries.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ func main() {
}
```

Assuming that you have a `Tracer` and [exporter](exporting_data.md) configured, this code will:
Assuming that you have a `Tracer` and [exporter]({{< relref "exporting_data" >}}) configured, this code will:

* Start an HTTP server on port `3030`
* Automatically generate a span for each inbound HTTP request to `/hello-instrumented`
Expand All @@ -90,4 +90,4 @@ A full list of instrumentation libraries available can be found in the [OpenTele

Instrumentation libraries can do things like generate telemtry data for inbound and outbound HTTP requests, but they don't instrument your actual application.

To get richer telemetry data, use [manual instrumentatiion](manual_instrumentation.md) to enrich your telemetry data from instrumentation libraries with instrumentation from your running application.
To get richer telemetry data, use [manual instrumentatiion]({{< relref "manual_instrumentation" >}}) to enrich your telemetry data from instrumentation libraries with instrumentation from your running application.