Conversation
|
Fuzz test failed on 1b44450. To troubleshoot locally, use the GitHub CLI to download the seed corpus with |
1 similar comment
|
Fuzz test failed on 1b44450. To troubleshoot locally, use the GitHub CLI to download the seed corpus with |
|
Fuzz test failed on e90dd54. To troubleshoot locally, use the GitHub CLI to download the seed corpus with |
|
You have commit message errors, your commit messages To correct, run List of errors: Commit e90dd54, message |
stigok
force-pushed
the
216-expose-metrics
branch
from
e90dd54 to
67a2064
Compare
|
You have commit message errors, your commit messages To correct, run List of errors: Commit 67a2064, message |
stigok
force-pushed
the
216-expose-metrics
branch
2 times, most recently
from
a2db880 to
f43be1e
Compare
- Add arguments `-prometheus-metrics-enabled` and `-prometheus-listen-addr` to control whether to expose metrics from the registry app. - The `ModuleStore` interface has received an extra method `Metrics()` to support store-specific metrics.
Currently exposes rate limit status towards the GitHub API. These metrics are polled from the GitHub API on regular intervals. These requests are exempted from the general rate limits. The worker for polling this status is not started until the first call to `ReloadCache`. https://docs.github.com/en/rest/rate-limit/rate-limit?apiVersion=2022-11-28#get-rate-limit-status-for-the-authenticated-user
stigok
force-pushed
the
216-expose-metrics
branch
from
f43be1e to
8f723db
Compare
1 participant
Implements #216