You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a Back End service application, chances are that there's already an existing logger tight to the logging system (e.g. Logstash and Kibana) that one might want to use.
However, at the moment, trace-unhandled only allows to log using console.error.
It would make sense to keep that as the default behaviour, while providing the possibility to override that and use a custom logger.
What do you think?
The text was updated successfully, but these errors were encountered:
In a Back End service application, chances are that there's already an existing logger tight to the logging system (e.g. Logstash and Kibana) that one might want to use.
However, at the moment,
trace-unhandled
only allows to log usingconsole.error
.It would make sense to keep that as the default behaviour, while providing the possibility to override that and use a custom logger.
What do you think?
The text was updated successfully, but these errors were encountered: