-
Notifications
You must be signed in to change notification settings - Fork 365
Comparing changes
Open a pull request
base repository: siimon/prom-client
base: e29a1721f442973eb733cafedb2ed6de82b0c7e5
head repository: siimon/prom-client
compare: f817dd387faa0f3881d982dbe62c0783672b62d9
- 15 commits
- 22 files changed
- 9 contributors
Commits on Feb 1, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 96f7495 - Browse repository at this point
Copy the full SHA 96f7495View commit details
Commits on May 6, 2021
-
Configuration menu - View commit details
-
Copy full SHA for c7b9a9d - Browse repository at this point
Copy the full SHA c7b9a9dView commit details
Commits on Jul 31, 2021
-
Configuration menu - View commit details
-
Copy full SHA for bfeabc2 - Browse repository at this point
Copy the full SHA bfeabc2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 216e2b3 - Browse repository at this point
Copy the full SHA 216e2b3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4c8bbc7 - Browse repository at this point
Copy the full SHA 4c8bbc7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9d5b7f8 - Browse repository at this point
Copy the full SHA 9d5b7f8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 436a674 - Browse repository at this point
Copy the full SHA 436a674View commit details -
Use entry.details.kind if exists fallback entry.kind
Node 16 moved the PerformancyEntry. See https://nodejs.org/docs/latest-v16.x/api/deprecations.html#deprecations_dep0152_extension_performanceentry_properties Remove `buffered` observe option This option has been removed in Node 16: https://nodejs.org/docs/latest-v16.x/api/perf_hooks.html#perf_hooks_performanceobserver_observe_options This was redundant in Node <16 because `false` was already the default: https://nodejs.org/docs/latest-v15.x/api/perf_hooks.html#perf_hooks_performanceobserver_observe_options > buffered <boolean> … Default: false. Remove buffering comment
Configuration menu - View commit details
-
Copy full SHA for c31ccec - Browse repository at this point
Copy the full SHA c31ccecView commit details -
Set aggregation method for newer event loop metrics
These are not entirely accurate: they're the "mean of the mean" and "mean of percentiles," but that's as good as we can get. Fixes #418
Configuration menu - View commit details
-
Copy full SHA for a972f0c - Browse repository at this point
Copy the full SHA a972f0cView commit details
Commits on Aug 1, 2021
-
In gauge.inc/dec, default to 1 only if no arg is passed
Calling `.inc(value)` with a dynamic value that may be 0 or 1 will always cause to increase metrics by 1. This is very problematic and may distort the metrics in a non obvious way
Configuration menu - View commit details
-
Copy full SHA for 83cb173 - Browse repository at this point
Copy the full SHA 83cb173View commit details
Commits on Aug 2, 2021
-
docs: fix config reference for
collectDefaultMetrics
The docs for `collectDefaultMetrics` mention that the config object accepts a `registry`, but the property is actually `register`.
Configuration menu - View commit details
-
Copy full SHA for 2335e00 - Browse repository at this point
Copy the full SHA 2335e00View commit details
Commits on Aug 4, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 66f50b6 - Browse repository at this point
Copy the full SHA 66f50b6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 65cef4c - Browse repository at this point
Copy the full SHA 65cef4cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5fb2355 - Browse repository at this point
Copy the full SHA 5fb2355View commit details
Commits on Aug 9, 2021
-
Configuration menu - View commit details
-
Copy full SHA for f817dd3 - Browse repository at this point
Copy the full SHA f817dd3View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff e29a1721f442973eb733cafedb2ed6de82b0c7e5...f817dd387faa0f3881d982dbe62c0783672b62d9