can anyone help me out with this for loopback?
1) Can I monitor how many requests/second are currently being fielded on average and what's the peak load? 2) Can I monitor and determine which are the longest running requests? 3) Once I start ... can I monitor and determine, if my loopback server ever crashed or hung for a while ... as the incoming requests either queued-up or got rejected due to timeout, at its gates? 4) Can I monitor and determine: On average how long does a request/response take? 200ms, 5 seconds? 5) I'm using only a single process right now but if I were to switch to using 2 cores ... can I dedicate one of the loopback processes to handle the longer running requests only or maybe round robin between the them? Idea is to keep serving the short-lived API requests no matter what and leaving the longer ones with fewer cores/processes to handle them.
loopback-consoleto include a few fixes (promise resolution fixed, in particular!) and to substantially improve the documentation. Would you guys mind giving it a look over and letting me know how it looks now? https://github.com/GovRight/loopback-console