-
Notifications
You must be signed in to change notification settings - Fork 52
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
How to have correlation ids for messages from Cloud SDK in kibana? #4209
Comments
Hey @dinurp, this is a relevant feature request and we have discussed a similar issue in the past. |
Passing additional parameters to |
As of today this is not possible - we would need to implement some changes to make it possible. |
We are using Cloud SDK v3 via CAP nodejs v7 for making external calls. We have enabled logging with Kibana formatter by enabling the setting in CAP. We have bound application log service to the app when it is deployed to SAP BTP Cloud Foundry. The messages from CAP are logged in Kibana together with request logs from Cloud Foundry with correlation ID. Even the messages send from the CAP application have correlation ID headers and we are able to see messages for a request across the different apps and systems.
But messages from Cloud SDK are without correlation ID. They float around in Kibana and are not easily found. Cloud SDK logs warning messages like "WarningJWT: The provided JWT payload does not include a 'user_id' property." These messages are logged with no context and we are not able to understand the relevance of these messages without correlation with other messages.
How can we get Cloud SDK messages to be logged with correlation ID? They are already logged in Kibana format. But, without correlation with their context, these messages are pretty useless. We are not able to take heed of the warnings or locate reasons of errors.
Regards,
Dinu
The text was updated successfully, but these errors were encountered: