Description

gtal-box

opened on Mar 13, 2024

Issue body actions

Currently when there is an api error the logger logs and error, but the stack trace is included only in a following debug log.
This is true to all api clients, including segments, splits, events, impressions, telemetry
for example:

python-client/splitio/api/segments.py

Line 69 in 8326138

_LOGGER.error(

What is the reason for this?
And is it possible to turn this into one error message with the stack trace included?

Activity

1. kleinjoshuaa commented on Mar 28, 2024

   

   kleinjoshuaa

   on Mar 28, 2024

   More actions

   Hi @gtal-box - the reason for this is that Error and Debug are two different log levels. At the error level you will just get the error. The debug log level you will get both the error and the stack trace.
2. gtal-box commented on Apr 2, 2024

   

   gtal-box

   on Apr 2, 2024

   Author

   More actions

   Hi @kleinjoshuaa,

   From my humble experience it is a common practice to have the stack trace as part of the error log message.

   1. I see you are already doing it in other client libraries like dotnet and java.
   2. It is easier to investigate prod problems without turning debug logs on.

   Can you please consider adding the stack trace to the error message?
3. chillaq commented on Nov 12, 2025

   

   chillaq

   on Nov 12, 2025

   Contributor

   More actions

   Hi @gtal-box, thanks for raising this question, we actually had the stack trace also logged as error and we got complaints that it is cluttering the log output, especially when there is an exception that is reported frequently, given that error logging is the standard logging on production.

   This is why we moved the stack trace to a debug level instead.

   Let us know if you have any questions.

   Thanks
   Bilal

Issue actions