Overview
The OpenAI integration connects your OpenAI API usage data to G360. It is part of the LLM Metrics module. With this integration, you can:- Connect OpenAI using an admin key
- Monitor API usage, model consumption, and user activity
- Evaluate AI adoption and business impact across teams
- Schedule and monitor data synchronization
Prerequisites
Before you start, make sure you have:- Access to the Engineering Metrics Dashboard in G360
- An OpenAI admin API key
- Permission to configure integrations and projects
Your organization administrator generally manages the admin key, which enables centralized AI usage tracking.
Create an OpenAI connection
1
Open LLM Metrics Integrations
In the Engineering Metrics Dashboard, go to Integrations → LLM Metrics Integrations, then choose OpenAI.
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 OpenAI, choose the saved OpenAI admin key connection, and confirm. The data scope is added to the project automatically.
3
Configure sync behavior
The Sync Behavior section controls how often and for what duration data is collected.
4
Complete setup
Review all configuration settings and click Complete Setup.
5
Run the initial sync
Open the project and click Run Sync Now. This collects the latest OpenAI usage data, processes the metrics, and updates the dashboard.
Synchronization and metrics
After setup, G360 collects OpenAI usage data on the schedule you configured.A normal synchronization usually performs 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 API 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
- Synchronization still in progress
- 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, unique connection names that identify the environment.
- Periodically verify that the admin key is still valid.
- Keep consistent synchronization intervals to ensure accurate reporting.
- Review synchronization health and execution history to catch issues early.
- Review adoption, consumption, and ROI metrics periodically.

