Rename other references to in-process

nhulston · nhulston · commit d759fbb57b36 · 2025-08-25T16:01:27.000-04:00
diff --git a/content/en/serverless/azure_functions/_index.md b/content/en/serverless/azure_functions/_index.md
@@ -26,7 +26,7 @@ This page explains how to collect traces, trace metrics, runtime metrics, and cu
    ```js
    require('@datadog/serverless-compat').start();
 
-   // This line must come before importing any instrumented module. 
+   // This line must come before importing any instrumented module.
    const tracer = require('dd-trace').init()
    ```
 
@@ -101,7 +101,7 @@ This page explains how to collect traces, trace metrics, runtime metrics, and cu
    Datadog.Serverless.CompatibilityLayer.Start();
    ```
 
-   If your Azure Function app uses the In-Process model, add a NuGet package reference to `Microsoft.Azure.Functions.Extensions`:
+   If your Azure Function app uses the In-Container model, add a NuGet package reference to `Microsoft.Azure.Functions.Extensions`:
    ```shell
    dotnet package add Microsoft.Azure.Functions.Extensions
    ```
@@ -197,7 +197,7 @@ You can collect [debug logs][6] for troubleshooting. To configure debug logs, us
 `DD_TRACE_DEBUG`
 : Enables (`true`) or disables (`false`) debug logging for the Datadog Tracing Library. Defaults to `false`.
 
-  **Values**: `true`, `false` 
+  **Values**: `true`, `false`
 
 `DD_LOG_LEVEL`
 : Sets logging level for the Datadog Serverless Compatibility Layer. Defaults to `info`.
diff --git a/content/en/serverless/google_cloud_run/containers/_index.md b/content/en/serverless/google_cloud_run/containers/_index.md
@@ -7,9 +7,9 @@ further_reading:
   - link: 'https://www.datadoghq.com/blog/collect-traces-logs-from-cloud-run-with-datadog/'
     tag: 'Blog'
     text: 'Collect traces, logs, and custom metrics from Cloud Run services'
-  - link: "/serverless/google_cloud_run/containers/in_process/"
+  - link: "/serverless/google_cloud_run/containers/in_container/"
     tag: 'Documentation'
-    text: 'Instrument your container with the in-process approach'
+    text: 'Instrument your container with the in-container approach'
   - link: "/serverless/google_cloud_run/containers/sidecar/"
     tag: 'Documentation'
     text: 'Instrument your container with the sidecar approach'
@@ -22,12 +22,12 @@ To instrument your Google Cloud Run containers with Datadog, choose one of two o
 
 {{% gcr-container-options %}}
 
-- [**In-process**][1]: Wraps your application container with the Datadog Agent. Choose this option for a simpler setup, lower cost overhead, and direct log piping.
+- [**In-Container**][1]: Wraps your application container with the Datadog Agent. Choose this option for a simpler setup, lower cost overhead, and direct log piping.
 - [**Sidecar**][2]: Deploys the Datadog Agent in a separate container alongside your app container. Choose this option if you have multiple containers in a single service, if you prefer strict isolation of the Datadog Agent, or if you have performance-sensitive workloads.
 
-## Comparison: in-process versus sidecar instrumentation
+## Comparison: in-container versus sidecar instrumentation
 
-| Aspect                        | In-process                                               | Sidecar                                                                                                                                                      |
+| Aspect                        | In-container                                               | Sidecar                                                                                                                                                      |
 |-------------------------------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Deployment                    | One container (your app, wrapped with the Datadog Agent) | Two containers ( your app, Datadog Agent)                                                                                                                    |
 | Image changes                 | Increases app image size.                                | No change to app image.                                                                                                                                      |
@@ -41,5 +41,5 @@ To instrument your Google Cloud Run containers with Datadog, choose one of two o
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /serverless/google_cloud_run/containers/in_process
+[1]: /serverless/google_cloud_run/containers/in_container
 [2]: /serverless/google_cloud_run/containers/sidecar
diff --git a/content/en/serverless/google_cloud_run/containers/in_container/_index.md b/content/en/serverless/google_cloud_run/containers/in_container/_index.md
@@ -1,5 +1,5 @@
 ---
-title: In-Process Instrumentation
+title: In-Container Instrumentation
 type: multi-code-lang
 aliases:
   - /serverless/google_cloud_run/containers_in_process/
@@ -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_process" %}}
+{{% container-languages path="in_container" %}}
 
 [1]: /integrations/google-cloud-platform/
diff --git a/content/en/serverless/google_cloud_run/containers/in_container/dotnet.md b/content/en/serverless/google_cloud_run/containers/in_container/dotnet.md
@@ -1,5 +1,5 @@
 ---
-title: Instrumenting a .NET Cloud Run Container In-Process
+title: Instrumenting a .NET Cloud Run Container In-Container
 code_lang: dotnet
 type: multi-code-lang
 code_lang_weight: 50
@@ -16,7 +16,7 @@ further_reading:
 
 ## Setup
 
-<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-process/dotnet">available on GitHub</a>.</div>
+<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-container/dotnet">available on GitHub</a>.</div>
 
 1. **Install the Datadog .NET tracer** in your Dockerfile.
 
@@ -78,7 +78,7 @@ logger.LogInformation("Hello World!");
 
    To send custom metrics, [install the DogStatsD client][4] and [view code examples][5].
 
-{{% gcr-env-vars instrumentationMethod="in-process" language="csharp" %}}
+{{% gcr-env-vars instrumentationMethod="in-container" language="csharp" %}}
 
 ## Troubleshooting
 
diff --git a/content/en/serverless/google_cloud_run/containers/in_container/go.md b/content/en/serverless/google_cloud_run/containers/in_container/go.md
@@ -1,5 +1,5 @@
 ---
-title: Instrumenting a Go Cloud Run Container In-Process
+title: Instrumenting a Go Cloud Run Container In-Container
 code_lang: go
 type: multi-code-lang
 code_lang_weight: 30
@@ -16,7 +16,7 @@ further_reading:
 
 ## Setup
 
-<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-process/go">available on GitHub</a>.</div>
+<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-container/go">available on GitHub</a>.</div>
 
 1. **Install the Datadog Go tracer**.
 
@@ -73,7 +73,7 @@ go get github.com/DataDog/dd-trace-go/contrib/net/http/v2
 
    To send custom metrics, [install the DogStatsD client][4] and [view code examples][5].
 
-{{% gcr-env-vars instrumentationMethod="in-process" language="go" %}}
+{{% gcr-env-vars instrumentationMethod="in-container" language="go" %}}
 
 ## Troubleshooting
 
diff --git a/content/en/serverless/google_cloud_run/containers/in_container/java.md b/content/en/serverless/google_cloud_run/containers/in_container/java.md
@@ -1,5 +1,5 @@
 ---
-title: Instrumenting a Java Cloud Run Container In-Process
+title: Instrumenting a Java Cloud Run Container In-Container
 code_lang: java
 type: multi-code-lang
 code_lang_weight: 40
@@ -16,7 +16,7 @@ further_reading:
 
 ## Setup
 
-<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-process/java">available on GitHub</a>.</div>
+<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-container/java">available on GitHub</a>.</div>
 
 1. **Install the Datadog Java tracer**.
 
@@ -88,7 +88,7 @@ logger.info("Hello World!");
 
    To send custom metrics, [install the DogStatsD client][3] and [view code examples][4].
 
-{{% gcr-env-vars instrumentationMethod="in-process" language="java" %}}
+{{% gcr-env-vars instrumentationMethod="in-container" language="java" %}}
 
 ## Troubleshooting
 
diff --git a/content/en/serverless/google_cloud_run/containers/in_container/nodejs.md b/content/en/serverless/google_cloud_run/containers/in_container/nodejs.md
@@ -1,5 +1,5 @@
 ---
-title: Instrumenting a Node.js Cloud Run Container In-Process
+title: Instrumenting a Node.js Cloud Run Container In-Container
 code_lang: nodejs
 type: multi-code-lang
 code_lang_weight: 20
@@ -16,7 +16,7 @@ further_reading:
 
 ## Setup
 
-<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-process/node">available on GitHub</a>.</div>
+<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-container/node">available on GitHub</a>.</div>
 
 1. **Install the Datadog Node.js tracer**.
 
@@ -81,7 +81,7 @@ logger.info(`Hello world!`);
 
    To send custom metrics, [view code examples][3].
 
-{{% gcr-env-vars instrumentationMethod="in-process" language="nodejs" %}}
+{{% gcr-env-vars instrumentationMethod="in-container" language="nodejs" %}}
 
 ## Troubleshooting
 
diff --git a/content/en/serverless/google_cloud_run/containers/in_container/php.md b/content/en/serverless/google_cloud_run/containers/in_container/php.md
@@ -1,5 +1,5 @@
 ---
-title: Instrumenting a PHP Cloud Run Container In-Process
+title: Instrumenting a PHP Cloud Run Container In-Container
 code_lang: php
 type: multi-code-lang
 code_lang_weight: 70
@@ -16,7 +16,7 @@ further_reading:
 
 ## Setup
 
-<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-process/php">available on GitHub</a>.</div>
+<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-container/php">available on GitHub</a>.</div>
 
 1. **Install the Datadog PHP tracer** in your Dockerfile.
 
@@ -57,7 +57,7 @@ apk add libgcc
 
    To send custom metrics, [install the DogStatsD client][3] and [view code examples][4].
 
-{{% gcr-env-vars instrumentationMethod="in-process" language="php" %}}
+{{% gcr-env-vars instrumentationMethod="in-container" language="php" %}}
 
 ## Troubleshooting
 
diff --git a/content/en/serverless/google_cloud_run/containers/in_container/python.md b/content/en/serverless/google_cloud_run/containers/in_container/python.md
@@ -1,5 +1,5 @@
 ---
-title: Instrumenting a Python Cloud Run Container In-Process
+title: Instrumenting a Python Cloud Run Container In-Container
 code_lang: python
 type: multi-code-lang
 code_lang_weight: 10
@@ -16,7 +16,7 @@ further_reading:
 
 ## Setup
 
-<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-process/python">available on GitHub</a>.</div>
+<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-container/python">available on GitHub</a>.</div>
 
 1. **Install the Datadog Python tracer**.
 
@@ -78,7 +78,7 @@ logger.info("Hello world!")
 
    To send custom metrics, [install the DogStatsD client][4] and [view code examples][5].
 
-{{% gcr-env-vars instrumentationMethod="in-process" language="python" %}}
+{{% gcr-env-vars instrumentationMethod="in-container" language="python" %}}
 
 ## Troubleshooting
 
diff --git a/content/en/serverless/google_cloud_run/containers/in_container/ruby.md b/content/en/serverless/google_cloud_run/containers/in_container/ruby.md
@@ -1,5 +1,5 @@
 ---
-title: Instrumenting a Ruby Cloud Run Container In-Process
+title: Instrumenting a Ruby Cloud Run Container In-Container
 code_lang: ruby
 type: multi-code-lang
 code_lang_weight: 60
@@ -16,7 +16,7 @@ further_reading:
 
 ## Setup
 
-<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-process/ruby">available on GitHub</a>.</div>
+<div class="alert alert-info">A sample application is <a href="https://github.com/DataDog/serverless-gcp-sample-apps/tree/main/cloud-run/in-container/ruby">available on GitHub</a>.</div>
 
 1. **Install the Datadog Ruby tracer**.
 
@@ -60,7 +60,7 @@ logger.info "Hello world!"
 
    To send custom metrics, [install the DogStatsD client][3] and [view code examples][4].
 
-{{% gcr-env-vars instrumentationMethod="in-process" language="ruby" %}}
+{{% gcr-env-vars instrumentationMethod="in-container" language="ruby" %}}
 
 ## Troubleshooting
 
diff --git a/content/en/serverless/google_cloud_run/functions.md b/content/en/serverless/google_cloud_run/functions.md
@@ -239,7 +239,7 @@ See [Configure labels for services][15] in the Cloud Run documentation for instr
 | `DD_SOURCE`      | See [Unified Service Tagging][13].                                                                                                                                          |
 | `DD_TAGS`        | See [Unified Service Tagging][13].                                                                                                                                          |
 
-Do not use the `DD_LOGS_ENABLED` environment variable. This variable is only used for [in-process container instrumentation][14].
+Do not use the `DD_LOGS_ENABLED` environment variable. This variable is only used for [in-container container instrumentation][14].
 
 You can also find `FUNCTION_TARGET` on the source tab inside Google console: `Function entry point`.
 
@@ -757,6 +757,6 @@ public class Function : IHttpFunction
 [11]: /tracing/other_telemetry/connect_logs_and_traces/go
 [12]: /tracing/other_telemetry/connect_logs_and_traces/ruby
 [13]: /getting_started/tagging/unified_service_tagging/
-[14]: /serverless/google_cloud_run/containers_in_process
+[14]: /serverless/google_cloud_run/containers/in_container/
 [15]: https://cloud.google.com/run/docs/configuring/services/labels
 [16]: https://cloud.google.com/blog/products/serverless/google-cloud-functions-is-now-cloud-run-functions
diff --git a/layouts/shortcodes/gcr-container-options.html b/layouts/shortcodes/gcr-container-options.html
@@ -2,9 +2,9 @@
   <div class="container cards-dd col-num-2">
     <div class="row g-2 g-xl-3 justify-content-center">
       <div class="col">
-        <a class="card h-100" href="/serverless/google_cloud_run/containers/in_process">
+        <a class="card h-100" href="/serverless/google_cloud_run/containers/in_container">
           <div class="card-body text-center d-flex align-items-center justify-content-center p-0" style="min-height: 120px;">
-            <h5 class="m-0">In-Process</h5>
+            <h5 class="m-0">In-Container</h5>
           </div>
         </a>
       </div>
diff --git a/layouts/shortcodes/gcr-env-vars.html b/layouts/shortcodes/gcr-env-vars.html
@@ -7,7 +7,7 @@
 | Variable                 | Description |
 | ------------------------ | ----------- |
 | `DD_API_KEY`             | [Datadog API key][1001] - **Required**|
-| `DD_SITE`                | [Datadog site][1002] - **Required** |{{ if eq (.Get "instrumentationMethod") "in-process" }}
+| `DD_SITE`                | [Datadog site][1002] - **Required** |{{ if eq (.Get "instrumentationMethod") "in-container" }}
 | `DD_LOGS_ENABLED`        | When true, send logs (stdout and stderr) to Datadog. Defaults to false. |{{ end }}{{ if eq (.Get "instrumentationMethod") "sidecar" }}
 | `DD_SERVERLESS_LOG_PATH` | The path where the sidecar should tail logs from. Defaults to `/shared-volume/logs/app.log`. |{{ end }}
 | `DD_LOGS_INJECTION`      | When true, enrich all logs with trace data for supported loggers. See [Correlate Logs and Traces][1003] for more information. {{ if eq (.Get "instrumentationMethod") "sidecar" }}Set in your *main* application container, not the sidecar container.{{ end }}|
