Your Site Reliability Engineering (SRE) team is designing a centralized incident response dashboard in Google Cloud Monitoring for an on-call rotation troubleshooting production microservices. The dashboard must satisfy the following operational requirements: Display critical telemetry, including golden signal metric charts and Service Level Objective (SLO) status widgets. Embed clear, step-by-step diagnostic procedures and incident playbooks directly alongside the metric visualizations to minimize context switching during an outage. Provide one-click deep links from the dashboard into Cloud Logging with pre-filtered query parameters alongside correlated, in-dashboard log views. Which dashboard configuration should your team implement in Cloud Monitoring?

Add Descriptive text widgets formatted with Markdown to document diagnostic playbooks and embed URL links directly to pre-filtered Cloud Logging queries, placed adjacent to metric charts, SLO widgets, and Log entries widgets.: ### What Descriptive Text and Log Widgets Are **Descriptive text widgets** in Google Cloud Monitoring custom dashboards allow teams to render rich text using **Markdown syntax**. These widgets can be combined with **Log entries widgets**, **SLO widgets**, and **Metric charts** to create interactive, self-contained incident response playbooks. ### How It Meets the Requirements - **Step-by-step diagnostic procedures**: Markdown text widgets allow engineers to write structured, formatted runbooks—including headers, checklists, and code snippets—directly adjacent to the live metric graphs. - **Direct links to Cloud Logging**: Markdown supports standard hyperlink formatting (`[Link text](url)`), enabling SRE teams to generate direct, parameter-encoded URLs pointing to specific filtered queries in the **Logs Explorer** as well as links to external documentation. - **Correlated logs and metrics**: Adding **Log entries widgets** alongside metric charts and SLO status widgets displays live log streams on the same pane of glass, eliminating context switching during triage. ### Key Advantages - **Unified operational pane**: Eliminates navigation overhead by co-locating metric graphs, log viewers, SLO compliance indicators, and mitigation runbooks. - **Rich formatting**: Markdown natively supports bold emphasis, formatted command-line snippets (`gcloud` / `kubectl`), bullet points, and links. - **Maintainability**: Text widgets can be managed and updated either through the Google Cloud console dashboard editor or programmatically via the Cloud Monitoring API using dashboard JSON representations. ### Why This Is Optimal Cloud Monitoring custom dashboards are purpose-built to combine telemetry visualizations (charts, gauges, SLOs, log streams) with contextual Markdown documentation. This provides on-call engineers with immediate, actionable guidance and deep navigation links at the point of metric degradation.

Cloud Monitoring Dashboard Playbook Markdown Widgets | Professional Cloud DevOps Engineer

Cloud Monitoring Dashboard Playbook Markdown Widgets

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

Your Site Reliability Engineering (SRE) team is designing a centralized incident response dashboard in Google Cloud Monitoring for an on-call rotation troubleshooting production microservices.

The dashboard must satisfy the following operational requirements:

Display critical telemetry, including golden signal metric charts and Service Level Objective (SLO) status widgets.
Embed clear, step-by-step diagnostic procedures and incident playbooks directly alongside the metric visualizations to minimize context switching during an outage.
Provide one-click deep links from the dashboard into Cloud Logging with pre-filtered query parameters alongside correlated, in-dashboard log views.

Which dashboard configuration should your team implement in Cloud Monitoring?

Add Descriptive text widgets formatted with Markdown to document diagnostic playbooks and embed URL links directly to pre-filtered Cloud Logging queries, placed adjacent to metric charts, SLO widgets, and Log entries widgets.

Use Workload Manager predefined dashboards with event markers enabled, relying on default automated remediation playbooks rather than custom widgets.

Embed custom HTML iframe widgets configured to load the company's internal wiki runbook pages and execute client-side scripts that dynamically query the Cloud Logging API.

Configure an alerting policy incident annotation that routes Markdown runbook payloads to BigQuery, requiring on-call engineers to run scheduled SQL queries to extract Cloud Logging URLs.

Professional Cloud DevOps Engineer

Cloud Monitoring Dashboard Playbook Markdown Widgets

Related questions