> For the complete documentation index, see [llms.txt](https://docs.blocktorch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocktorch.xyz/use-cases/searching/logs.md).

# Logs

Logs in blocktorch are all the records of events and transactions and that occur within a decentralized application and its utilized services. The logs play a critical role in monitoring the service's health, troubleshooting issues, and understanding user activities. 

The result of your logs query always include:

* **`Status`**: Logs are categorized by status levels such as <mark style="color:green;background-color:green;">EVENT</mark>, <mark style="color:blue;background-color:blue;">SUCCESS</mark>, <mark style="color:purple;background-color:purple;">REVERTED</mark>, <mark style="color:red;background-color:red;">FAILED</mark>. This helps in filtering logs based on relevance for your query.
* **`Timestamp`**: Each log entry includes a timestamp, indicating when the event occurred. This is crucial for tracking the order of events. In Blocktorch's free version everyone can access logs up to 7 days in the past. You can filter for specific time windows or also look at the logs as they are streamed live.
* **`Type`**: There are 4 types of logs blocktorch captures:
  * **`TRANSACTION`**: a transaction call is produced with any invoked transaction, and can result in logs of the other 3 types being produced
  * **`CALL`**: a call log is produced when a smart contract function is called
  * **`DELEGATE`**: a delegate log is produced when a caller contract executes code from another smart contract, that is especially the case when using proxy architecture
  * **`STATIC`**: a static call log is produced when a read function is invoked so there is no change to state
* **`Service/Contract`**: The contract message provides details about the smart contract / service that produced the log and which chain it has been triggered on
* **`Content`**: Additional context is given through information like the function name invoked, its transaction hash or the error message, if the smart contract ABI is unknown the signature will be `anonymous`

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

{% hint style="info" %}
The pre-filtered logs for a specific smart contract can be found on the detail page of a smart contract by clicking your contract in the smart contract overview page
{% endhint %}