Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
smartcitydevops opened this issue Feb 23, 2022 · 1 comment

Comments

@smartcitydevops
Copy link
Collaborator

smartcitydevops commented Feb 23, 2022

Related to #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

@AlvaroVega AlvaroVega changed the title Service - Subservice ( and entityId and further parameters if possible ) in Cygnus "Finishing internal transaction" log Original Service, Subservice (entityId and further parameters) in "Finishing internal transaction" log instead of mapped Feb 23, 2022
@smartcitydevops
Copy link
Collaborator Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant