From 399c33203d5c7a971a8215194f43cd5072d9d616 Mon Sep 17 00:00:00 2001 From: Devesh chouhan Date: Mon, 29 Apr 2024 20:14:50 +0000 Subject: [PATCH 01/15] added "using instrumentationo libraries" for cpp --- content/en/docs/languages/cpp/library.md | 64 ++++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 content/en/docs/languages/cpp/library.md diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md new file mode 100644 index 000000000000..ffa38e753cd2 --- /dev/null +++ b/content/en/docs/languages/cpp/library.md @@ -0,0 +1,64 @@ +--- +title: Using instrumentation libraries +linkTitle: Libraries +weight: 40 +--- + +{{% docs/languages/libraries-intro "C++" %}} + + +## Using instrumentation libraries + + +When you develop an app, you might use third-party libraries and frameworks to accelerate your work. If you then +instrument your app using OpenTelemetry, you might want to avoid spending additional time to manually add traces, +logs, and metrics to the third-party libraries and frameworks you use. + +Many libraries and frameworks already support OpenTelemetry or are supported through OpenTelemetry +[instrumentation](/docs/concepts/instrumentation/libraries/), +so that they can generate telemetry you can export to an observability back end. + +If you are instrumenting an app or service that use third-party libraries or frameworks, follow these instructions to +learn how to use natively instrumented libraries and instrumentation libraries for your dependencies. + + +## Use natively instrumented libraries + +If a library comes with OpenTelemetry support by default, you can get traces, metrics, and logs emitted from that +library by adding and setting up the OpenTelemetry SDK with your app. + +The library might require some additional configuration for the instrumentation. Go to the documentation for that +library to learn more. + + +## Use instrumentation libraries + + +If a library doesn't include OpenTelemetry support, you can use +[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library) +to generate telemetry data for a library or framework. + +For example, +[NGINX instrumentation](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation/nginx) +Adds OpenTelemetry distributed tracing support to nginx. + + +## setup + +For setup of instrumentation library check [otel-cpp-contrib](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation) + + +## Available packages + +A full list of instrumentation libraries available can be found in the [openTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=cpp&component=instrumentation) + + +## Next steps + +After you've set up instrumentation libraries, you might want to add +[additional instrumentation](/docs/languages/php/instrumentation) to collect +custom telemetry data. + +You might also want to configure an appropriate exporter to +[export your telemetry data](/docs/languages/cpp/exporters) to one or more +telemetry backends. \ No newline at end of file From 841054f0d2bd35b5a868a1d4cdce8f1ad06fc817 Mon Sep 17 00:00:00 2001 From: Devesh chouhan Date: Tue, 30 Apr 2024 00:16:08 +0000 Subject: [PATCH 02/15] added "using instrumentationo libraries" for cpp --- content/en/docs/languages/cpp/library.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index ffa38e753cd2..22e736320ec7 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -15,7 +15,7 @@ instrument your app using OpenTelemetry, you might want to avoid spending additi logs, and metrics to the third-party libraries and frameworks you use. Many libraries and frameworks already support OpenTelemetry or are supported through OpenTelemetry -[instrumentation](/docs/concepts/instrumentation/libraries/), +[instrumentation](https://opentelemetry.io/docs/concepts/instrumentation/libraries/), so that they can generate telemetry you can export to an observability back end. If you are instrumenting an app or service that use third-party libraries or frameworks, follow these instructions to @@ -35,7 +35,7 @@ library to learn more. If a library doesn't include OpenTelemetry support, you can use -[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library) +[instrumentation libraries](https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-library) to generate telemetry data for a library or framework. For example, @@ -56,9 +56,9 @@ A full list of instrumentation libraries available can be found in the [openTele ## Next steps After you've set up instrumentation libraries, you might want to add -[additional instrumentation](/docs/languages/php/instrumentation) to collect +[additional instrumentation](https://opentelemetry.io/docs/languages/cpp/instrumentation/) to collect custom telemetry data. You might also want to configure an appropriate exporter to -[export your telemetry data](/docs/languages/cpp/exporters) to one or more +[export your telemetry data]( https://opentelemetry.io/docs/languages/cpp/exporters/) to one or more telemetry backends. \ No newline at end of file From e0a4afa6ea19ab32169ef062dd05afb4a1224a29 Mon Sep 17 00:00:00 2001 From: Devesh chouhan <132684997+devc007@users.noreply.github.com> Date: Tue, 30 Apr 2024 14:54:15 +0530 Subject: [PATCH 03/15] Update content/en/docs/languages/cpp/library.md Co-authored-by: Fabrizio Ferri-Benedetti --- content/en/docs/languages/cpp/library.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index 22e736320ec7..ed21270c8a31 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -16,7 +16,7 @@ logs, and metrics to the third-party libraries and frameworks you use. Many libraries and frameworks already support OpenTelemetry or are supported through OpenTelemetry [instrumentation](https://opentelemetry.io/docs/concepts/instrumentation/libraries/), -so that they can generate telemetry you can export to an observability back end. +so that they can generate telemetry you can export to an observability backend. If you are instrumenting an app or service that use third-party libraries or frameworks, follow these instructions to learn how to use natively instrumented libraries and instrumentation libraries for your dependencies. From 6e9208ae9fa43486987d4a5c2fc0e5ed84878d1e Mon Sep 17 00:00:00 2001 From: Devesh chouhan <132684997+devc007@users.noreply.github.com> Date: Tue, 30 Apr 2024 14:54:26 +0530 Subject: [PATCH 04/15] Update content/en/docs/languages/cpp/library.md Co-authored-by: Fabrizio Ferri-Benedetti --- content/en/docs/languages/cpp/library.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index ed21270c8a31..1434cfac0417 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -27,7 +27,7 @@ learn how to use natively instrumented libraries and instrumentation libraries f If a library comes with OpenTelemetry support by default, you can get traces, metrics, and logs emitted from that library by adding and setting up the OpenTelemetry SDK with your app. -The library might require some additional configuration for the instrumentation. Go to the documentation for that +The library might require some additional configuration for the instrumentation. See the documentation for that library to learn more. From 5efc0424f6626bd77665409fe28a9236448b427b Mon Sep 17 00:00:00 2001 From: Devesh chouhan <132684997+devc007@users.noreply.github.com> Date: Tue, 30 Apr 2024 14:54:47 +0530 Subject: [PATCH 05/15] Update content/en/docs/languages/cpp/library.md Co-authored-by: Fabrizio Ferri-Benedetti --- content/en/docs/languages/cpp/library.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index 1434cfac0417..ac6018637364 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -40,7 +40,7 @@ to generate telemetry data for a library or framework. For example, [NGINX instrumentation](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation/nginx) -Adds OpenTelemetry distributed tracing support to nginx. +adds OpenTelemetry distributed tracing support to NGINX. ## setup From aee4b5855c3f31bfb0b8d2a551bc68eef29b750a Mon Sep 17 00:00:00 2001 From: Devesh chouhan <132684997+devc007@users.noreply.github.com> Date: Tue, 30 Apr 2024 14:54:58 +0530 Subject: [PATCH 06/15] Update content/en/docs/languages/cpp/library.md Co-authored-by: Fabrizio Ferri-Benedetti --- content/en/docs/languages/cpp/library.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index ac6018637364..2151a31f10f8 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -31,9 +31,6 @@ The library might require some additional configuration for the instrumentation. library to learn more. -## Use instrumentation libraries - - If a library doesn't include OpenTelemetry support, you can use [instrumentation libraries](https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-library) to generate telemetry data for a library or framework. From c5d98a8a564e5bbfafe34b724c4b257ff2dc2f59 Mon Sep 17 00:00:00 2001 From: Devesh chouhan <132684997+devc007@users.noreply.github.com> Date: Tue, 30 Apr 2024 14:55:16 +0530 Subject: [PATCH 07/15] Update content/en/docs/languages/cpp/library.md Co-authored-by: Fabrizio Ferri-Benedetti --- content/en/docs/languages/cpp/library.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index 2151a31f10f8..48b4eadd7100 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -40,7 +40,7 @@ For example, adds OpenTelemetry distributed tracing support to NGINX. -## setup +## Setup For setup of instrumentation library check [otel-cpp-contrib](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation) From 560e175abf02fb1538f2815c7c7588ee382393d4 Mon Sep 17 00:00:00 2001 From: Devesh chouhan <132684997+devc007@users.noreply.github.com> Date: Tue, 30 Apr 2024 14:55:31 +0530 Subject: [PATCH 08/15] Update content/en/docs/languages/cpp/library.md Co-authored-by: Fabrizio Ferri-Benedetti --- content/en/docs/languages/cpp/library.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index 48b4eadd7100..982a3d0cd4ec 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -42,7 +42,7 @@ adds OpenTelemetry distributed tracing support to NGINX. ## Setup -For setup of instrumentation library check [otel-cpp-contrib](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation) +To set up an instrumentation library see [otel-cpp-contrib](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation) ## Available packages From 7867fc5a2baf7fafae58ed9afa73ea2574c99fdf Mon Sep 17 00:00:00 2001 From: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Date: Tue, 30 Apr 2024 09:31:42 +0000 Subject: [PATCH 09/15] Results from /fix:all --- content/en/docs/languages/cpp/library.md | 45 ++++++++++++------------ static/refcache.json | 20 +++++++++++ 2 files changed, 42 insertions(+), 23 deletions(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index 982a3d0cd4ec..6309b61feb1c 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -6,30 +6,30 @@ weight: 40 {{% docs/languages/libraries-intro "C++" %}} - ## Using instrumentation libraries +When you develop an app, you might use third-party libraries and frameworks to +accelerate your work. If you then instrument your app using OpenTelemetry, you +might want to avoid spending additional time to manually add traces, logs, and +metrics to the third-party libraries and frameworks you use. -When you develop an app, you might use third-party libraries and frameworks to accelerate your work. If you then -instrument your app using OpenTelemetry, you might want to avoid spending additional time to manually add traces, -logs, and metrics to the third-party libraries and frameworks you use. - -Many libraries and frameworks already support OpenTelemetry or are supported through OpenTelemetry +Many libraries and frameworks already support OpenTelemetry or are supported +through OpenTelemetry [instrumentation](https://opentelemetry.io/docs/concepts/instrumentation/libraries/), so that they can generate telemetry you can export to an observability backend. -If you are instrumenting an app or service that use third-party libraries or frameworks, follow these instructions to -learn how to use natively instrumented libraries and instrumentation libraries for your dependencies. - +If you are instrumenting an app or service that use third-party libraries or +frameworks, follow these instructions to learn how to use natively instrumented +libraries and instrumentation libraries for your dependencies. ## Use natively instrumented libraries -If a library comes with OpenTelemetry support by default, you can get traces, metrics, and logs emitted from that -library by adding and setting up the OpenTelemetry SDK with your app. - -The library might require some additional configuration for the instrumentation. See the documentation for that -library to learn more. +If a library comes with OpenTelemetry support by default, you can get traces, +metrics, and logs emitted from that library by adding and setting up the +OpenTelemetry SDK with your app. +The library might require some additional configuration for the instrumentation. +See the documentation for that library to learn more. If a library doesn't include OpenTelemetry support, you can use [instrumentation libraries](https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-library) @@ -39,23 +39,22 @@ For example, [NGINX instrumentation](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation/nginx) adds OpenTelemetry distributed tracing support to NGINX. - ## Setup -To set up an instrumentation library see [otel-cpp-contrib](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation) - +To set up an instrumentation library see +[otel-cpp-contrib](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation) ## Available packages -A full list of instrumentation libraries available can be found in the [openTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=cpp&component=instrumentation) - +A full list of instrumentation libraries available can be found in the +[openTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=cpp&component=instrumentation) ## Next steps After you've set up instrumentation libraries, you might want to add -[additional instrumentation](https://opentelemetry.io/docs/languages/cpp/instrumentation/) to collect -custom telemetry data. +[additional instrumentation](https://opentelemetry.io/docs/languages/cpp/instrumentation/) +to collect custom telemetry data. You might also want to configure an appropriate exporter to -[export your telemetry data]( https://opentelemetry.io/docs/languages/cpp/exporters/) to one or more -telemetry backends. \ No newline at end of file +[export your telemetry data](https://opentelemetry.io/docs/languages/cpp/exporters/) +to one or more telemetry backends. diff --git a/static/refcache.json b/static/refcache.json index c062089cae1c..5512da08dcbf 100644 --- a/static/refcache.json +++ b/static/refcache.json @@ -5827,6 +5827,22 @@ "StatusCode": 206, "LastSeen": "2024-02-23T22:55:04.014798-05:00" }, + "https://opentelemetry.io/docs/concepts/instrumentation/libraries/": { + "StatusCode": 206, + "LastSeen": "2024-04-30T09:31:37.735092936Z" + }, + "https://opentelemetry.io/docs/languages/cpp/exporters/": { + "StatusCode": 206, + "LastSeen": "2024-04-30T09:31:38.598060401Z" + }, + "https://opentelemetry.io/docs/languages/cpp/instrumentation/": { + "StatusCode": 206, + "LastSeen": "2024-04-30T09:31:38.379400427Z" + }, + "https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-library": { + "StatusCode": 206, + "LastSeen": "2024-04-30T09:31:37.929550219Z" + }, "https://opentelemetry.io/docs/specs/otel/protocol": { "StatusCode": 206, "LastSeen": "2024-02-24T14:33:05.630341-08:00" @@ -5835,6 +5851,10 @@ "StatusCode": 206, "LastSeen": "2024-03-19T10:16:49.992495889Z" }, + "https://opentelemetry.io/ecosystem/registry/": { + "StatusCode": 206, + "LastSeen": "2024-04-30T09:31:38.297519267Z" + }, "https://opentracing.io": { "StatusCode": 206, "LastSeen": "2024-01-18T19:07:33.813401-05:00" From b82dd8e31850655638ba02307d7e63e3a98fbaa1 Mon Sep 17 00:00:00 2001 From: Devesh chouhan <132684997+devc007@users.noreply.github.com> Date: Tue, 30 Apr 2024 19:08:11 +0530 Subject: [PATCH 10/15] Update content/en/docs/languages/cpp/library.md Co-authored-by: Severin Neumann --- content/en/docs/languages/cpp/library.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index 6309b61feb1c..ad33992c37db 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -47,7 +47,7 @@ To set up an instrumentation library see ## Available packages A full list of instrumentation libraries available can be found in the -[openTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=cpp&component=instrumentation) +[OpenTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=cpp&component=instrumentation) ## Next steps From c1f25246b87136e93c6d4f5ed792919edfbae139 Mon Sep 17 00:00:00 2001 From: Devesh chouhan <132684997+devc007@users.noreply.github.com> Date: Tue, 30 Apr 2024 19:20:00 +0530 Subject: [PATCH 11/15] Update content/en/docs/languages/cpp/library.md Co-authored-by: Severin Neumann --- content/en/docs/languages/cpp/library.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index ad33992c37db..7f3c92e1b1b2 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -35,9 +35,6 @@ If a library doesn't include OpenTelemetry support, you can use [instrumentation libraries](https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-library) to generate telemetry data for a library or framework. -For example, -[NGINX instrumentation](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation/nginx) -adds OpenTelemetry distributed tracing support to NGINX. ## Setup From faab03b20605765df605c0145bfd878145b337a8 Mon Sep 17 00:00:00 2001 From: Devesh chouhan Date: Fri, 3 May 2024 14:32:53 +0000 Subject: [PATCH 12/15] fixed the formatting --- content/en/docs/languages/cpp/library.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index 7f3c92e1b1b2..f75ffbe22276 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -35,7 +35,6 @@ If a library doesn't include OpenTelemetry support, you can use [instrumentation libraries](https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-library) to generate telemetry data for a library or framework. - ## Setup To set up an instrumentation library see From 8aafe11b929bc76b542eada11859082c6f8e33c8 Mon Sep 17 00:00:00 2001 From: Devesh chouhan Date: Tue, 7 May 2024 06:17:09 +0000 Subject: [PATCH 13/15] uses local path not absolute path --- content/en/docs/languages/cpp/library.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index f75ffbe22276..b414e276bd45 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -15,7 +15,7 @@ metrics to the third-party libraries and frameworks you use. Many libraries and frameworks already support OpenTelemetry or are supported through OpenTelemetry -[instrumentation](https://opentelemetry.io/docs/concepts/instrumentation/libraries/), +[instrumentation](docs/concepts/instrumentation/libraries/), so that they can generate telemetry you can export to an observability backend. If you are instrumenting an app or service that use third-party libraries or @@ -32,7 +32,7 @@ The library might require some additional configuration for the instrumentation. See the documentation for that library to learn more. If a library doesn't include OpenTelemetry support, you can use -[instrumentation libraries](https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-library) +[instrumentation libraries](docs/specs/otel/glossary/#instrumentation-library) to generate telemetry data for a library or framework. ## Setup @@ -43,14 +43,14 @@ To set up an instrumentation library see ## Available packages A full list of instrumentation libraries available can be found in the -[OpenTelemetry registry](https://opentelemetry.io/ecosystem/registry/?language=cpp&component=instrumentation) +[OpenTelemetry registry](ecosystem/registry/?language=cpp&component=instrumentation) ## Next steps After you've set up instrumentation libraries, you might want to add -[additional instrumentation](https://opentelemetry.io/docs/languages/cpp/instrumentation/) +[additional instrumentation](docs/languages/cpp/instrumentation/) to collect custom telemetry data. You might also want to configure an appropriate exporter to -[export your telemetry data](https://opentelemetry.io/docs/languages/cpp/exporters/) +[export your telemetry data](docs/languages/cpp/exporters/) to one or more telemetry backends. From b44fc9047f017f77449a39cfcbebc048f2ed5b18 Mon Sep 17 00:00:00 2001 From: Devesh chouhan Date: Wed, 8 May 2024 05:38:29 +0000 Subject: [PATCH 14/15] Fixed URL issue --- content/en/docs/languages/cpp/library.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index b414e276bd45..2b230d876425 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -15,7 +15,7 @@ metrics to the third-party libraries and frameworks you use. Many libraries and frameworks already support OpenTelemetry or are supported through OpenTelemetry -[instrumentation](docs/concepts/instrumentation/libraries/), +[instrumentation](/docs/concepts/instrumentation/libraries/), so that they can generate telemetry you can export to an observability backend. If you are instrumenting an app or service that use third-party libraries or @@ -32,7 +32,7 @@ The library might require some additional configuration for the instrumentation. See the documentation for that library to learn more. If a library doesn't include OpenTelemetry support, you can use -[instrumentation libraries](docs/specs/otel/glossary/#instrumentation-library) +[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library) to generate telemetry data for a library or framework. ## Setup @@ -43,14 +43,14 @@ To set up an instrumentation library see ## Available packages A full list of instrumentation libraries available can be found in the -[OpenTelemetry registry](ecosystem/registry/?language=cpp&component=instrumentation) +[OpenTelemetry registry](/ecosystem/registry/?language=cpp&component=instrumentation) ## Next steps After you've set up instrumentation libraries, you might want to add -[additional instrumentation](docs/languages/cpp/instrumentation/) +[additional instrumentation](/docs/languages/cpp/instrumentation/) to collect custom telemetry data. You might also want to configure an appropriate exporter to -[export your telemetry data](docs/languages/cpp/exporters/) +[export your telemetry data](/docs/languages/cpp/exporters/) to one or more telemetry backends. From 98b173867dc0c793a14e1ac04dbda761d7e48c04 Mon Sep 17 00:00:00 2001 From: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Date: Fri, 17 May 2024 16:09:42 +0000 Subject: [PATCH 15/15] Results from /fix:format --- content/en/docs/languages/cpp/library.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/languages/cpp/library.md b/content/en/docs/languages/cpp/library.md index 2b230d876425..310b91afa60c 100644 --- a/content/en/docs/languages/cpp/library.md +++ b/content/en/docs/languages/cpp/library.md @@ -15,8 +15,8 @@ metrics to the third-party libraries and frameworks you use. Many libraries and frameworks already support OpenTelemetry or are supported through OpenTelemetry -[instrumentation](/docs/concepts/instrumentation/libraries/), -so that they can generate telemetry you can export to an observability backend. +[instrumentation](/docs/concepts/instrumentation/libraries/), so that they can +generate telemetry you can export to an observability backend. If you are instrumenting an app or service that use third-party libraries or frameworks, follow these instructions to learn how to use natively instrumented @@ -48,9 +48,9 @@ A full list of instrumentation libraries available can be found in the ## Next steps After you've set up instrumentation libraries, you might want to add -[additional instrumentation](/docs/languages/cpp/instrumentation/) -to collect custom telemetry data. +[additional instrumentation](/docs/languages/cpp/instrumentation/) to collect +custom telemetry data. You might also want to configure an appropriate exporter to -[export your telemetry data](/docs/languages/cpp/exporters/) -to one or more telemetry backends. +[export your telemetry data](/docs/languages/cpp/exporters/) to one or more +telemetry backends.