VOOZH about

URL: https://docs.datadoghq.com/account_management/billing/ci_visibility/

⇱ CI Visibility Billing


For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/account_management/billing/ci_visibility.md. A documentation index is available at /llms.txt.

CI Visibility Billing

This product is not supported for your selected Datadog site. ().

Overview

This guide provides a non-exhaustive list of billing considerations for CI Visibility.

Counting committers

A committer is an active Git contributor, identified by their Git author email address. For billing purposes, a committer is included if they make at least three commits in a given month.

Billing for commits made by bots or actions performed in the GitHub UI

Commits made by verified bots or through actions performed directly in the GitHub UI are not billed by Datadog. These are automatically excluded from billing calculations. Only verified bots are excluded from billing.

Excluding commits from specific people

Yes, you can exclude commits from specific people by using exclusion filters.

Deduplicating committers across email addresses

In some cases, a single developer’s commits can be split across multiple Git author emails. For example, a developer might set a different email with git config user.email in different repositories. If more than one of those emails passes the three-commit billing threshold described above, each counts as a separate committer.

For repositories hosted on GitHub, Datadog can map each Git author email to the underlying GitHub user so that the developer is counted once, even when they push under different emails. This requires a Datadog GitHub App installed on the affected repositories with the Contents: Read permission.

This mapping is available for GitHub repositories only. Repositories hosted on GitLab, Azure DevOps, or Bitbucket are not deduplicated.

If your committer count looks higher than expected for GitHub repositories, check that the Datadog GitHub App is installed on those repositories with the Contents: Read permission. You can review your installation from the GitHub integration tile.

Further Reading