add configuration section

Author: nhulston

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

@@ -1,7 +1,7 @@
 ---
 title: Instrumenting a Node.js Cloud Run Container In-Process
 further_reading:
-- link: '/tracing/trace_collection/automatic_instrumentation/dd_libraries/nodejs/#getting-started'
+- link: '/tracing/trace_collection/automatic_instrumentation/dd_libraries/nodejs/'
   tag: 'Documentation'
   text: 'Tracing Node.js Applications'
 ---
@@ -21,7 +21,7 @@ const tracer = require('dd-trace').init({
 });
 ```
 
-For more information, see [Tracing Node.js applications](https://docs.datadoghq.com/tracing/trace_collection/automatic_instrumentation/dd_libraries/nodejs/#getting-started).
+For more information, see [Tracing Node.js applications][1].
 
 ## 2. Install Serverless-Init
 
@@ -30,9 +30,6 @@ Add the following instructions and arguments to your Dockerfile.
 ```dockerfile
 COPY --from=datadog/serverless-init:1 /datadog-init /app/datadog-init
 ENV NODE_OPTIONS="--require dd-trace/init"
-ENV DD_SERVICE=datadog-demo-run-nodejs
-ENV DD_ENV=datadog-demo
-ENV DD_VERSION=1
 ENTRYPOINT ["/app/datadog-init"]
 CMD ["/nodejs/bin/node", "/path/to/your/app.js"]
 ```
@@ -51,22 +48,14 @@ CMD ["/nodejs/bin/node", "/path/to/your/app.js"]
    ENV NODE_OPTIONS="--require dd-trace/init"
    ```
 
-3. (Optional) Add Datadog tags.
-
-   ```dockerfile
-   ENV DD_SERVICE=datadog-demo-run-nodejs
-   ENV DD_ENV=datadog-demo
-   ENV DD_VERSION=1
-   ```
-
-4. Change the entrypoint to wrap your application in the Datadog `serverless-init` process.
+3. Change the entrypoint to wrap your application in the Datadog `serverless-init` process.
    **Note**: If you already have an entrypoint defined inside your Dockerfile, see the [alternative configuration](#alt-node).
 
    ```dockerfile
    ENTRYPOINT ["/app/datadog-init"]
    ```
 
-5. Execute your binary application wrapped in the entrypoint. Adapt this line to your needs.
+4. Execute your binary application wrapped in the entrypoint. Adapt this line to your needs.
    ```dockerfile
    CMD ["node", "/path/to/your/app.js"]
    ```
@@ -99,10 +88,19 @@ const logger = createLogger({
   exitOnError: false,
   format: format.json(),
   transports: [
-    new transports.File({ filename: `/shared-volume/logs/app.log` }),
     new transports.Console()
   ],
 });
 
 logger.info(`Hello world!`);
 ```
+
+## 4. Configure your application
+
+{{% gcr-configure-env-vars %}}
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /tracing/trace_collection/automatic_instrumentation/dd_libraries/nodejs/

layouts/shortcodes/gcr-configure-env-vars.md

@@ -0,0 +1,34 @@
+After the container is built and pushed to your registry, set the required environment variables for the Datadog Agent:
+
+- `DD_API_KEY`: Datadog API key, used to send data to your Datadog account. It should be configured as a Google Cloud Secret for privacy and safety.
+- `DD_SITE`: Datadog endpoint and website. Select your site on the right side of this page. Your site is: {{< region-param key="dd_site" code="true" >}}.
+
+For more environment variables and their function, see [Environment Variables](#environment-variables).
+
+The following command deploys the service and allows any external connection to reach it. In this example, your service listening is set to port 8080. Ensure that this port number matches the exposed port inside of your Dockerfile.
+
+```shell
+gcloud run deploy <APP_NAME>
+  --image=gcr.io/<YOUR_PROJECT>/<APP_NAME> \
+  --port=8080 \
+  --update-env-vars=DD_API_KEY=$DD_API_KEY \
+  --update-env-vars=DD_SITE=$DD_SITE \
+```
+
+### Environment variables
+
+| Variable | Description |
+| -------- | ----------- |
+| `DD_API_KEY` | [Datadog API key][1] - **Required**|
+| `DD_SITE` | [Datadog site][2] - **Required** |
+| `DD_LOGS_ENABLED` | When true, send logs (stdout and stderr) to Datadog. Defaults to false. |
+| `DD_SERVICE`      | See [Unified Service Tagging][3].                                  |
+| `DD_VERSION`      | See [Unified Service Tagging][3].                                  |
+| `DD_ENV`          | See [Unified Service Tagging][3].                                  |
+| `DD_SOURCE`       | See [Unified Service Tagging][3].                                  |
+| `DD_TAGS`         | See [Unified Service Tagging][3].                                  |
+
+
+[1]: /account_management/api-app-keys/#api-keys
+[2]: /getting_started/site/
+[3]: /getting_started/tagging/unified_service_tagging/