Overview
The Gemini Cloud Assist Investigations preview feature uses Gemini advanced capabilities to assist in creating and running Managed Service for Apache Spark clusters and jobs. This feature analyzes failed clusters and failed and slow-running jobs to identify root causes and recommend fixes. It creates persistent analysis that you can review, save, and share with Google Cloud support to facilitating collaboration and accelerate issue resolution.
Features
Use this feature to create investigations from the Google Cloud console:
- Add a natural language context description to an issue before creating an investigation.
- Analyse failed clusters and slow and failed jobs.
- Get insights into issue root causes with recommended fixes.
- Create Google Cloud support cases with the full investigation context attached.
Before you begin
To get started using the Investigation feature, in your Google Cloud project, enable the Gemini Cloud Assist API.
Create an investigation
To create an investigation, do the following:
In the Google Cloud console, go to the Cloud Assist Investigations page.
Click Create.
Describe the issue: Provide a description of the cluster or job issue.
Select time range: Prove a time range when the issue occurred (default is 30 minutes).
Select resources:
- Click Add resource.
- In the Quick filters field, type "dataproc", and then select one
or more of
dataproc.Batch,dataproc.Job, ordataproc.Clusteras filters. - Select the listed batch, job, or cluster to investigate.
- In the Quick filters field, type "dataproc", and then select one
or more of
- Click Add resource.
Click Create.
Interpret investigation results
Once an investigation is complete, the Investigation details page opens. This page contains the full Gemini analysis, which is organized into the following sections:
- Issue: A collapsed section containing auto-populated details of the job being investigated.
- Relevant Observations: A collapsed section that lists key data points and anomalies that Gemini found during its analysis of logs and metrics.
- Hypotheses: This is the primary section, which is expanded by default.
It presents a list of potential root causes for the observed issue. Each
hypothesis includes:
- Overview: A description of the possible cause, such as "High Shuffle Write Time and Potential Task Skew."
- Recommended Fixes: A list of actionable steps to address the potential issue.
Take action
After reviewing the hypotheses and recommendations:
Apply one or more of the suggested fixes to the job configuration or code, and then rerun the job.
Provide feedback on the helpfulness of the investigation by clicking the thumbs-up or thumbs-down icons at the top of the panel.
Review and escalate investigations
The results of a previously run investigation can be reviewed by clicking the investigation name on the Cloud Assist Investigations page to open the Investigation details page.
If further assistance is needed, you can use open a Google Cloud support case. This process provides the support engineer with the complete context of the previously performed investigation, including the observations and hypotheses generated by Gemini. This context sharing significantly reduces the back-and-forth communication required with the support team, and leads to faster case resolution.
To create a support case from an investigation:
In the Investigation details page, click Request support.
Preview status and pricing
There is no charge for Gemini Cloud Assist investigations during public preview. Charges will apply to the feature when it becomes generally available (GA).
For more information about pricing after general availability, see Gemini Cloud Assist Pricing.