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.
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.
Billing enrichment
Billing enrichment correlates your billable-committer metrics with data from a reference table, using the committer’s email address as the join key. This adds tags such as vp_name or director_name to your billing data, so you can break down billing data by organizational structure.
To set up billing enrichment:
- Create a reference table that contains a column with committer email addresses, along with any additional columns you want to expose as tags (such as
vp_name). - In Datadog, go to CI/CD Optimization > Billing & Committers.
- Turn on Enrich billing metrics.
- Select the Reference table to use.
- Select the Email key column: the column in the reference table that contains the committer email address. Datadog uses this column to join billing data with the reference table.
- Select the Enrichment columns: the columns from the reference table to expose as tags on billing metrics. Leave empty to include all columns.
After billing enrichment is configured, the additional tags from the reference table appear alongside your existing billable-committer metrics.
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
