> For the complete documentation index, see [llms.txt](https://cloakedkeys.gitbook.io/ofsc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloakedkeys.gitbook.io/ofsc/getting-started/controlling-output.md).

# Controlling Output/Logs

various options for output

***

## Log Streams

### Discord

> ℹ️ **Discord logs will solely contain the log message, whereas other logs will include additional details like function calls and line numbers.**

> ℹ️ **You can set the environment default 'OFSC\_DISCORD\_ASYNC' to true to spend up discord logs**\
> **This could result in logs not being in order**

> ℹ️ **For optimal performance with Discord, it's recommended to use the Normal or below logging level. Levels like Debug generate a significant amount of data, requiring numerous requests to process and log**

The output goes to the Discord channel

#### LEVELS

*In ascending output order*

* OFF
* LOW
* NORMAL

***

### Output

**output to the console**

> ℹ️ **For clear console output, it is recommended to set the logging level to Normal or below to avoid excessive messages**

#### LEVELS

*In ascending output order*

* PROMPT
* LOW
* NORMAL
* DEBUG

***

### Log

**output to logfile within the config folder** (`~/.config/ofscraper/logging/`)

*In ascending output order*

* OFF
* LOW
* NORMAL
* DEBUG
* TRACE

Deprecated

* STAT

***

> ℹ️ **Logs are safe to share after a check:** the OnlyFans session cookie and the Fansly token are masked in log lines. Still look for personal details before posting a log.

## Log levels details

With the 1.9 release, you gain increased control over the output level.

**OFF**

```

This feature allows you to deactivate Discord or log file logging. 
By default, these outputs are turned off.
```

**PROMPT**

```

The program needs prompts and specific console output for certain operations. 
It configures console output to only show necessary information. 
Providing a scraping action and usernames should largely disable most,
 if not all, additional output.
```

**LOW**

```

It disables all progress bars and displays essential program status while running. 
It also includes avatars and applies to all output destinations.
```

**STATS**

> ℹ️ **Removed in 3.5**

```

Slight modification to LOW no avatars will be shown

```

**NORMAL**.

```
The default console output level, progress bars
 and general status messages are displayed. 
 All output destinations, including Discord and log files, 
 receive general status messages but exclude progress bars.
```

**DEBUG**

```
It includes debugger messages and tracebacks within the 
'Normal' output level. 
This applies to all output destinations.

```

**TRACE** (log file only)

```

This mode provides the most detailed and extensive 
information compared to all other modes.
```


---

# 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://cloakedkeys.gitbook.io/ofsc/getting-started/controlling-output.md?ask=<question>&goal=<user_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.