Overview
The Garth AI Code Review integration connects AI-powered code review metrics to G360, so you can monitor AI-assisted code review activity in the Engineering Metrics dashboard. It is available under the Quality Integrations module. Using this integration, organizations can monitor:- AI-assisted code review activity
- Usage trends
- Team adoption metrics
- Review insights and analytics
Prerequisites
Before configuring the integration, ensure you have:- Access to the Engineering Metrics dashboard in G360
- A valid Garth AI Code Review API key with the access needed to read metrics and usage data
- Permission to configure integrations
Create a Garth AI Code Review connection
1
Open Garth AI Code Review
In G360, open the Engineering Metrics dashboard. In the left sidebar, go to Integration → Quality Integrations → Garth AI Code Review.
2
Start a new connection
Click Add Connection. The Add Connection window opens.
3
Enter connection details
4
Test the connection
Click Test Connection and wait for validation to finish. If the API key is valid, the test succeeds. If the test fails, verify the API key and retry.
5
Save the connection
Click Save Connection. The connection appears in the configured connections list.
Metrics
After the connection is saved, G360 collects AI code review metrics and analytics automatically. Use them to review AI code review usage, adoption trends across teams, review analytics, and engineering productivity insights.Troubleshooting
Connection test failed
Connection test failed
Possible causes
- Invalid API Key
- Missing permissions
- Expired credentials
- Verify the API key.
- Ensure the API key has the necessary access permissions.
- Retest the connection.
Metrics not appearing
Metrics not appearing
Possible causes
- Data synchronization is still in progress
- Incorrect integration setup
- Incomplete connection configuration
- Wait for synchronization to complete.
- Verify the connection details.
- Retest the connection if required.
Best practices
- Use clear, descriptive connection names that identify the environment or purpose.
- Periodically validate the API key to avoid synchronization interruptions.
- Store API credentials securely, and rotate them according to your organization’s security policies.
- Review usage trends and adoption metrics regularly to understand AI code review use across teams.

