We call a login: http://localhost:3000/api/auth/login and we see in the logs that there were 2 flowIds that were generated (one for gateway, one for auth module):
[JobLike] [pid: 61991] - 2020-10-06T16:19:28.391 - [MetadataMiddleware] Received request with the following metada: {"flowId":"1b7a093650344c06993908b8a2848442","time":1601990368391}
[JobLike] [pid: 61991] - 2020-10-06T16:19:28.419 - [MetadataMiddleware] Received request with the following metada: {"flowId":"9f117ccaf36f4fc69a064f2abbff0df3","time":1601990368419}
Seems like every http call we generate a new flowId. This is nice when we will introduce parentId.
Possible fix:
We will have to create a new and modified HttpService where the metadata will be added automatically to a custom header.
This is a temporary solution, because in the distant future we will probably use other communication protocols between our modules / services.
Scenario:
We call a login:
http://localhost:3000/api/auth/loginand we see in the logs that there were 2 flowIds that were generated (one for gateway, one for auth module):Seems like every http call we generate a new flowId. This is nice when we will introduce
parentId.Possible fix:
We will have to create a new and modified
HttpServicewhere the metadata will be added automatically to a custom header.This is a temporary solution, because in the distant future we will probably use other communication protocols between our modules / services.