Overview
The Anthropic integration connects your Anthropic API usage data to G360. It is part of the LLM Metrics module. With this integration, you can:- Connect Anthropic using an admin key
- Analyze LLM usage, user activity, and model consumption
- Estimate AI business impact and ROI
- Schedule and monitor data synchronization
Prerequisites
Before you start, make sure you have:- Access to the Engineering Metrics Dashboard in G360
- An Anthropic admin API key
- Permission to configure integrations and projects
Your organization or company administrator typically provides the admin key to enable AI access and usage tracking.
Create an Anthropic connection
1
Open LLM Metrics Integrations
In the Engineering Metrics Dashboard, go to Integrations → LLM Metrics Integrations, then choose Anthropic.
2
Start a new connection
Click New Connection.
3
Enter connection details
4
Test the connection
Click Test Connection and wait for validation. If it fails, verify the admin key and its permissions, then retry.
5
Save the connection
Click Save Connection. The connection appears in the available connections list.
Create an LLM Metrics project
1
Add a project
Go to Projects, click Add Project, select LLM Metrics as the project type, and enter the required project details.
2
Select the data source
In the Data Source section, select Anthropic, choose the saved Anthropic admin key connection, and confirm. The data scope is added to the project automatically.
3
Configure sync behavior
The Sync Behavior section controls how and when data is collected.
4
Complete setup
Review the configuration and click Complete Setup.
5
Run the initial sync
Open the project and click Run Sync Now. This collects the latest Anthropic usage data, processes the metrics, and updates the dashboard.
Synchronization and metrics
After setup, G360 collects Anthropic usage data on the schedule you configured.A normal synchronization usually triggers the required transformation automatically.
Available insights
Some Executive Summary features may still be under active development, depending on the deployment version.
Troubleshooting
Connection test failed
Connection test failed
Possible causes
- Invalid admin key
- Missing permissions
- Expired credentials
- Verify the admin key.
- Confirm permissions with the administrator.
- Retry the connection test.
No data appearing after sync
No data appearing after sync
Possible causes
- Initial synchronization still running
- Incorrect project configuration
- Schedule disabled
- Check the Status section.
- Run the synchronization manually.
- Verify the sync schedule settings.
Schedule not running
Schedule not running
Possible causes
- Schedule set to Inactive
- Schedule currently Paused
- Set the schedule status to Active.
- Verify the configured sync frequency and execution time.
Best practices
- Use clear and unique connection names.
- Periodically verify that the admin key is still valid.
- Configure regular synchronization schedules.
- Monitor synchronization status regularly.
- Review ROI and usage metrics periodically for adoption insights.

