[IA] Rename net to dotnet in /docs/{languages,zero-code}/net, add redirects and adjust links (#6590)

Author: chalin

.htmltest.yml

@@ -28,7 +28,7 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
   - ^/api/?$
   - ^((/..)?/docs/languages/\w+|\.\.)/(api|examples|registry)/$
   - ^(/..)?/docs/collector/registry/$
-  - ^(/..)?/docs/languages/net/(metrics-api|traces-api)/
+  - ^(/..)?/docs/languages/dotnet/(metrics-api|traces-api)/
   - ^((/..)?/docs/migration/)?opencensus/$
   - ^(/community/end-user/)?feedback-survey/$
   - ^/../docs/specs/?$ # non-default locale spec redirect

content/en/blog/2022/frontend-overhaul/index.md

@@ -55,7 +55,7 @@ The demo’s stack includes multiple microservices in different languages,
 covering each of the following OTel-supported languages:
 
 - [C++](/docs/languages/cpp/)
-- [.NET](/docs/languages/net/)
+- [.NET](/docs/languages/dotnet/)
 - [Erlang/Elixir](/docs/languages/erlang/)
 - [Go](/docs/languages/go/)
 - [Node.js](/docs/languages/js/)

content/en/blog/2023/end-user-discussions-03.md

@@ -190,7 +190,7 @@ 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/zero-code/python/), [.NET](/docs/zero-code/net/), and
+  [Python](/docs/zero-code/python/), [.NET](/docs/zero-code/dotnet/), and
   [Node.js](/docs/zero-code/js/).
 - If you’re using Kubernetes, they can use the
   [OTel operator](https://github.com/open-telemetry/opentelemetry-operator),

content/en/blog/2023/otel-dotnet-auto-instrumentation.md

@@ -20,7 +20,7 @@ package that simplify the task of deploying and configuring the collection of
 telemetry. The automatic instrumentation is fully compatible with manual
 instrumentation in case you need to send custom spans or metrics.
 
-To get started, [read the documentation](/docs/zero-code/net) or browse the
+To get started, [read the documentation](/docs/zero-code/dotnet) or browse the
 [examples](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/tree/main/examples)
 for demonstrations of different instrumentation scenarios covered by the
 OpenTelemetry .NET Automatic Instrumentation.

content/en/blog/2023/otel-in-focus-02.md

@@ -76,7 +76,7 @@ planning a release of new documentation for PHP soon.
 has been released with deprecations to Jaeger exporters, several performance
 improvements and bugfixes, and changes to Prometheus export.
 
-##### [.NET](/docs/languages/net/)
+##### [.NET](/docs/languages/dotnet/)
 
 [v1.4](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.4.0)
 removes several deprecated extension methods.

content/en/blog/2023/otel-in-focus-05.md

@@ -86,7 +86,7 @@ exporting, and suppressing instrumentation.
   `opentelemetry.sdk.metrics.view`
 - Fix headers types mismatch for OTLP Exporters
 
-#### [.NET](/docs/languages/net/)
+#### [.NET](/docs/languages/dotnet/)
 
 [Version 1.5.0-rc1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.5.0-rc.1)
 includes many bugfixes across a variety of packages.

content/en/blog/2023/otel-in-focus-06.md

@@ -113,7 +113,7 @@ has been released, requiring some migrations to be performed.
 [Version 1.14](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v1.14.0)
 includes an optional `forceFlush` method to the `SpanExporter` interface.
 
-#### [.NET](/docs/languages/net/)
+#### [.NET](/docs/languages/dotnet/)
 
 [Version 1.5.1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.5.1)
 has been released, as well as 1.5.0. 1.5.1 is a fix for issues introduced in

content/en/blog/2023/otel-in-focus-07.md

@@ -72,7 +72,7 @@ includes updates to OTLP and log support.
 includes metric bug fixes for histograms and exponential histograms. In
 addition, OTLP support has been updated.
 
-#### [.NET](/docs/languages/net/)
+#### [.NET](/docs/languages/dotnet/)
 
 [Version 1.6.0-alpha.1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.6.0-alpha.1)
 has been released. 1.6 re-introduces support for exemplars, as well as

content/en/blog/2023/otel-in-focus-08.md

@@ -89,7 +89,7 @@ the OTLP exporter.
 [Version 1.15.2](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v1.15.1)
 fixes several bugs.
 
-#### [.NET](/docs/languages/net/)
+#### [.NET](/docs/languages/dotnet/)
 
 [Version 1.6.0-rc.1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.6.0-rc.1)
 has been released, bringing small changes to metrics, export, and an

content/en/blog/2023/otel-in-focus-09.md

@@ -188,7 +188,7 @@ fixes an unintentional breaking change in previous releases.
 There have been several important changes in the experimental packages,
 including deprecation of legacy configuration APIs.
 
-#### [.NET](/docs/languages/net/)
+#### [.NET](/docs/languages/dotnet/)
 
 [Version 1.6.0](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.6.0)
 includes minor updates to metrics.

content/en/blog/2023/otel-in-focus-10.md

@@ -119,7 +119,7 @@ fixes several bugs in tracing and metrics. Experimental builds include several
 bug fixes and enhancements to the logging exporter, the deprecation of direct
 Jaeger export, and more.
 
-#### [.NET](/docs/languages/net/)
+#### [.NET](/docs/languages/dotnet/)
 
 [Version 1.7.0-alpha](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.7.0-alpha.1)
 includes many bug fixes and updates, including some breaking changes.

content/en/docs/concepts/instrumentation/zero-code/index.md

@@ -46,7 +46,7 @@ Other configuration options are available, including:
 
 Automatic instrumentation is available for the following languages:
 
-- [.NET](/docs/zero-code/net/)
+- [.NET](/docs/zero-code/dotnet/)
 - [Go](/docs/zero-code/go)
 - [Java](/docs/zero-code/java/)
 - [JavaScript](/docs/zero-code/js/)

content/en/docs/getting-started/dev.md

@@ -26,7 +26,7 @@ Next, you can deep dive into the documentations for the
 [language](../../languages/) you are using:
 
 - [C++](../../languages/cpp/)
-- [.NET](../../languages/net/)
+- [.NET](../../languages/dotnet/)
 - [Erlang / Elixir](../../languages/erlang/)
 - [Go](../../languages/go/)
 - [Java](../../languages/java/)

content/en/docs/languages/_index.md

@@ -5,7 +5,9 @@ description:
   languages
 weight: 250
 aliases: [/docs/instrumentation]
-redirects: [{ from: /docs/instrumentation/*, to: ':splat' }] # Only for `en`
+redirects:
+  - { from: /docs/instrumentation/*, to: ':splat' } # Only for `en`
+  - { from: 'net/*', to: 'dotnet/:splat' }
 ---
 
 OpenTelemetry code [instrumentation][] is supported for the languages listed in

content/en/docs/languages/net/_index.md renamed to content/en/docs/languages/dotnet/_index.md

@@ -3,7 +3,7 @@ title: .NET
 description: >
   <img width="35" class="img-initial" src="/img/logos/32x32/dotnet.svg"
   alt=".NET"> A language-specific implementation of OpenTelemetry in .NET.
-aliases: [/csharp, /csharp/metrics, /csharp/tracing]
+aliases: [net, /csharp, /csharp/metrics, /csharp/tracing]
 weight: 12
 ---
 

content/en/docs/languages/net/examples.md renamed to content/en/docs/languages/dotnet/examples.md

@@ -8,7 +8,7 @@ cSpell:ignore: ASPNETCORE rolldice
 This page will show you how to get started with OpenTelemetry in .NET.
 
 If you are looking for a way to automatically instrument your application, check
-out [this guide](/docs/zero-code/net/getting-started/).
+out [this guide](/docs/zero-code/dotnet/getting-started/).
 
 You will learn how you can instrument a simple .NET application, in such a way
 that [traces][], [metrics][] and [logs][] are emitted to the console.
@@ -28,7 +28,7 @@ you can use OpenTelemetry .NET with other frameworks as well. For a complete
 list of libraries for supported frameworks, see the
 [registry](/ecosystem/registry/?component=instrumentation&language=dotnet).
 
-For more elaborate examples, see [examples](/docs/languages/net/examples/).
+For more elaborate examples, see [examples](/docs/languages/dotnet/examples/).
 
 ### Create and launch an HTTP Server
 
@@ -264,9 +264,10 @@ Value: Sum: 1330.4766000000002 Count: 5 Min: 50.0333 Max: 465.7936
 For more:
 
 - Run this example with another [exporter][] for telemetry data.
-- Try [automatic instrumentation](/docs/zero-code/net/) on one of your own apps.
+- Try [automatic instrumentation](/docs/zero-code/dotnet/) on one of your own
+  apps.
 - Learn about [manual instrumentation][] and try out more
-  [examples](/docs/languages/net/examples/).
+  [examples](/docs/languages/dotnet/examples/).
 - Take a look at the [OpenTelemetry Demo](/docs/demo/), which includes .NET
   based [Cart Service](/docs/demo/services/cart/).
 

content/en/docs/languages/net/exporters.md renamed to content/en/docs/languages/dotnet/exporters.md

@@ -12,12 +12,12 @@ cSpell:ignore: dicelib rolldice
 
 On this page you will learn how you can add traces, metrics and logs to your
 code manually. You are not limited to using one kind of instrumentation: you can
-also use [automatic instrumentation](/docs/zero-code/net/) to get started and
+also use [automatic instrumentation](/docs/zero-code/dotnet/) to get started and
 then enrich your code with manual instrumentation as needed.
 
 Also, for libraries your code depends on, you don't have to write
 instrumentation code yourself, since they might be already instrumented or there
-are [instrumentation libraries](/docs/languages/net/libraries/) for them.
+are [instrumentation libraries](/docs/languages/dotnet/libraries/) for them.
 
 {{% /alert %}}
 
@@ -39,8 +39,8 @@ you can refer to the [OpenTelemetry API Shim docs for tracing](../shim).
 ## Example app preparation {#example-app}
 
 This page uses a modified version of the example app from
-[Getting Started](/docs/languages/net/getting-started/) to help you learn about
-manual instrumentation.
+[Getting Started](/docs/languages/dotnet/getting-started/) to help you learn
+about manual instrumentation.
 
 You don't have to use the example app: if you want to instrument your own app or
 library, follow the instructions here to adapt the process to your own code.
@@ -307,15 +307,15 @@ loggerFactory.Dispose();
 For debugging and local development purposes, the example exports telemetry to
 the console. After you have finished setting up manual instrumentation, you need
 to configure an appropriate exporter to
-[export the app's telemetry data](/docs/languages/net/exporters/) to one or more
-telemetry backends.
+[export the app's telemetry data](/docs/languages/dotnet/exporters/) to one or
+more telemetry backends.
 
 The example also sets up the mandatory SDK default attribute `service.name`,
 which holds the logical name of the service, and the optional, but highly
 encouraged, attribute `service.version`, which holds the version of the service
 API or implementation. Alternative methods exist for setting up resource
 attributes. For more information, see
-[Resources](/docs/languages/net/resources/).
+[Resources](/docs/languages/dotnet/resources/).
 
 To verify your code, build and run the app:
 
@@ -670,13 +670,13 @@ private int rollOnce()
 
 The documentation for the metrics API & SDK is missing, you can help make it
 available by
-[editing this page](https://github.com/open-telemetry/opentelemetry.io/edit/main/content/en/docs/languages/net/instrumentation.md).
+[editing this page](https://github.com/open-telemetry/opentelemetry.io/edit/main/content/en/docs/languages/dotnet/instrumentation.md).
 
 ## Logs
 
 The documentation for the logs API and SDK is missing. You can help make it
 available by
-[editing this page](https://github.com/open-telemetry/opentelemetry.io/edit/main/content/en/docs/languages/net/instrumentation.md).
+[editing this page](https://github.com/open-telemetry/opentelemetry.io/edit/main/content/en/docs/languages/dotnet/instrumentation.md).
 
 ## Next steps
 
@@ -689,5 +689,5 @@ You'll also want to configure an appropriate exporter to
 [export your telemetry data](../exporters/) to one or more telemetry backends.
 
 You can also check the
-[automatic instrumentation for .NET](/docs/zero-code/net/), which is currently
-in beta.
+[automatic instrumentation for .NET](/docs/zero-code/dotnet/), which is
+currently in beta.

content/en/docs/languages/net/getting-started.md renamed to content/en/docs/languages/dotnet/getting-started.md

@@ -116,19 +116,19 @@ You can also find more instrumentations available in the
 ## Next steps
 
 After you have set up instrumentation libraries, you may want to add your own
-[instrumentation](/docs/languages/net/instrumentation) to your code, to collect
-custom telemetry data.
+[instrumentation](/docs/languages/dotnet/instrumentation) to your code, to
+collect custom telemetry data.
 
 If you are using .NET Framework 4.x instead of modern .NET, refer to the
-[.NET Framework docs](/docs/languages/net/netframework) to configure
+[.NET Framework docs](/docs/languages/dotnet/netframework) to configure
 OpenTelemetry and instrumentation libraries on .NET Framework.
 
 You'll also want to configure an appropriate exporter to
-[export your telemetry data](/docs/languages/net/exporters) to one or more
+[export your telemetry data](/docs/languages/dotnet/exporters) to one or more
 telemetry backends.
 
 You can also check the
-[automatic instrumentation for .NET](/docs/zero-code/net), which is currently in
-beta.
+[automatic instrumentation for .NET](/docs/zero-code/dotnet), which is currently
+in beta.
 
 [opentelemetry-dotnet]: https://github.com/open-telemetry/opentelemetry-dotnet

content/en/docs/languages/net/instrumentation.md renamed to content/en/docs/languages/dotnet/instrumentation.md

@@ -146,13 +146,13 @@ exception on the `Activity` itself as an `ActivityEvent`.
 
 After you have observability generated automatically with instrumentation
 libraries, you may want to add
-[manual instrumentation](/docs/languages/net/instrumentation) to collect custom
-telemetry data.
+[manual instrumentation](/docs/languages/dotnet/instrumentation) to collect
+custom telemetry data.
 
 You'll also want to configure an appropriate exporter to
-[export your telemetry data](/docs/languages/net/exporters) to one or more
+[export your telemetry data](/docs/languages/dotnet/exporters) to one or more
 telemetry backends.
 
 You can also check the
-[automatic instrumentation for .NET](/docs/zero-code/net), which is currently in
-beta.
+[automatic instrumentation for .NET](/docs/zero-code/dotnet), which is currently
+in beta.

content/en/docs/languages/net/libraries.md renamed to content/en/docs/languages/dotnet/libraries.md

@@ -137,7 +137,7 @@ code, the values in code take precedence.
 There are more resource detectors you can add to your configuration, for example
 to get details about your [Cloud] environment or [Deployment][].
 
-[getting started]: /docs/languages/net/getting-started/
+[getting started]: /docs/languages/dotnet/getting-started/
 [host]: /docs/specs/semconv/resource/host/
 [cloud]: /docs/specs/semconv/resource/cloud/
 [deployment]: /docs/specs/semconv/resource/deployment-environment/

content/en/docs/languages/net/metrics-api.md renamed to content/en/docs/languages/dotnet/metrics-api.md

@@ -413,10 +413,10 @@ This will capture things like the current stack trace as attributes in the span.
 ## Next steps
 
 After you've setup manual instrumentation, you may want to use
-[instrumentation libraries](/docs/languages/net/libraries). Instrumentation
+[instrumentation libraries](/docs/languages/dotnet/libraries). Instrumentation
 libraries will instrument relevant libraries you're using and generate data for
 things like inbound and outbound HTTP requests and more.
 
 You'll also want to configure an appropriate exporter to
-[export your telemetry data](/docs/languages/net/exporters) to one or more
+[export your telemetry data](/docs/languages/dotnet/exporters) to one or more
 telemetry backends.

content/en/docs/languages/net/netframework.md renamed to content/en/docs/languages/dotnet/netframework.md

@@ -181,7 +181,7 @@ For details on how each OpenTracing shim works, see the appropriate
 language-specific documentation. For details on the design of the OpenTracing
 shim, see [OpenTracing Compatibility][ot_spec].
 
-[.net]: /docs/languages/net/shim/
+[.net]: /docs/languages/dotnet/shim/
 [go]: https://pkg.go.dev/go.opentelemetry.io/otel/bridge/opentracing
 [java]:
   https://github.com/open-telemetry/opentelemetry-java/tree/main/opentracing-shim

content/en/docs/languages/net/registry.md renamed to content/en/docs/languages/dotnet/registry.md

@@ -178,7 +178,7 @@ spec:
 
 #### Learn more {#dotnet-learn-more}
 
-For more details, see [.NET Auto Instrumentation docs](/docs/zero-code/net/).
+For more details, see [.NET Auto Instrumentation docs](/docs/zero-code/dotnet/).
 
 ### Deno
 

content/en/docs/languages/net/resources.md renamed to content/en/docs/languages/dotnet/resources.md

@@ -1,5 +1,6 @@
 ---
 title: Zero-code Instrumentation
+redirects: [{ from: 'net/*', to: 'dotnet/:splat' }]
 weight: 260
 ---
 

content/en/docs/languages/net/shim.md renamed to content/en/docs/languages/dotnet/shim.md

@@ -2,8 +2,9 @@
 title: .NET zero-code instrumentation
 description: Send traces and metrics from .NET applications and services.
 linkTitle: .NET
-weight: 30
+aliases: [net]
 redirects: [{ from: /docs/languages/net/automatic/*, to: ':splat' }]
+weight: 30
 cSpell:ignore: coreutils HKLM iisreset myapp
 ---
 
@@ -12,7 +13,7 @@ from .NET applications and services to observability backends without having to
 modify their source code.
 
 To learn how to instrument your service or application code, read
-[Manual instrumentation](/docs/languages/net/instrumentation).
+[Manual instrumentation](/docs/languages/dotnet/instrumentation).
 
 ## Compatibility
 
@@ -295,5 +296,5 @@ For general troubleshooting steps and solutions to specific issues, see
 
 After you have automatic instrumentation configured for your app or service, you
 might want to [send custom traces and metrics](./custom) or add
-[manual instrumentation](/docs/languages/net/instrumentation) to collect custom
-telemetry data.
+[manual instrumentation](/docs/languages/dotnet/instrumentation) to collect
+custom telemetry data.

content/en/docs/languages/net/traces-api.md renamed to content/en/docs/languages/dotnet/traces-api.md

@@ -87,4 +87,4 @@ To create your custom metrics manually, follow these steps:
 
 ## Further reading
 
-- [OpenTelemetry.io documentation for .NET Manual Instrumentation](/docs/languages/net/instrumentation#setting-up-an-activitysource)
+- [OpenTelemetry.io documentation for .NET Manual Instrumentation](/docs/languages/dotnet/instrumentation#setting-up-an-activitysource)

content/en/docs/migration/opentracing.md

@@ -9,7 +9,7 @@ This page will show you how to get started with OpenTelemetry .NET Automatic
 Instrumentation.
 
 If you are looking for a way to manually instrument your application, check out
-[this guide](/docs/languages/net/getting-started).
+[this guide](/docs/languages/dotnet/getting-started).
 
 You will learn how you can instrument a simple .NET application automatically,
 in such a way that [traces][], [metrics][] and [logs][] are emitted to the
@@ -28,7 +28,7 @@ The following example uses a basic
 application. If you are not using ASP.NET Core, that's OK — you can still use
 OpenTelemetry .NET Automatic Instrumentation.
 
-For more elaborate examples, see [examples](/docs/languages/net/examples/).
+For more elaborate examples, see [examples](/docs/languages/dotnet/examples/).
 
 ### Create and launch an HTTP Server
 

content/en/docs/platforms/kubernetes/operator/automatic.md

@@ -28,7 +28,7 @@ Luego, puedes profundizar en la documentación por
 [lenguaje de programación](../../languages/) que estás utilizando:
 
 - [C++](../../languages/cpp/)
-- [.NET](../../languages/net/)
+- [.NET](../../languages/dotnet/)
 - [Erlang / Elixir](../../languages/erlang/)
 - [Go](../../languages/go/)
 - [Java](../../languages/java/)

content/en/docs/zero-code/_index.md

@@ -33,7 +33,7 @@ OpenTelemetry を使えば、[コードベースの計装](/docs/concepts/instru
 
 ゼロコード計装は以下の言語に対応しています。
 
-- [.NET](/docs/zero-code/net/)
+- [.NET](/docs/zero-code/dotnet/)
 - [Go](/docs/zero-code/go)
 - [Java](/docs/zero-code/java/)
 - [JavaScript](/docs/zero-code/js/)