This repository has been archived by the owner on Jan 15, 2025. It is now read-only.
Update dependency prom-client to v14 - abandoned #15
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.
This PR contains the following updates:
^10.1.0
->^14.0.0
Release Notes
siimon/prom-client
v14.1.0
Compare Source
Changed
types: converted all the generic Metric types to be optional
The
done()
functions returned bygauge.startTimer()
andsummary.startTimer()
now return the timed duration. Histograms already hadthis behavior.
types: fixed type for
registry.getMetricsAsArray()
Improve performance of
gague.inc()
andgauge.dec()
by callinghashObject()
once.Added
The
processResources
metric was added, which keeps a track of all sorts ofactive resources. It consists of the following gauges:
nodejs_active_resources
- Number of active resources that are currentlykeeping the event loop alive, grouped by async resource type.
nodejs_active_resources_total
- Total number of active resources.It is supposed to provide the combined result of the
processHandles
andprocessRequests
metrics along with information about any other types ofasync resources that these metrics do not keep a track of (like timers).
Support gzipped pushgateway requests
v14.0.1
Compare Source
Changed
v14.0.0
Compare Source
Breaking
changed:
linearBuckets
does not propagate rounding errors anymore.Fewer bucket bounds will be affected by rounding errors. Histogram bucket
labels may change.
6f1f3b2
changed: The push gateway methods
pushAdd()
,push()
anddelete()
nowreturn Promises instead of accepting a callback:
f177b1f
changed: The default
nodejs_eventloop_lag_*
metrics are now reset every timethey are observed. This prevents these metrics from "stabilizing" over a long
period of time and becoming insensitive to small changes. For more info, see
#370.
0f444cd
Changed
await
/then
s to examples.074f339
client.contentType
.3b66641
c9bf1d8
v13.2.0
Compare Source
Changed
process
if cluster module is not used.Added
zero()
toHistogram
for setting the metrics for a given label combination to zeroGauge.inc/dec(0)
without defaulting to 1v13.1.0
Compare Source
Changed
Added
labels()
andremove()
v13.0.0
Compare Source
Breaking
changed: The following functions are now async (return a promise):
registry.metrics()
registry.getMetricsAsJSON()
registry.getMetricsAsArray()
registry.getSingleMetricAsString()
If your metrics server has a line like
res.send(register.metrics())
, youshould change it to
res.send(await register.metrics())
.Additionally, all metric types now accept an optional
collect
function,which is called when the metric's value should be collected and within which
you should set the metric's value. You should provide a
collect
function forpoint-in-time metrics (e.g. current memory usage, as opposed to HTTP request
durations that are continuously logged in a histogram).
changed:
register.clusterMetrics()
no longer accepts a callback; it onlyreturns a promise.
removed: v12.0.0 added the undocumented functions
registry.registerCollector
and
registry.collectors()
. These have been removed. If you were using them,you should instead provide a
collect
function as described above.Changed
registry.resetMetrics()
(#238)registry.resetMetrics()
registry.resetMetrics()
registry.getMetricAsPrometheusString
utils.getPropertiesFromObj
withObject.values
catch
bindingsnumber
in typescript instead ofvoid
Added
registry.registerCollector()
andregistry.collectors()
methods in TypeScript declarationexample/pushgateway.js
v12.0.0
Compare Source
Breaking
constructors, only the config object forms remain.
interval. The
timeout
option tocollectDefaultMetrics(conf)
is no longersupported or needed, and the function no longer returns a
Timeout
object.Changed
process_max_fds
is process limit, not OS (#314)Metric
labelNames & labelValues in TypeScript declaration to a generic typeT extends string
, instead ofstring
registry.getMetricsAsJSON()
registry.getMetrics*
startTimer
, when invoked returns the number of secondsprocess_start_time_seconds
Added
v11.5.3
Compare Source
Changed
compressCount
in Summaries to control compression of data in t-digest.v11.5.2
Compare Source
Changed
v11.5.1
Compare Source
Changed
v11.5.0
Compare Source
Added
timestamps
toggle tocollectDefaultMetrics
optionsvalidateMetricName
v11.4.0
Compare Source
Added
nodejs_active_handles
metric to thecollectDefaultMetrics()
. Unlikenodejs_active_handles_total
it split count of active handles by type.nodejs_active_requests
metric to thecollectDefaultMetrics()
. Unlikenodejs_active_requests_total
it split count of active requests by type.v11.3.0
Compare Source
Changed
metrics. (#244)
Added
remove()
method on each metric type, based on Prometheus "Writing Client Libraries" section on labelsv11.2.1
Compare Source
Breaking
Changed
Added
v11.2.0
Compare Source
Changed
merge
patch version to remove vulnerability.Added
benchmark
suite which can be run withnpm run benchmarks
.v11.1.3
Compare Source
Changed
Object.assign
on hot paths, as well asmutating objects when appropriate.
v11.1.2
Compare Source
Changed
histogram
scrape performance by usingacc.push
instead ofacc.concat
. Fixes #216 with #219v11.1.1
Compare Source
Changed
processOpenFileDescriptors
metric when no custom config was setv11.1.0
Compare Source
Changed
startTimer
utility to not mutate objects passed asstartLabels
Counter
to validate labels parameter ofinc()
against initiallabelset
AggregatorFactory
losing the aggregator method of metricsv11.0.0
Compare Source
Breaking
gauge.setToCurrentTime()
to use seconds instead of millisecondsbest practices
v10.2.3
Compare Source
Breaking
Changed
registry.getMetricsAsJSON()
ignores registry default labelsAdded
v10.2.2
Compare Source
Changed
process_virtual_memory_bytes
reported under linuxv10.2.1
Compare Source
Changed
clusterMetrics
promise if no callback is providedv10.2.0
Compare Source
Changed
Added
reset
to Counter and GaugeresetMetrics
to register to callingreset
of all metric instancesv10.1.1
Compare Source
Changed
arguments
in cluster codeConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.