-
Notifications
You must be signed in to change notification settings - Fork 428
Record cluster worker scrape failures #850
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
nightjard
wants to merge
2
commits into
prometheus:main
Choose a base branch
from
nightjard:fix/cluster-worker-failure-histogram-290
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -23,6 +23,7 @@ | |
| */ | ||
|
|
||
| const { debuglog } = require('node:util'); | ||
| const Histogram = require('./histogram'); | ||
| const Registry = require('./registry'); | ||
| const { waitFor } = require('./util'); | ||
|
|
||
|
|
@@ -41,6 +42,13 @@ const GET_METRICS_REQ = '@prometheus-io/client:getMetricsReq'; | |
| const GET_METRICS_RES = '@prometheus-io/client:getMetricsRes'; | ||
| const GOODBYE = '@prometheus-io/client:goodbye'; | ||
|
|
||
| const clusterWorkerScrapeFailures = new Histogram({ | ||
| name: 'prom_client_cluster_worker_scrape_failures', | ||
| help: 'Number of workers that failed to return metrics during a failed cluster scrape.', | ||
| buckets: [1, 2, 4, 8, 16, 32], | ||
| registers: [], | ||
| }); | ||
|
|
||
| let registries = [Registry.globalRegistry]; | ||
| let listenersAdded = false; | ||
| let requestCtr = 0; // Concurrency control | ||
|
|
@@ -90,6 +98,7 @@ class AggregatorRegistry extends Registry { | |
| const responsePromises = [this.#selfMetrics(), ...workerMetrics]; | ||
| const request = { | ||
| responseHandlers, | ||
| workerFailures: 0, | ||
| promise: waitFor( | ||
| this.#gather(requestId, metricSnapshot, responsePromises), | ||
| 5_000, | ||
|
|
@@ -105,6 +114,16 @@ class AggregatorRegistry extends Registry { | |
|
|
||
| return await request.promise; | ||
| } catch (err) { | ||
| let failedWorkers = request.workerFailures; | ||
|
|
||
| if (err.message === 'Timeout') { | ||
| failedWorkers += request.responseHandlers.size; | ||
| } | ||
|
|
||
| if (failedWorkers > 0) { | ||
| clusterWorkerScrapeFailures.observe(failedWorkers); | ||
| } | ||
|
|
||
| if (err.message === 'Timeout') { | ||
| throw new Error( | ||
| `Operation timed out. ${request.responseHandlers.size} outstanding responses.`, | ||
|
|
@@ -118,8 +137,13 @@ class AggregatorRegistry extends Registry { | |
| } | ||
|
|
||
| async #selfMetrics() { | ||
| const metrics = await Promise.all( | ||
| registries.map(r => r.getMetricsAsJSON()), | ||
| ); | ||
| metrics.push([await clusterWorkerScrapeFailures.get()]); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are you sure you're not double-reporting this? That should be in the default registry. |
||
|
|
||
| return { | ||
| metrics: await Promise.all(registries.map(r => r.getMetricsAsJSON())), | ||
| metrics, | ||
| }; | ||
| } | ||
|
|
||
|
|
@@ -348,6 +372,7 @@ async function primaryListener(worker, event) { | |
| request.responseHandlers.delete(worker.id); | ||
|
|
||
| if (event.error) { | ||
| request.workerFailures++; | ||
| response.reject(new Error(event.error)); | ||
| } else { | ||
| response.resolve({ | ||
|
|
||
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think observing 0's when there are no workers is probably unlikely to happen but is also extra information about the class of failure we may be dealing with. As written this will never catch unclassified errors such as an NPE in the try block.
For instance, regressions in the Node API are not unknown. I work on a project that doesn't work on node 24.7-24.16, for instance, due to breaking changes in
child_process.fork()