Investigate extremely slow requests captures on Edge environment about opbeans-node HOT 1 OPEN

Thanks. I poked a little bit -- mostly me learning some about opbeans-node and opbeans-loadgen -- and I don't see any obvious normal reason why the "GET /api/customers" endpoint code could have a long delay at the end:

• There is the separate handler to redirect "/api" requests 50% of the time that I'm not at all familiar with:

  opbeans-node/server.js

  Lines 86 to 109 in a052ed7

  	app.use('/api', function (req, res, next) {
  	if (Math.random() > opbeansRedirectProbability) {
  	return next()
  	}
  	const service = opbeansServiceUrls[Math.floor(Math.random() * opbeansServiceUrls.length)]
  	const opts = {
  	method: req.method,
  	hostname: service.hostname,
  	port: service.port,
  	path: req.originalUrl
  	}
  	req.log.debug('proxying request: %s => %s:%s', req.originalUrl, opts.hostname, opts.port + opts.path)
  	const clientReq = http.request(opts)
  	clientReq.on('response', clientRes => {
  	res.writeHead(clientRes.statusCode, clientRes.headers)
  	clientRes.pipe(res)
  	})
  	req.pipe(clientReq)
  	})

• and the app.get('*', ... routing pattern that I'm not familiar with:

  opbeans-node/server.js

  Line 113 in a052ed7

  app.get('*', function (req, res, next) {

• I noticed that some of the other opbeans-$lang services also have some slow outliers as well.
• The slow transactions on edge today are all "GET /api/customers".

tl;dr: I don't have much useful info. @alex-fedotyev If something changes to either make this a higher prio or if you notice a behaviour change, please mention it here.

from opbeans-node.