> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reviewing and Exporting Logs

> Read the log directly on the gateway machine, set the log level and file rotation, and export the complete set for support.

The gateway writes its log on the machine it runs on. The gateway's window shows
it in the *Logging* tab; in the browser you only see an excerpt, in the
[Diagnostics](/docs/en/scan/gateway#diagnostics) tab of the gateway detail page.

## Reading the log

The *Log* table has the columns *Time*, *Level*, *Message* and *Source*; a search
field above it filters across all four columns.

At most 500 entries are shown, the most recent by timestamp. Older entries are
only available through the export (see below); the table does not load further
pages.

<Tip>
  *Open log directory* takes you straight to
  `%ProgramData%\Docusnap\EnterpriseGateway`, where the log files and the
  configuration are stored.
</Tip>

## Log level and file rotation

The tab has three settings: *Logging level:*, *Maximum log file size (MB):* and
*Maximum number of log files:*. The level has five values — *Information*,
*Warning*, *Error*, *Debug*, *None*.

<Warning>
  If the stored configuration carries a level the gateway does not know, it selects
  *None* and reports the unknown level in a red banner. Logging is then disabled.
  Select a valid level before you *Save* – saving without your own selection stores
  *None*.
</Warning>

<Note>
  You can set the same level in the browser under
  [Logging and Support](/docs/en/scan/gateway#logging-and-support). The file size is
  entered here in megabytes, in the browser through a separate unit field.
</Note>

*Save* also checks the IP ranges from the *Registration* tab — if one of them is
invalid, saving the logging settings fails as well.

## Exporting for support

*Export* creates an archive in a directory you choose, with a timestamp in its
name (`Supportfiles-….zip`). It contains every log file plus JSON files with the
versions of the scan modules and the gateway, the loaded assemblies, and the
gateway's start and system information.

<Warning>
  Give support this archive, not a printout of the table: only the archive contains
  the complete set.
</Warning>

## Deleting logs

*Delete logs* asks for confirmation and then works through the files from newest
to oldest. The newest file is emptied rather than deleted, because the service
keeps writing to it; the others are removed.

<Warning>
  This cannot be undone, and it also affects entries the table no longer shows
  because of its limit. Export first if you still need the set.
</Warning>

## Viewing loaded assemblies

Three further, read-only tabs show what the gateway has loaded:

| Tab | Content |
| - | - |
| *Plugin version* | the scan modules with their version |
| *Loaded assemblies* | the assemblies of the gateway itself |
| *Plugin assemblies* | the assemblies per scan module, linked through the *Module* column |

The values come from the running process. In the browser, the
[Diagnostics](/docs/en/scan/gateway#diagnostics) tab combines the same information
into one table and adds status and the time of the last update.

## Related

State, configuration and remote access to the log and diagnostics are covered in
[Managing Gateways](/docs/en/scan/gateway).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.