Skip to main content
Telara

Integrations / GitLab Duo

GitLab Duo logo

GitLab Duo

GitLab Duo AI metrics — per-user usage across Code Suggestions, Duo Chat, Code Review, Agent Platform, Job Troubleshooting, and MCP tool calls, plus the AI Catalog agents/flows configured for a group. Pairs with `gitlab` connector for code/MR operations.

Personal access token
Spend
Actions

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

A GitLab.com group or self-managed instance with Duo.
Owner or a token that can read Duo usage. This is not the GitLab source connector.

Vendor setup

Get the credential

1
Prefer Connect on GitLab.com
Settings → Integrations → GitLab Duo. Approve access. Grant the permissions this page lists from the catalog.
2
Token path
On self-managed, create a personal or group access token and paste it. Do not copy a permission list from an old wiki.

Permissions Telara requests

  • read_api
    OAuth 2.0
  • read_user
    OAuth 2.0

In Telara

Connect in Telara

Personal access token

GitLab Personal Access Token (or Group Access Token) with scopes: - `read_api` — sufficient for AiUserMetrics / AiMetrics / AiUsageData reads - `api` — required only if you also want to drive seat assignment via the userAddOnAssignmentBulkCreate mutation from the same credential Token must belong to a user with the Owner role on the target group (group-level GraphQL aiUserMetrics is owner-gated). Per GitLab docs: AiUserMetrics and AiMetrics require ClickHouse to be configured on the target instance — see retention notes above.

In Telara, open Settings → Integrations, choose this connector, and paste the token into the field Telara shows.

Fields Telara asks for
  • Private token
OAuth 2.0

OAuth flow for hosted gitlab.com. `read_api` is enough for spend metrics reads; add `api` if seat assignment is also delegated.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by directory ID.

Vendor history: 90 days of vendor-side history.

  • duo_total_events
    events
  • code_suggestions_events
    events
  • duo_chat_events
    events
  • code_review_events
    events
  • agent_platform_events
    events
  • troubleshoot_job_events
    events
  • mcp_tool_call_events
    events
  • code_suggestions_shown
    count
  • code_suggestions_accepted
    count
  • code_suggestions_shown_lines
    lines
  • code_suggestions_accepted_lines
    lines
  • duo_code_contributors
    users
  • duo_chat_contributors
    users
  • duo_used_users
    users

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

A token that can clone code is not enough for Duo usage reports.
Self-managed instances must be reachable from Telara.