> 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.

<figure><img src="/files/LJTEe6aTiTYVDtaSWHCs" alt=""><figcaption></figcaption></figure>

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`

<figure><img src="/files/ffInaDNvSVDHGIZElBeC" alt=""><figcaption></figcaption></figure>

Just select the environment you want to see the `Logs` for and you are good to go.

## Using Debug node&#x20;

To utilise the `Logs feature` to the fullest we have provided `Debug node` which helps you to print values in the logs.

<figure><img src="/files/CBKNebSbYaSPYkkLrF1f" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/DrtwCpiCahY9MY4wLWyU" alt=""><figcaption></figcaption></figure>

When you make an API call for same flow you will receive logs as specified below<br>

<figure><img src="/files/SLB4V7cCTJay3PXwH0lS" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/ZIViJ0mS6fpabDGhrb3e" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cosmocloud.io/resources/apis/checking-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.