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
The module reporting has no logs. It's frustrating when a report fails and we can't see more than one or two requests with no useful information about the fault.
Tasks:
Add the module (import { log } from '../logger';)
Add INFO logs for all methods (at least one message just for follow the trace)
Add DEBUG logs for all methods, where we can see details such as the URLs, filters, API ID, and any other relevant information for a troubleshooting session.
Add ERROR logs for all the catch and all parts of the code where we are handling any kind of error.
The text was updated successfully, but these errors were encountered:
Here 73b3ccb we've added logs for INFO, DEBUG and ERROR level. Now the reporting module shows valuable information and errors when "debug" mode is disabled and when "debug" mode is enabled we can see the full trace in all functions.
Hi team,
The module
reporting
has no logs. It's frustrating when a report fails and we can't see more than one or two requests with no useful information about the fault.Tasks:
import { log } from '../logger';
)INFO
logs for all methods (at least one message just for follow the trace)DEBUG
logs for all methods, where we can see details such as the URLs, filters, API ID, and any other relevant information for a troubleshooting session.ERROR
logs for all thecatch
and all parts of the code where we are handling any kind of error.The text was updated successfully, but these errors were encountered: