Hello!
I noticed that the github_workflow_job_duration_ms metrics sometimes have massively large value e.g. -63911756733000.
This causes aggregation operators (sum, etc.) to have wonky results.
For now I am removing the faulty metrics with explicit greater than 0 filter.
The -63911756733000 value seems to be the result when subtracting time.Now() against null time; it results in a value in the range of negative 63 trillion:
// https://go.dev/play/p/Aisjl4galN9
x := time.Time{}.UnixMilli() - time.Now().UnixMilli()
fmt.Println(x)
// -63393490800000
Not sure where the null is coming from; querying github about the affected jobs, they seem to have normal results:
gh api repos/xxx/yyy/actions/jobs/11111111111 --jq '{created_at, started_at}'
{
"created_at": "2026-04-13T23:44:11Z",
"started_at": "2026-04-13T23:44:14Z",
}
Hello!
I noticed that the
github_workflow_job_duration_msmetrics sometimes have massively large value e.g.-63911756733000.This causes aggregation operators (
sum, etc.) to have wonky results.For now I am removing the faulty metrics with explicit greater than 0 filter.
The
-63911756733000value seems to be the result when subtractingtime.Now()againstnulltime; it results in a value in the range of negative 63 trillion:Not sure where the
nullis coming from; querying github about the affected jobs, they seem to have normal results: