# Server Logs

Thigner.io server instances provide a logging console that allows visualizing the program status and events in real-time. These data can be used to evaluate the behavior of the server or any integration that is being developed. 

{% hint style="info" %}
This feature is only available for the instance's manager account 
{% endhint %}

## Start Logging

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

Follow the next steps to start logging the events of the server instance:

<figure><img src="/files/8GQbiwLcJFk8cQ4t8Xaf" alt=""><figcaption></figcaption></figure>

1. Go to the "Cluster Hosts" section of Thinger.io's main menu. The Host list displays all server instances connected within the same cluster, classified by their web domain.
2. Click the desired instance to access the server administration panel&#x20;
3. On the top right corner, choose the "Logs" tab to open the logging console
4. Press the "Connect" button to start the log sampling

<figure><img src="/files/7FBUxo8unjyqN2IrcS7q" alt=""><figcaption></figcaption></figure>

The structure of the log entries consists of six columns in which the following data is specified:

* **Date:** YYYY-MM-DD
* **Hour:** HH:MM:SS.SSS
* **PC**: Program Counter in seconds
* **Working Thread:** Thinger.io program has been created to optimize host architecture with multithread execution. This column identifies the thread that managed each event.
* **Program Module:** This column informs about the feature that is being used by each event.
* **Message:** Is the log content including a message type identification and a description

<br>

| Date | Hour | PC | Thread |   |   |
| ---- | ---- | -- | ------ | - | - |


---

# 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.thinger.io/server/server-configuration/server-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.