Draft
Conversation
Reads summary CSVs and pushes custom metrics to Datadog via the v2
series API. Supports --dry-run to preview without sending.
Metrics pushed:
- github.issues.created/closed (monthly)
- github.prs.created/closed (monthly)
- github.issues.by_type / github.prs.by_type (Bug, Feature, etc.)
- github.issues.by_label / github.prs.by_label (per-label monthly)
- github.issues.total_open/total_closed (current snapshot)
- github.prs.total_open/total_closed (current snapshot)
- github.discussions.created/closed/answered (monthly)
All metrics tagged with repo:{owner}/{name}. Label metrics tagged
with label:{name}, type metrics with issue_type:{name}.
DD_API_KEY can be passed via --dd-api-key or DD_API_KEY env var.
DD_SITE for non-US1 regions via --dd-site or DD_SITE env var.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Instead of pre-aggregated monthly summaries, each issue/PR/discussion
becomes a data point at its created_at timestamp, tagged with ALL its
labels. This enables cross-label queries in Datadog like:
github.issues{domain:vrl,type:bug}
Label tags use the label prefix as key: "domain: vrl" -> domain:vrl,
"source: kafka" -> source:kafka. Unprefixed labels use label: key.
Defaults to --since 2026-01-01 to keep initial volume small.
312 series / 1,158 points for Vector 2026 data.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Makes --dd-api-key optional — reads from DD_API_KEY in the .env file loaded by --env-file, or from the environment. Same for DD_SITE. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
We want GitHub project health data in Datadog dashboards — with the ability to slice by any combination of labels, issue types, and state.
What's new
push-metricsreads the SQLite database and pushes per-item metrics to Datadog. Each issue, PR, and discussion becomes a data point at itscreated_attimestamp, tagged with all its labels. This enables queries like:Usage
Metrics
github.issuesrepo,state,issue_type, all labelsgithub.issues.closedgithub.prsrepo,state, all labelsgithub.prs.closedgithub.discussionsrepo,state,category,answeredTag format
Labels with a prefix become structured tags:
domain: vrl→domain:vrlsource: kafka→source:kafkatype: bug→type:bugsink: s3→sink:s3GitHub issue types:
issue_type:bug,issue_type:feature,issue_type:taskUnprefixed labels:
label:Epic,label:good first issueVolume (Vector repo)
Test plan
cargo buildcompiles cleanly--dry-runshows correct series, tags, and point counts🤖 Generated with Claude Code