Skip to content

Conversation

mhaas
Copy link
Contributor

@mhaas mhaas commented Jan 11, 2022

When logging exceptions with logging.exception(), the cf-python-logging library will emit the stacktrace as a separate field in the JSON. This field is now being filtered by the BTP and no longer visible in Kibana.

This commit adds the stacktrace to the main 'msg' field and thus makes it possible again to debug exceptions in our Python applications.

When logging exceptions with logging.exception(), the cf-python-logging
library will emit the stacktrace as a separate field in the JSON. This field
is now being filtered by the BTP and no longer visible in Kibana.

This commit adds the stacktrace to the main 'msg' field and thus makes it
possible again to debug exceptions in our Python applications.
@mhaas
Copy link
Contributor Author

mhaas commented Jan 13, 2022

Hi @gvachkov, @alexpenev-s,

please let me know your thoughts on this change. It would be good to have the issue addressed soon.

Thanks

Michael

@jahan01
Copy link

jahan01 commented Feb 19, 2022

@alexpenev-s @gvachkov any one of can review this and merge ? We would also need this.

@cla-assistant
Copy link

cla-assistant bot commented Mar 23, 2022

CLA assistant check
All committers have signed the CLA.

@kmaslenkovsap kmaslenkovsap merged commit bc5213b into SAP:master Mar 23, 2022
@mhaas mhaas deleted the fix_stacktrace_not_shown_in_kibana branch July 26, 2023 16:22
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

Successfully merging this pull request may close these issues.

3 participants