Skip to content

x/build/cmd/coordinator: add health check and graph to track hourly remaining GitHub API rate limit #44406

@dmitshur

Description

@dmitshur

While investigating #44404, I noticed in GopherBot's logs that it was failing to take some actions due to exceeding GitHub API rate limit quota:

$ kubectl logs -f gopherbot-deployment-6c6d86d5b9-s88c8 | grep "API rate limit"
[...]
2021/02/19 00:19:47 cl2issue: GET https://api.github.com/repos/golang/go/issues/44295/comments?per_page=1000&since=2021-02-19T00%3A14%3A00Z: 403 API rate limit of 5000 still exceeded until 2021-02-19 00:47:55 +0000 UTC, not making remote request. [rate reset in 28m08s]
[...]

When rate limit is exceeded, GopherBot stops being reliable for its users, and regular maintenance tasks do not occur.

This may be related to heavy activity, or perhaps it's caused by increased deterioration of issue #28320. This issue is to keep an eye on big of a problem it is and what we need to do here.

CC @golang/release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Buildersx/build issues (builders, bots, dashboards)FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions