1
0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2024-12-10 09:50:58 +02:00

Change markdown links to relref (#2479)

This commit is contained in:
Phillip Carter 2021-12-21 10:49:18 -08:00 committed by GitHub
parent 1e46549f61
commit c555a7b592
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions

View File

@ -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" >}}

View File

@ -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`
@ -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.