> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/settings/monitoring/runtime-log-level.md).
# Runtime Log Level
Change how much detail each Tellius service writes to its logs, and which browser log levels are collected, while Tellius keeps running.
Under **Settings → System → Monitoring → Runtime Log Level**, super users change how much detail Tellius services write to their logs. A change applies straight away, without restarting any server. Use it when you, or Tellius Support, need more detail to troubleshoot a problem.
### Log levels
From the most detail to the least:
* **DEBUG:** everything, including detailed step-by-step information for troubleshooting.
* **INFO:** normal activity. This is the usual level.
* **WARN:** only warnings and errors.
* **ERROR:** only errors.
### Frontend Log Levels
Choose which log levels from people's browsers Tellius collects with usage telemetry. Open the list and select or clear **WARN**, **INFO** and **DEBUG**. **FATAL** and **ERROR** are always collected and can't be cleared. If the setting was never changed, **FATAL**, **ERROR**, **WARN** and **INFO** are selected.
Once you change the selection, **Cancel** and **Save** appear in the card. **Save** applies it, and **Cancel** goes back to the saved selection. See [Usage & Support](/tellius-6.4/settings/administration/usage-and-support.md) for usage telemetry.
### Service cards
Each card sets the log level of one Tellius service:
| Card | Service | Preset loggers |
| ---------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Resource Tracker | Resource Tracker | com.tellius.resourcetracker (default), root, com.tellius.resourcetracker.routing, com.tellius.resourcetracker.utils, com.tellius.resourcetracker.elasticsearch |
| Viz Engine | Viz Engine | com.tellius.vizengine (default), root, com.tellius.vizengine.requesthandlers, com.tellius.vizengine.tql, requestResponseLogging |
| Spark Service | Spark REST service | com.tellius (default), root, requestResponseLogging, com.tellius.rest.request.handlers.load, com.tellius.spark.library |
| TQL | TQL query service | com.tellius (default), root, com.tellius.rest.sql.tql, com.tellius.rest.request.handlers.tql, com.tellius.rest.sql.esql |
| Middleware | Middleware | root (default), Middleware.Logging, Middleware.Repo, Middleware.Application, MiddlewareWeb.Router |
| Kaiya | Kaiya | No logger. The card has a **Tag** list with the log level only. |
* **Logger Name:** the part of the service whose level you change. Pick a preset logger, or choose **Enter custom logger…** and type a class or module name, for example `com.tellius.package.ClassName`. Tellius checks that the logger exists and tells you whether it is available. A logger that doesn't exist can't be set.
* **Log Level:** **DEBUG**, **INFO**, **WARN** or **ERROR**. The card shows the level that is in effect now.
Once you change a card, **Cancel** and **Set** appear under it. **Set** applies the new level to that service at once, and a message shows the change, for example **Middleware: INFO → DEBUG**. **Cancel** goes back to the level in effect.
When the page opens, Tellius checks whether a service's root and application loggers are set to different levels. If they are, a message tells you so. Setting a level on the card applies it to both.
{% hint style="warning" %}
**Turn DEBUG back off.** DEBUG writes far more to the logs than INFO. Set DEBUG only for the service and logger Tellius Support asks about, reproduce the problem, then set the level back to **INFO**.
{% endhint %}
### Who can see this page
Only super users see **Runtime Log Level** in Settings. A custom role reaches it with **Manage system** under **Administration**. See [Custom roles](/tellius-6.4/settings/users-and-access/custom-roles.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://help.tellius.com/tellius-6.4/settings/monitoring/runtime-log-level.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.
