> For the complete documentation index, see [llms.txt](https://inscada.gitbook.io/ins/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inscada.gitbook.io/ins/en-1/user-interface/logs.md).

# Logs

You can view all the actions in the inSCADA platform from the logs menu. With Logs, you can filter the errors, information and warnings in your system with the parameters entered in the search criteria, detect errors, perform performance evaluations and ensure that your system operates at the optimum point.

* You can see the execution times of your Script and Expression codes,
* You can see communication errors on device and frame on variable basis,
* You can see your not-activated frames, variables as warning,
* You can see all errors related to your connections.

It informs you that you can go to the source of all errors and make corrections.

![Figure 1 : Logs](/files/-LOUIlrGdlwkeWClAUo5)

## Search Form

It is a filter form where you can search among records.

#### Project 

Allows you to list the records of the project you selected.

#### Source

It provides information, error, and warning messages to be listed by source. inSCADA categorizes the resources within the system; Script Runner, Communication, Alarm, Animation Element, and Global.

#### Activity

Allows you to list the entries in which any word appears. For example, Modbus, DNP3 , Timeout.

#### Log Severity

Information messages are divided into 3 groups within the inSCADA platform: Information, Warning, Error.

#### Date Range

Provides a list of actions between two dates.

{% hint style="info" %}
Do not make the date range long. This will cause the records to arrive later. In addition, deleting the records after you have made your review makes it easier to recognize newly created records.
{% endhint %}


---

# 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://inscada.gitbook.io/ins/en-1/user-interface/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.