@@ -9,8 +9,8 @@ IgnoreDirs:

- ^blog/(\d+/)?page/\d+

IgnoreInternalURLs: # list of paths

IgnoreURLs: # list of regexs of paths or URLs to be ignored

- ^/docs/instrumentation/\w+/(api|examples)/$

- ^/docs/instrumentation/net/(metrics-api|traces-api)/

- ^/docs/languages/\w+/(api|examples)/$

- ^/docs/languages/net/(metrics-api|traces-api)/

- ^/community/end-user/feedback-survey/$

- ^(/docs/migration/)?opencensus/$

@@ -47,7 +47,7 @@ generate, collect, and export telemetry data (metrics, logs, and traces) to help

you analyze your software's performance and behavior.

> OpenTelemetry is **generally available** across

> [several languages](/docs/instrumentation/) and is suitable for use.

> [several languages](/docs/languages/) and is suitable for use.

{{% /blocks/lead %}}

@@ -261,5 +261,5 @@ COPY opentelemetry_module.conf /etc/nginx/conf.d

[v1.0.1 release of the otel-webserver-module]:

https://github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.1

[java]:

/docs/instrumentation/java/automatic/agent-config/#capturing-http-request-and-response-headers

[python]: /docs/instrumentation/python/automatic/

/docs/languages/java/automatic/agent-config/#capturing-http-request-and-response-headers

[python]: /docs/languages/python/automatic/

@@ -302,5 +302,5 @@ _A version of this article was [originally posted][] on the New Relic blog._

[otlp]: /docs/specs/otlp/

[opentelemetry-java]: https://github.com/open-telemetry/opentelemetry-java

[environment variable]: /docs/specs/otel/metrics/sdk_exporters/otlp/

[instrumentation]: /docs/instrumentation

[instrumentation]: /docs/languages

[github.com/open-telemetry]: https://github.com/open-telemetry

@@ -54,15 +54,15 @@ context.

The demo’s stack includes multiple microservices in different languages,

covering each of the following OTel-supported languages:

- [C++](/docs/instrumentation/cpp/)

- [.NET](/docs/instrumentation/net/)

- [Erlang/Elixir](/docs/instrumentation/erlang/)

- [Go](/docs/instrumentation/go/)

- [Node.js](/docs/instrumentation/js/)

- [PHP](/docs/instrumentation/php/)

- [Python](/docs/instrumentation/python/)

- [Ruby](/docs/instrumentation/ruby/)

- [Rust](/docs/instrumentation/rust/)

- [C++](/docs/languages/cpp/)

- [.NET](/docs/languages/net/)

- [Erlang/Elixir](/docs/languages/erlang/)

- [Go](/docs/languages/go/)

- [Node.js](/docs/languages/js/)

- [PHP](/docs/languages/php/)

- [Python](/docs/languages/python/)

- [Ruby](/docs/languages/ruby/)

- [Rust](/docs/languages/rust/)

Every microservice has a specific goal and can communicate with others by using

a global gRPC definition. Persistent information is saved into a PostgreSQL

@@ -159,7 +159,7 @@ find a channel for your language, feel free to start a discussion on the

[OpenTelemetry CNCF Slack channel](https://cloud-native.slack.com/archives/CJFCJHG4Q),

or on [GitHub](https://github.com/open-telemetry/community), like with

[this issue for OTel for Perl](https://github.com/open-telemetry/community/issues/828).

Please also check out [this page](/docs/instrumentation/other/) for more info.

Please also check out [this page](/docs/languages/other/) for more info.

#### 2- Python instrumentation

@@ -190,9 +190,9 @@ agent to the host metrics receiver for infrastructure monitoring.

maturing in OTel; for example, the Java JAR agent takes care of instrumenting

[most libraries](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/supported-libraries.md#libraries--frameworks)

that are used by applications. Auto-instrumentation is also available for

[Python](/docs/instrumentation/python/automatic/),

[.NET](/docs/instrumentation/net/automatic/), and

[Node.js](/docs/instrumentation/js/automatic).

[Python](/docs/languages/python/automatic/),

[.NET](/docs/languages/net/automatic/), and

[Node.js](/docs/languages/js/automatic).

- If you’re using Kubernetes, they can use the

[OTel operator](https://github.com/open-telemetry/opentelemetry-operator),

which takes care of instrumentations for applications deployed on K8s. The

@@ -118,8 +118,7 @@ analysis.

### How do you generate traces?

To instrument their code, they configure the

[Node.js SDK](/docs/instrumentation/js/getting-started/nodejs/) and use a number

of

[Node.js SDK](/docs/languages/js/getting-started/nodejs/) and use a number of

[Node.js auto-instrumentation plug-ins](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node).

While the team is currently only using

[auto-instrumentation](/docs/specs/otel/glossary/#automatic-instrumentation) to

@@ -135,9 +135,9 @@ experience OpenTelemetry in action:

- Seeing structured logs, being able to correlate traces and logs, and emitting

metrics.

- Experiencing the benefits of

[context propagation](/docs/instrumentation/js/propagation/) – i.e. spans and

traces interacting across different operations to provide an end-to-end view

of a service call.

[context propagation](/docs/languages/js/propagation/) – i.e. spans and traces

interacting across different operations to provide an end-to-end view of a

service call.

### How did you promote OpenTelemetry across the organization?

@@ -473,7 +473,7 @@ check out the following resources:

[otel-logs-events]: /docs/specs/otel/logs/event-api/

[otel-semconv-logs]: /docs/specs/semconv/general/logs/

[otel-python-repo]: https://github.com/open-telemetry/opentelemetry-python

[otel-python]: /docs/instrumentation/python/

[otel-python]: /docs/languages/python/

[py-docs-logs]:

https://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation/logging/logging.html

[py-docs-logs-example]: