feat: [SVLS-6946] rearrange serverless google cloud docs for incremental updates (#30102)

* feat: [SVLLS-6946] rearrange serverless google cloud docs for live updates

* chore: move google cloud under serverless

* chore: fix serverless google cloud index links

* chore: move google_cloud_run doc into serverless/google_cloud directory

* chore: move google cloud run in process docs to serverless/google_cloud directory

* chore: move cloud run functions docs to serverless/google_cloud directory

* chore: move functions 1st gen to serverless/google_cloud

* update structure

* fix menu

* update cloud run index page

* make links located at ``/serverless/google_cloud_run`; keep ``/serverless/google_cloud` as an alias

* fix workload html

* add further reading; fix padding on workloads

* replace workload images with text for more clarity

* hide gen 1 functions from sidebar

* add further erading

* move functions warning labels

* update sidecar & in-process links

* add 1st gen functions to sidebar

* fix link; require google cloud integration

* add info alerts for Google Cloud integration

* fix alert link

* update alerts

* update code text in alerts

* revert .editorconfig

* edits

---------

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

Author: 3 people

config/_default/menus/main.en.yaml

@@ -3353,14 +3353,22 @@ menu:
       parent: serverless
       identifier: serverless_gcr
       weight: 7
-    - name: 1st Gen Functions
-      url: serverless/google_cloud_run/functions_gen1
+    - name: Containers (Sidecar)
+      url: serverless/google_cloud_run/containers
       parent: serverless_gcr
       weight: 701
-    - name: 2nd Gen Functions
-      url: serverless/google_cloud_run/functions
+    - name: Containers (In-Process)
+      url: serverless/google_cloud_run/containers_in_process
       parent: serverless_gcr
       weight: 702
+    - name: Functions
+      url: serverless/google_cloud_run/functions
+      parent: serverless_gcr
+      weight: 703
+    - name: Functions (1st generation)
+      url: serverless/google_cloud_run/functions_1st_gen
+      parent: serverless_gcr
+      weight: 704
     - name: Glossary
       url: serverless/glossary
       parent: serverless

content/en/serverless/_index.md

@@ -31,7 +31,7 @@ cascade:
 {{< vimeo url="https://player.vimeo.com/progressive_redirect/playback/543362476/rendition/1080p/file.mp4?loc=external&signature=4927d13b131aea1e3b4f77efca5af49bb509f5e7f1d6ca06a5267ba02a8c194a" poster="/images/poster/serverless.png" >}}
 
 <br/>
- 
+
 <div class="alert alert-info">Make sure to check out discussions going on in the <a href="https://datadoghq.slack.com/archives/CFDPB83M4">#serverless</a> channel in the <a href="https://chat.datadoghq.com/">Datadog Slack community</a>.</div>
 
 {{< learning-center-callout header="Join an enablement webinar session" hide_image="true" btn_title="Sign Up" btn_url="https://www.datadoghq.com/technical-enablement/sessions/?tags.topics-0=Serverless">}}
@@ -56,7 +56,7 @@ With [Distributed Tracing][5], you can connect your serverless traces to metrics
 
 ### AWS Step Functions
 
-AWS Step Functions is a serverless orchestration service that lets developers create and manage multi-step application workflows in AWS. 
+AWS Step Functions is a serverless orchestration service that lets developers create and manage multi-step application workflows in AWS.
 
 Monitor metrics and logs from the [AWS Step Functions Integration][13] to view cloud-native telemetry within the Serverless app view.
 
@@ -66,7 +66,7 @@ Enhanced Step Function metrics, which appear in Datadog with the prefix `aws.sta
 
 ### Azure App Service
 
-The [Datadog extension for Azure App Service][7] provides tracing capabilities for Azure Web Apps. 
+The [Datadog extension for Azure App Service][7] provides tracing capabilities for Azure Web Apps.
 
 Use the [Azure App Service view][8] to:
 
@@ -82,7 +82,7 @@ The Datadog extension for Azure App Service provides tracing capabilities for Az
 
 ### Azure Container Apps
 
-Azure Container Apps is a fully managed serverless platform for deploying and scaling container-based applications. Datadog provides monitoring and log collection for Container Apps through the [Azure integration][9]. 
+Azure Container Apps is a fully managed serverless platform for deploying and scaling container-based applications. Datadog provides monitoring and log collection for Container Apps through the [Azure integration][9].
 
 Datadog also provides a solution, now in Preview, for [instrumenting your Container Apps applications][10] with a purpose-built Agent to enable tracing, custom metrics, and direct log collection.
 

content/en/serverless/google_cloud_run/_index.md

@@ -1,5 +1,5 @@
 ---
-title: Google Cloud Run with serverless-init
+title: Instrumenting Google Cloud Run In-Process
 further_reading:
 
 - link: 'https://www.datadoghq.com/blog/collect-traces-logs-from-cloud-run-with-datadog/'
@@ -10,9 +10,15 @@ further_reading:
 
 ## Overview
 
-<div class="alert alert-info">If you are running multiple containers per Google Cloud Run application, Datadog recommends using the Datadog sidecar: <a href="/serverless/google_cloud_run">Instrument Google Cloud Run</a>.</div>
+Google Cloud Run is a fully managed serverless platform for deploying and scaling container-based applications. 
 
-Google Cloud Run is a fully managed serverless platform for deploying and scaling container-based applications. Datadog provides monitoring and log collection for Cloud Run through the [Google Cloud integration][1]. Datadog also provides a solution for instrumenting your Cloud Run applications with a purpose-built Agent to enable tracing, custom metrics, and direct log collection.
+This page provides instructions for instrumenting your Google Cloud Run containers with the Datadog Agent, which enables tracing, custom metrics, and direct log collection.
+
+<div class="alert alert-info">To instrument your Google Cloud Run applications with the Datadog Agent running in a sidecar, see <a href="/serverless/google_cloud_run/containers">Instrument Google Cloud Run with Sidecar</a>.</div>
+
+<div class="alert alert-info">
+<strong>Have you set up your <a href="/integrations/google-cloud-platform/">Google Cloud integration</a>?</strong> Datadog recommends setting up the integration, which collects metrics and logs from Google Cloud services, before proceeding on to instrumentation. Remember to add the <code>cloud asset viewer</code> role to your service account and enable the Cloud Asset Inventory API in Google Cloud.
+</div>
 
 ### Prerequisites
 
@@ -106,7 +112,7 @@ gcr.io/<YOUR_PROJECT>/<YOUR_APP_NAME>
 
 ## Configure your application
 
-Once the container is built and pushed to your registry, the last step is to set the required environment variables for the Datadog Agent:
+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][11] 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" >}}.
 
@@ -126,17 +132,17 @@ See [all arguments and flags for `gcloud run deploy`][26].
 
 ## Results
 
-Once the deployment is completed, your metrics and traces are sent to Datadog. In Datadog, navigate to **Infrastructure > Serverless** to see your serverless metrics and traces.
+After the deployment is completed, your metrics and traces are sent to Datadog. In Datadog, navigate to **Infrastructure > Serverless** to see your serverless metrics and traces.
 
 ## Additional configurations
 
-- **Advanced Tracing:** The Datadog Agent already provides some basic tracing for popular frameworks. Follow the [advanced tracing guide][2] for more information.
+- **Advanced tracing:** The Datadog Agent already provides some basic tracing for popular frameworks. Follow the [advanced tracing guide][2] for more information.
 
 - **Logs:** If you use the [Google Cloud integration][1], your logs are already being collected. Alternatively, you can set the `DD_LOGS_ENABLED` environment variable to `true` to capture application logs through the serverless instrumentation directly.
 
-- **Custom Metrics:** You can submit custom metrics using a [DogStatsD client][4]. For monitoring Cloud Run and other serverless applications, use [distribution][9] metrics. Distributions provide `avg`, `sum`, `max`, `min`, and `count` aggregations by default. On the Metric Summary page, you can enable percentile aggregations (p50, p75, p90, p95, p99) and also manage tags. To monitor a distribution for a gauge metric type, use `avg` for both the [time and space aggregations][11]. To monitor a distribution for a count metric type, use `sum` for both the time and space aggregations.
+- **Custom metrics:** You can submit custom metrics using a [DogStatsD client][4]. For monitoring Cloud Run and other serverless applications, use [distribution][9] metrics. Distributions provide `avg`, `sum`, `max`, `min`, and `count` aggregations by default. On the Metric Summary page, you can enable percentile aggregations (p50, p75, p90, p95, p99) and also manage tags. To monitor a distribution for a gauge metric type, use `avg` for both the [time and space aggregations][11]. To monitor a distribution for a count metric type, use `sum` for both the time and space aggregations.
 
-### Environment Variables
+### Environment variables
 
 | Variable | Description |
 | -------- | ----------- |
@@ -158,7 +164,6 @@ This integration depends on your runtime having a full SSL implementation. If yo
 RUN apt-get update && apt-get install -y ca-certificates
 ```
 
-
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}