> For the complete documentation index, see [llms.txt](https://docs.cosmocloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cosmocloud.io/resources/apis/checking-logs.md).
# Checking Logs
Cosmocloud offers the **Logs** feature to user for easy debugging and development process. User can navigate to `Logs` tab present in `Application layer` to check logs.
## Exploring Log table
Let us see what values are displayed in `Log table` in cosmocloud.
1. **Timestamp** : It displays API call request time
2. **Request Id :** It is unique ID assigned to each API request call. Multiple Logs having same request ID means that all of those logs are received for same API call.
3. **Log Type** : It specify what type of information log holds for a specific API call. In image provided above both logs are for same API calls. One holds `REQUEST` information log e.g. endpoint,headers, request body etc. whereas one holds `RESPONSE` information e.g. response data etc.
4. **Log Level** : It specify the logs level for e.g. `DEBUG`, `INFO` , `ERROR` etc.
5. **Endpoint** : It specify the endpoint for API from which logs are received.
6. **Method** : It specify the API call method type
## Environment specific Logging
You can access API logs for specific environments using toggle present at top of `Log table`
Just select the environment you want to see the `Logs` for and you are good to go.
## Using Debug node
To utilise the `Logs feature` to the fullest we have provided `Debug node` which helps you to print values in the logs.
We can use this node to print values to the `Logs`. Let us assume we have a variable of type dict declared at top of our API flow and i want to check if values in it are correct. We can use debug node for same.
When you make an API call for same flow you will receive logs as specified below
Now as you can see, Apart from `REQUEST` and `REQUEST` you are now also receiving `DEBUG` log for same API call as well. when you click on **View** you will be able to see debug values.