-
Notifications
You must be signed in to change notification settings - Fork 87
Conversation
@@ -42,6 +42,44 @@ Object { | |||
} | |||
`; | |||
|
|||
exports[`Tests that require Docker setup one-app successfully started metrics has all metrics 1`] = ` |
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'd encourage looking at the diff of this file across the two commits to see the difference in metric names
📊 Bundle Size Report
|
"nodejs_eventloop_lag_min_seconds", | ||
"nodejs_eventloop_lag_p50_seconds", | ||
"nodejs_eventloop_lag_p90_seconds", | ||
"nodejs_eventloop_lag_p99_seconds" |
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.
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.
as there aren't any reviews yet and we might want to keep the two commits separate I've replaced 39b35b5 with 3b23458 to reduce the need for squashing later
(might be moot if the metric test isn't desired on it's own, but just in case)
3b23458
to
39b35b5
Compare
@@ -14,6 +14,7 @@ services: | |||
image: one-app:at-test | |||
expose: | |||
- "8443" | |||
- "3005" |
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 know it is the sample, but what expose 3005 now?
@@ -46,7 +46,8 @@ const setUpTestRunner = async ({ oneAppLocalPortToUse } = {}) => { | |||
'one-app': { | |||
ports: [ | |||
`${oneAppLocalPortToUse}:8443`, | |||
], | |||
oneAppMetricsLocalPortToUse ? `${oneAppMetricsLocalPortToUse}:3005` : undefined, |
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.
@JamesSingleton the 3005 port has to be exposed because it is mapped here like from ramdomPort to 3005
8006fdc
4671577
to
b4f779d
Compare
also removes the need for gc-stats, using the Node.JS API instead
ah, #111 was merged! I ran the tests before rebasing but not after 🤦♂️ |
b4f779d
to
c6d49a1
Compare
I thought I updated it but, might have messed up because I did it from my fork |
Description
prom-client
12.x added more metrics which cover those that we added viaprometheus-gc-stats
. Additionally,prom-client
is making use of the newperf_hooks
API in Node.JS removing the need forgc-stats
(binary dep). This, like #45 will help reduce potential install problems and binary incompatibilities (ex: switching base docker images).Motivation and Context
This keeps One App up-to-date and reduces installation complexity.
How Has This Been Tested?
Integration tests have been added showing the metric names exposed.
Types of Changes
Probably a breaking change as the metric names change (and reducing names but increasing labels for some of that information). I'm hoping this can be added before v5.0.0 is officially released.
Checklist:
What is the Impact to Developers Using One App?
This reduces one of the two native dependencies and so hopefully makes installation easier.