search

telefonicaid / fiware-cygnus

A connector in charge of persisting context data sources into other third-party databases and storage systems, creating a historical view of the context
https://fiware-cygnus.rtfd.io/
GNU Affero General Public License v3.0
64 stars 104 forks source link

Original Service, Subservice (entityId and further parameters) in "Finishing internal transaction" log instead of mapped #2138

Open smartcitydevops opened 2 years ago

smartcitydevops commented 2 years ago

Related to https://github.com/telefonicaid/fiware-cygnus/issues/2108

We would consider ver useful that the string that follows to "Destination:" in Cygnus log for "Finishing internal transaction" would show:

service subservice entity_id entity_type or service subservice entity_type or service subservice entity_id attribute

(at least, service subservice)

It seems that, currently, the string after "Destination:" is based upon namemappings information. We think that service-subservice-... would be more useful for operations based on these logs.

Thanks in advance

smartcitydevops commented 2 years ago

Please consider both successful and unsuccessful scenarios for this issue, that is, please write

Destination: Service Subservice [Further parameter 1] [Further parameter 2]...

in the "Finishing internal transaction" final successful log, as well as in the last ERROR or WARN Cygnus log

I hope it helps