# Viewing Logs

The Sesame Data `Logs` feature provides developers with a comprehensive toolset for investigating system activities and events. Through this functionality, users can access detailed records of actions, errors, and system activities, aiding in troubleshooting, performance optimization, and security analysis.

Key components of the Logs feature include:

1. **Event Tracking**: Logs capture a wide range of system events, including API requests, errors, response time and the token used.
2. **Timestamps**: Each log entry is timestamped, enabling users to precisely track the sequence of events and identify correlations between actions.
3. **Status**: If the calls are success or failure and the details of errors.
4. **Search and Filtering**: Developers can efficiently search and filter log entries based on various criteria such as time range, status, token name, and specific error messages.

{% hint style="info" %}
Please note that **our logs do not store** any personal or financial information. They exclusively retain technical errors and details about the requests made.
{% endhint %}

## How to view logs

Access `Sesame > Sesame Data > Logs`.

<figure><img src="/files/3CXBHzv6vacLYYDGcgf7" alt=""><figcaption><p>The Logs page</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.landytech.com/faq-and-troubleshooting/viewing-logs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
