Cloud Run Functions v2 Docs Refresh (#31440)

* move files from `in_process` to `in_container`

* add aliases

* Rename other references to in-process

* (chore): create functions directory

* (chore): generalize container-languages -> serverless-init-languages for reuse (GCP functions, Azure)

* (feat): create separate pages for each runtime

* Add banner redirecting to 1st gen functions

* fix container languages call

* revert container-languages rename

* add FUNCTION_TARGET env var to table if in function docs

* implement python page

* implement node page

* implement go page

* implement java page

* disable php in container-languages if in functions

* remove duplicated service label

* implement dotnet page

* implement ruby page

* fix ruby DD_SOURCE

* copy edits and image fixing

* also update sidecar container docs

---------

Co-authored-by: cecilia saixue watt <[email protected]>

Author: nhulston

content/en/serverless/google_cloud_run/containers/in_container/_index.md

@@ -10,6 +10,6 @@ First, set up the **[Google Cloud Integration][1]** to collect metrics and logs
 
 Then, instrument your application using one of the following guides:
 
-{{% container-languages path="in_container" %}}
+{{% container-languages path="google_cloud_run/containers/in_container" %}}
 
 [1]: /integrations/google-cloud-platform/

content/en/serverless/google_cloud_run/containers/sidecar/_index.md

@@ -9,6 +9,6 @@ First, set up the [Datadog-Google Cloud Platform integration][1] to collect metr
 
 Then, select your runtime below for instructions on how to instrument your application:
 
-{{% container-languages path="sidecar" %}}
+{{% container-languages path="google_cloud_run/containers/sidecar" %}}
 
 [1]: /integrations/google-cloud-platform/

content/en/serverless/google_cloud_run/containers/sidecar/dotnet.md

@@ -61,9 +61,9 @@ RUN mkdir -p /dd_tracer/dotnet/ && tar -xzvf /tmp/datadog-dotnet-apm.tar.gz -C /
 
 3. **Set up logs**.
 
-   In the previous step, you created a shared volume. Additionally, you set the `DD_SERVERLESS_LOG_PATH` env var, or it was defaulted to `/shared-volume/logs/app.log`.
+   In the previous step, you created a shared volume. You may have also set the `DD_SERVERLESS_LOG_PATH` environment variable, which defaults to `/shared-volume/logs/app.log`.
 
-   Now, you will need to configure your logging library to write logs to that file. In .NET, we recommend writing logs in a JSON format. For example, you can use a third-party logging library such as `Serilog`:
+   In this step, configure your logging library to write logs to that file set in `DD_SERVERLESS_LOG_PATH`. In .NET, we recommend writing logs in a JSON format. For example, you can use a third-party logging library such as `Serilog`:
    {{< code-block lang="csharp" disable_copy="false" >}}
 using Serilog;
 

content/en/serverless/google_cloud_run/containers/sidecar/go.md

@@ -61,9 +61,9 @@ go get github.com/DataDog/dd-trace-go/contrib/net/http/v2
 
 3. **Set up logs**.
 
-   In the previous step, you created a shared volume. Additionally, you set the `DD_SERVERLESS_LOG_PATH` env var, or it was defaulted to `/shared-volume/logs/app.log`.
+   In the previous step, you created a shared volume. You may have also set the `DD_SERVERLESS_LOG_PATH` environment variable, which defaults to `/shared-volume/logs/app.log`.
 
-   Now, you will need to configure your logging library to write logs to that file. In Go, we recommend writing logs in a JSON format. For example, you can use a third-party logging library such as `logrus`:
+   In this step, configure your logging library to write logs to the file set in `DD_SERVERLESS_LOG_PATH`. In Go, we recommend writing logs in a JSON format. For example, you can use a third-party logging library such as `logrus`:
    {{< code-block lang="go" disable_copy="false" >}}
 const LOG_FILE = "/shared-volume/logs/app.log"
 

content/en/serverless/google_cloud_run/containers/sidecar/java.md

@@ -70,9 +70,9 @@ implementation 'com.datadoghq:dd-trace-api:DD_TRACE_JAVA_VERSION_HERE'
 
 3. **Set up logs**.
 
-   In the previous step, you created a shared volume. Additionally, you set the `DD_SERVERLESS_LOG_PATH` env var, or it was defaulted to `/shared-volume/logs/app.log`.
+   In the previous step, you created a shared volume. You may have also set the `DD_SERVERLESS_LOG_PATH` environment variable, which defaults to `/shared-volume/logs/app.log`.
 
-   Now, you will need to configure your logging library to write logs to that file. In Java, we recommend writing logs in a JSON format. For example, you can use a third-party logging library such as `Log4j 2`:
+   In this step, configure your logging library to write logs to the file set in `DD_SERVERLESS_LOG_PATH`. In Java, we recommend writing logs in a JSON format. For example, you can use a third-party logging library such as `Log4j 2`:
 
    {{< code-block lang="java" disable_copy="false" >}}
 private static final Logger logger = LogManager.getLogger(App.class);

content/en/serverless/google_cloud_run/containers/sidecar/nodejs.md

@@ -58,9 +58,9 @@ ENV NODE_OPTIONS="--require dd-trace/init"
 
 3. **Set up logs**.
 
-   In the previous step, you created a shared volume. Additionally, you set the `DD_SERVERLESS_LOG_PATH` env var, or it was defaulted to `/shared-volume/logs/app.log`.
+   In the previous step, you created a shared volume. You may have also set the `DD_SERVERLESS_LOG_PATH` environment variable, which defaults to `/shared-volume/logs/app.log`.
 
-   Now, you will need to configure your logging library to write logs to that file. In Node.js, we recommend writing logs in a JSON format. For example, you can use a third-party logging library such as `winston`:
+   In this step, configure your logging library to write logs to the file set in `DD_SERVERLESS_LOG_PATH`. In Node.js, we recommend writing logs in a JSON format. For example, you can use a third-party logging library such as `winston`:
    {{< code-block lang="javascript" disable_copy="false" >}}
 const tracer = require('dd-trace').init({
   logInjection: true,

content/en/serverless/google_cloud_run/containers/sidecar/php.md

@@ -53,9 +53,9 @@ apk add libgcc
 
 3. **Set up logs**.
 
-   In the previous step, you created a shared volume. Additionally, you set the `DD_SERVERLESS_LOG_PATH` env var, or it was defaulted to `/shared-volume/logs/app.log`.
+   In the previous step, you created a shared volume. You may have also set the `DD_SERVERLESS_LOG_PATH` environment variable, which defaults to `/shared-volume/logs/app.log`.
 
-   Now, you will need to configure your logging library to write logs to that file. For example:
+   In this step, configure your logging library to write logs to the file set in `DD_SERVERLESS_LOG_PATH`. For example:
 
    {{< code-block lang="php" disable_copy="false" >}}
 const LOG_FILE = "/shared-volume/logs/app.log";

content/en/serverless/google_cloud_run/containers/sidecar/python.md

@@ -50,9 +50,9 @@ RUN pip install ddtrace
 
 3. **Set up logs**.
 
-   In the previous step, you created a shared volume. Additionally, you set the `DD_SERVERLESS_LOG_PATH` env var, or it was defaulted to `/shared-volume/logs/app.log`.
+   In the previous step, you created a shared volume. You may have also set the `DD_SERVERLESS_LOG_PATH` environment variable, which defaults to `/shared-volume/logs/app.log`.
 
-   Now, you will need to configure your logging library to write logs to that file. You can also set a custom format for log/trace correlation and other features. Datadog recommends setting the following environment variables:
+   In this step, configure your logging library to write logs to the file set in `DD_SERVERLESS_LOG_PATH`. You can also set a custom format for log/trace correlation and other features. Datadog recommends setting the following environment variables:
    - `ENV PYTHONUNBUFFERED=1`: In your main container. Ensure Python outputs appear immediately in container logs instead of being buffered.
    - `ENV DD_LOGS_INJECTION=true`: In your main container. Enable log/trace correlation for supported loggers.
    - `DD_SOURCE=python`: In your sidecar container. Enable advanced Datadog log parsing.

content/en/serverless/google_cloud_run/containers/sidecar/ruby.md

@@ -46,9 +46,9 @@ gem 'datadog'
 
 3. **Set up logs**.
 
-   In the previous step, you created a shared volume. Additionally, you set the `DD_SERVERLESS_LOG_PATH` env var, or it was defaulted to `/shared-volume/logs/app.log`.
+   In the previous step, you created a shared volume. Additionally, you may have also set the `DD_SERVERLESS_LOG_PATH` environment variable, which defaults to `/shared-volume/logs/app.log`.
 
-   Now, you will need to configure your logging library to write logs to that file. You can also set a custom format for log/trace correlation and other features. Datadog recommends setting the environment variable `DD_SOURCE=go` in your sidecar container to enable advanced Datadog log parsing.
+   In this step, configure your logging library to write logs to the file set in `DD_SERVERLESS_LOG_PATH`. You can also set a custom format for log/trace correlation and other features. Datadog recommends setting the environment variable `DD_SOURCE=ruby` in your sidecar container to enable advanced Datadog log parsing.
 
    Then, update your logging library. For example, you can use Ruby's native `logger` library:
    {{< code-block lang="ruby" disable_copy="false" >}}