GitHub
Copilot Logs
Retrieves GitHub Copilot activity logs from GitHub Enterprise audit logs. Automatically filters to Copilot-related events (action:copilot.*).
Sync Type: Incremental
Requirements
Before configuring this input, you need to:
-
Create a Personal Access Token (PAT) — GitHub docs.
- Go to your GitHub settings
- Navigate to Developer settings > Personal access tokens > Tokens (classic)
- Click "Generate new token (classic)"
- Select the
read:audit_logscope - Copy and securely store the generated token
-
Required Permissions:
- You must be an enterprise admin to access enterprise audit logs
- The PAT must have the
read:audit_logscope
Configuration
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
| enterprise | string | Yes | - | Your GitHub enterprise slug or ID |
| bot_actions_only | boolean | No | false | When enabled, only returns events initiated by the Copilot bot (actor |
| backfill_start_time | string | No | - | Date to start fetching data from (ISO 8601). If not specified, no past records are fetched. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
| personal_access_token | string | Yes | GitHub Personal Access Token with read |
Troubleshooting
Common issues and solutions:
1. Rate Limit Errors
- The input automatically handles rate limiting by waiting for the reset period
- You'll see logs indicating the wait time when rate limits are hit
2. Authentication Errors
- Verify your PAT has the
read:audit_logscope - Ensure the PAT hasn't expired
- Confirm you have enterprise admin access
3. No Data
- Check if your enterprise slug/ID is correct
- Verify that Copilot events exist in the time range you're querying
- Ensure you have Copilot enabled in your enterprise
Related Articles
Sample Record
Code
Last modified on