You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add the percentage CPU time used by the event loop in the last
LOOP_INTERVAL so we can see if a Node.js process is CPU bound.
* Add thread cpu times for Mac.
Update README.md
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,12 +247,14 @@ Emitted when a garbage collection (GC) cycle occurs in the underlying V8 runtime
247
247
Emitted when all possible environment variables have been collected. Use `appmetrics.monitor.getEnvironment()` to access the available environment variables.
248
248
249
249
### Event: 'loop'
250
-
Emitted every 60 seconds, summarising event tick information in time interval
250
+
Emitted every 5 seconds, summarising event tick information in time interval
251
251
*`data` (Object) the data from the event loop sample:
252
252
*`count` (Number) the number of event loop ticks in the last interval.
253
253
*`minimum` (Number) the shortest (i.e. fastest) tick in milliseconds.
254
254
*`maximum` (Number) the longest (slowest) tick in milliseconds.
255
255
*`average` (Number) the average tick time in milliseconds.
256
+
*`cpu_user` (Number) the percentage of 1 CPU used by the event loop thread in user code the last interval. This is a value between 0.0 and 1.0.
257
+
*`cpu_system` (Number) the percentage of 1 CPU used by the event loop thread in system code in the last interval. This is a value between 0.0 and 1.0.
0 commit comments