index
Table of Contents
Section titled “Table of Contents”Overview
Section titled “Overview”This runbook is specifically about GitLab Duo Agentic Chat troubleshooting. For regular Duo Chat, please check out the Duo Chat Runbook instead.
Quick Links
Section titled “Quick Links”Note: these links are mostly for Duo Workflow as a whole, since Agentic Chat uses the Workflow infrastructure.
- Langsmith traces
- Sentry error tracking
- Grafana Service Overview
- Logs for gitlab.com
- Logs for staging.gitlab.com
Before starting the investigation
Section titled “Before starting the investigation”NOTE: Do NOT expose customer’s RED data in public issues. Redact them or make a confidential issue if you’re unsure.
Before starting the investigation, please collect the following information:
- User name who encountered the bug (e.g.
@johndoe) - What happened (e.g. User asked a question in Agentic Duo Chat and the chat did not respond)
- When it happened (e.g. Around 2024/09/16 01:00 UTC)
- GitLab Workflow VS Code extension version (e.g. v.6.26.1)
- How often it happens (e.g. It happens everytime)
- Steps to reproduce (e.g. 1. Ask a question “xxx” 2. Click …)
- AI Gateway or self-managed AI Gateway (If they use custom models, it’s likely latter.)
- A link to a Slack discussion, if any.
Rollback procedures
Section titled “Rollback procedures”If there is an error identified in the Duo Workflow Service, you will have to rollback the deployment using Runway. Declare an incident and ask an SRE for help if you do not have the ability to do this.
If there is an error identified in the LSP or VS Code extension, follow these steps to contact the Editor Extensions team.
Relevant Slack channel
Section titled “Relevant Slack channel”If you have a problem with Agentic Chat, the best place to ask for help is the #subteam-duo-chat-workflow-service Slack channel.