# Getting started with ClearInsights Logging

### Logs

#### Log Types

* **Critical:** For failures that require immediate attention. Examples: data loss scenarios, out of disk space.
* **Error:** For errors and exceptions that cannot be handled. These messages indicate a failure in the current operation or request, not an app-wide failure.
* **Warning:** For abnormal or unexpected events. Typically includes errors or conditions that don't cause the app to fail.
* **Informational:** Tracks the general flow of the app. May have long-term value.
* **Trace:** Contain the most detailed messages. These messages may contain sensitive app data. These messages are disabled by default and should ***not*** be enabled in production.

#### Overview

![](/files/TKBIM6E1PbVurHLlcoaS)

For each log you will see information related to the message, product, environment, source and stack trace. **Insights** tab will be available depending on the discovery of additional information. 

### Reports

Reporting gives you an overview of Critical and Error log types. You can filter by date range and top 5, 10, 15 to get insight into errors that occur most frequently.

### Settings

Settings is where you can who can receive which kind of notifications and how frequently.\
\
For more see:

{% content-ref url="/pages/nW9hMaZ8w4uc9hiGGnV0" %}
[Notifications](/introducing-clearinsights/clearinsights-core-concepts/notifications.md)
{% endcontent-ref %}


---

# 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.clearinsights.io/clearinsights-products/clearinsights-logging/getting-started-with-clearinsights-logging.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.