fix wrong rpcMetadata.route value when route.use(<middleware>) handle nested router

[biuboombiuboom]

What version of OpenTelemetry are you using?

opentelemetry: 1.4.0
node: 16.14.2

What version of Node are you using?

What did you do?

    const app = express();
    const router = express.Router();
    app.use('/users', router);
    router.get('/:userId', (req, res) => {
      res.status(200).end('user-'+req.params.userId);
    });
    router.use(customMiddleware);
    const bookRouter = express.Router({ mergeParams: true });
    router.use('/:userId/books', bookRouter);
    bookRouter.get('/:bookId', (req, res) => {
      setImmediate(() => {
        res.status(200).end('book-' + req.params.bookId);
      });
    });       

request http://localhost:8080/proxy/v1/bar/1

What did you expect to see?

rpcMetadata.route='/users/:userId/books/:bookId'

What did you see instead?

rpcMetadata.route='/:userId/books/:bookId'

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[mikesimons]

Looks like OP decided to drop the PR but this is definitely still an issue.

@blumamir @chigia001 Is the approach taken in #1615 the right direction?
Would consider picking this up with some direction on how you think it could be solved.