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

Rename manual_instrumentation and add redirects (#2480)

Browse Source 
* Rename manual_instrumentation and add redirects

* Update

* More feedback + name adjustment

* Go back
This commit is contained in:
Phillip Carter 2021-12-21 16:11:19 -08:00 committed by GitHub
parent c555a7b592
commit 49987ad852
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
website_docs/exporting_data.md
View File

@ -1,6 +1,7 @@
---
title: "Processing and Exporting Data"
title: Processing and Exporting Data
weight: 4
linkTitle: Exporting data
---
Once you've instrumented your code, you need to get the data out in order to do anything useful with it. This page will cover the basics of the process and export pipeline.

2
website_docs/getting-started.md
View File

@ -536,7 +536,7 @@ start adding OpenTelemetry Go to your projects at this point. Go instrument your
code!
For more information about instrumenting your code and things you can do with
spans, refer to the [Instrumenting]({{< relref "manual_instrumentation" >}})
spans, refer to the [Instrumenting]({{< relref "manual" >}})
documentation. Likewise, advanced topics about processing and exporting
telemetry data can be found in the [Processing and Exporting Data]({{< relref
"exporting_data" >}}) documentation.

4
website_docs/using_instrumentation_libraries.md → website_docs/libraries.md
View File

@ -1,6 +1,8 @@
---
title: Using instrumentation libraries
weight: 3
linkTitle: Libraries
aliases: [/docs/instrumentation/go/using_instrumentation_libraries, /docs/instrumentation/go/automatic_instrumentation]
---
Go does not support truly automatic instrumentation like other languages today. Instead, you'll need to depend on [instrumentation libraries](https://opentelemetry.io/docs/reference/specification/glossary/#instrumentation-library) that generate telemetry data for a particular instrumented library. For example, the instrumentation library for `net/hhtp` will automatically create spans that track inbound and outbound requests once you configure it in your code.
@ -90,4 +92,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]({{< relref "manual_instrumentation" >}}) to enrich your telemetry data from instrumentation libraries with instrumentation from your running application.
To get richer telemetry data, use [manual instrumentatiion]({{< relref "manual" >}}) to enrich your telemetry data from instrumentation libraries with instrumentation from your running application.

4
website_docs/manual_instrumentation.md → website_docs/manual.md
View File

@ -1,6 +1,8 @@
---
title: Instrumentation
title: Manual Instrumentation
weight: 3
linkTitle: Manual
aliases: [/docs/instrumentation/go/instrumentation, /docs/instrumentation/go/manual_instrumentation]
---
Instrumentation is the process of adding observability code to your application. There are two general types of instrumentation - automatic, and manual - and you should be familiar with both in order to effectively instrument your software.