re-organize agent config (#4811)

Co-authored-by: Patrice Chalin <[email protected]>
Co-authored-by: Patrice Chalin <[email protected]>
Co-authored-by: Severin Neumann <[email protected]>

Author: 3 people

content/en/blog/2022/debug-otel-with-otel/index.md

@@ -260,5 +260,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/zero-code/java/agent/configuration/#capturing-http-request-and-response-headers
+  /docs/zero-code/java/agent/instrumentation/http/#capturing-http-request-and-response-headers
 [python]: /docs/zero-code/python/

content/en/docs/faas/lambda-auto-instrument.md

@@ -56,7 +56,7 @@ variables:
   instrumentations, see [Suppressing specific agent instrumentation][1].
 
   [1]:
-    /docs/zero-code/java/agent/configuration/#suppressing-specific-agent-instrumentation
+    /docs/zero-code/java/agent/disable/#suppressing-specific-agent-instrumentation
 
 For example, to only enable auto-instrumentation for Lambda and the AWS SDK, you
 would set the following environment variables:

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

@@ -212,7 +212,7 @@ Therefore, the example uses `http://demo-collector:4318`, which connects to the
 #### Excluding auto-instrumentation {#java-excluding-auto-instrumentation}
 
 By default, the Java auto-instrumentation ships with
-[many instrumentation libraries](/docs/zero-code/java/agent/#supported-libraries-frameworks-application-services-and-jvms).
+[many instrumentation libraries](/docs/zero-code/java/agent/getting-started/#supported-libraries-frameworks-application-services-and-jvms).
 This makes instrumentation easy, but could result in too much or unwanted data.
 If there are any libraries you do not want to use you can set the
 `OTEL_INSTRUMENTATION_[NAME]_ENABLED=false` where `[NAME]` is the name of the
@@ -221,7 +221,7 @@ the default libraries by setting
 `OTEL_INSTRUMENTATION_COMMON_DEFAULT_ENABLED=false` and then use
 `OTEL_INSTRUMENTATION_[NAME]_ENABLED=true` where `[NAME]` is the name of the
 library. For more details, see
-[Suppressing specific instrumentation](/docs/zero-code/java/agent/configuration/#suppressing-specific-instrumentation).
+[Suppressing specific instrumentation](/docs/zero-code/java/agent/disable/).
 
 ```yaml
 apiVersion: opentelemetry.io/v1alpha1

content/en/docs/languages/java/getting-started.md

@@ -248,7 +248,7 @@ For more:
 [metrics]: /docs/concepts/signals/metrics/
 [logs]: /docs/concepts/signals/logs/
 [annotations]: /docs/zero-code/java/agent/annotations/
-[configure the java agent]: /docs/zero-code/java/agent/#configuring-the-agent
+[configure the java agent]: /docs/zero-code/java/agent/configuration/
 [console exporter]:
   https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md#logging-exporter
 [exporter]:

content/en/docs/languages/java/libraries.md

@@ -16,7 +16,7 @@ in order to generate telemetry data for a library or framework.
 The Java agent for automatic instrumentation includes instrumentation libraries
 for many common Java frameworks. Most are turned on by default. If you need to
 turn off certain instrumentation libraries, you can
-[suppress them](/docs/zero-code/java/agent/configuration/#suppressing-specific-instrumentation).
+[suppress them](/docs/zero-code/java/agent/disable/).
 
 If you use [code-based instrumentation](../instrumentation), you can leverage
 some instrumentation libraries for your dependencies standalone. To find out

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

@@ -5,7 +5,6 @@ aliases:
   - /docs/java/automatic_instrumentation
   - /docs/languages/java/automatic_instrumentation
 redirects: [{ from: /docs/languages/java/automatic/*, to: ':splat' }]
-cSpell:ignore: Dotel myapp
 ---
 
 Zero-code instrumentation with Java uses a Java agent JAR attached to any Java
@@ -14,97 +13,3 @@ popular libraries and frameworks. It can be used to capture telemetry data at
 the "edges" of an app or service, such as inbound requests, outbound HTTP calls,
 database calls, and so on. To learn how to manually instrument your service or
 app code, see [Manual instrumentation](/docs/languages/java/instrumentation/).
-
-## Setup
-
-1.  Download [opentelemetry-javaagent.jar][] from [Releases][] of the
-    `opentelemetry-java-instrumentation` repository and place the JAR in your
-    preferred directory. The JAR file contains the agent and instrumentation
-    libraries.
-2.  Add `-javaagent:path/to/opentelemetry-javaagent.jar` and other config to
-    your JVM startup arguments and launch your app:
-
-    - Directly on the startup command:
-
-      ```shell
-      java -javaagent:path/to/opentelemetry-javaagent.jar -Dotel.service.name=your-service-name -jar myapp.jar
-      ```
-
-    - Via the `JAVA_TOOL_OPTIONS` and other environment variables:
-
-      ```shell
-      export JAVA_TOOL_OPTIONS="-javaagent:path/to/opentelemetry-javaagent.jar"
-      export OTEL_SERVICE_NAME="your-service-name"
-      java -jar myapp.jar
-      ```
-
-## Configuring the agent
-
-The agent is highly configurable.
-
-One option is to pass configuration properties via the `-D` flag. In this
-example, a service name and Zipkin exporter for traces are configured:
-
-```sh
-java -javaagent:path/to/opentelemetry-javaagent.jar \
-     -Dotel.service.name=your-service-name \
-     -Dotel.traces.exporter=zipkin \
-     -jar myapp.jar
-```
-
-You can also use environment variables to configure the agent:
-
-```sh
-OTEL_SERVICE_NAME=your-service-name \
-OTEL_TRACES_EXPORTER=zipkin \
-java -javaagent:path/to/opentelemetry-javaagent.jar \
-     -jar myapp.jar
-```
-
-You can also supply a Java properties file and load configuration values from
-there:
-
-```sh
-java -javaagent:path/to/opentelemetry-javaagent.jar \
-     -Dotel.javaagent.configuration-file=path/to/properties/file.properties \
-     -jar myapp.jar
-```
-
-or
-
-```sh
-OTEL_JAVAAGENT_CONFIGURATION_FILE=path/to/properties/file.properties \
-java -javaagent:path/to/opentelemetry-javaagent.jar \
-     -jar myapp.jar
-```
-
-To see the full range of configuration options, see
-[Agent Configuration](configuration).
-
-## Supported libraries, frameworks, application services, and JVMs
-
-The Java agent ships with instrumentation libraries for many popular components.
-For the full list, see [Supported libraries, frameworks, application services,
-and JVMs][support].
-
-## Troubleshooting
-
-{{% config_option name="otel.javaagent.debug" %}}
-
-Set to `true` to see debug logs. Note that these are quite verbose.
-
-{{% /config_option %}}
-
-## Next steps
-
-After you have automatic instrumentation configured for your app or service, you
-might want to [annotate](annotations) selected methods or add
-[manual instrumentation](/docs/languages/java/instrumentation/) to collect
-custom telemetry data.
-
-[opentelemetry-javaagent.jar]:
-  https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/latest/download/opentelemetry-javaagent.jar
-[releases]:
-  https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases
-[support]:
-  https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/supported-libraries.md