The most ancient but the most effective way of understanding the system is to check the logs to see if they contain something that we print in case of a problem. Structured logging is particularly helpful if you want to troubleshoot even faster. However, it is not straightforward to check for the logs on CloudWatch. Plus, you can only check the logs of a function at a once. Logs page solves these problem by giving the flexibility of searching the logs for all of your serverless stacks.
You can navigate to logs page from left side bar by clicking Logs icon button.
In logs page, logs are listed in terms of :
Time - log time
Function Name - Related function of log
Actions - Go to invocation. You can go to invocation that log is included in by clicking this action button.
Show more - If message of the log long to display click on the row to show all message.
You can change time interval for displaying logs that generated in a specific time interval using time settings.
You can filter your logs using query bar.
Log Level: Some logs can be more critical or more mediocre compared to others. For example;
console.log() represents different level of severity. You can also give your own log level with Thundra loggers. You can filter the logs according to their log level.
Log Message: You can make a wild card search in the logs using wild cards or exact words. For example; you can type
*undr* and this filter can bring you the logs which contain
Log Context: You can filter the logs according to their source with this field.
Function Name: You can make a wild card search in the logs using wild cards or exact words in function name of logs.