> For the complete documentation index, see [llms.txt](https://docs.ostara.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ostara.dev/features/application-features/manage/loggers.md).
# Loggers
### Overview
Loggers at the application level is exactly the same as the instance level [Loggers](/features/instance-features/manage/loggers.md), but apply their changes to every active instance within the application.
### Usage
To change the log level of a given logger, simply click on one of the log levels to the right. The change will affect any other loggers within the hierarchy of the logger which were not explicitly set on Ostara or in the app configuration. At any point, you may press the **Reset** button on the right of any Ostara configured logger and reset it to its original state.
Loggers which were not configured, but inherit configuration will appear faded, whereas explicitly configured loggers will appear solid.
You can also filter the list to show only explicitly configured loggers by clicking on **Configured** in the top right:
Additionally, you can choose to only show loggers which represent classes by clicking on **Classes** in the top right
In addition to this, if multiple instances have conflicting log levels for certain loggers, they will be displayed like so:
### Required Abilities
* [Loggers](/features/abilities.md)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ostara.dev/features/application-features/manage/loggers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
