MVC - Move Root Cause Analysis to Duo Chat

Overview

We originally build the Root Cause Analysis feature in its own implementation outside of Duo Chat.

Proposal

Move Root Cause Analysis to use Duo Chat

1. The user clicks on the Root Cause Analysis button from the Job logs page
2. RCA results are displayed in the Duo Chat window

Feature Gating:

RCA should be available for only Gitlab Ultimate customers with Gitlab Duo Enterprise (this got moved to the other issue, because some of the abstractions were not ready yet)

Notes

RCA Model - We will covert this to use the ai gateway via the slash command abstractions which hit anthropic models. We will choose a model with a higher token limit like claude since build logs can be large.

Outstanding discussion items

Displaying the legal disclaimer in the flow is being discussed here &13080 (comment 1860392523)

Contacts

• Tech Lead (for RCA): @allison.browne
• PM (for grouppipeline execution): @rutshah
• EM (for grouppipeline execution): @carolinesimpson

Technical Proposal

• Truncation strategy should remain the same for now
  • We can adjust the prompt/truncation based on our findings from the prompt library exercise.
• We will add a new slash command in accordance with with other tools: ee/lib/gitlab/llm/chain/tools
  • This should inherit from: Gitlab::Llm::Chain::Tools::SlashCommandTool
  • We will need to add the ability to use a resouceId with slash commands, since the current implementations all pass over the selected text and do not use the resourceId to fetch the content. The resourceId is a globalId
• Be sure to test the prompts per model.