# Audit Logging

### Overview

ZigiOps records platform activity through a set of configurable logging and data collection mechanisms. These tools help administrators monitor integration behavior, diagnose issues, and generate support files when working with the ZigiWave support team.

Logging and debug data collection settings are managed in the **General Settings** page under the **Debug** section.

ZigiOps → Settings → General Settings → Debug

### Log Types and Data Collection

ZigiOps provides several categories of data collection that can be enabled or disabled independently depending on your monitoring and troubleshooting needs.

#### HTTP Data Collection

**Collect HTTP Data** controls whether ZigiOps captures HTTP request and response data exchanged with integrated systems. This data is available on the Troubleshooting page and is useful for diagnosing connectivity or mapping issues.

**HTTP Data Purging** sets the interval at which collected HTTP data is automatically cleared from the Troubleshooting page. Configuring a shorter purging interval reduces storage use while still allowing recent data to be reviewed.

#### Payload Data Collection

**Collect Payload Data** controls whether ZigiOps captures the payloads exchanged during integration operations. This data is available on the Troubleshooting page and is particularly useful for verifying field mapping outputs.

**Payload Data Purging** sets the automatic purging interval for payload data on the Troubleshooting page.

### Status Data Purging

**Status Data Purging** defines how long integration status records are retained before they are automatically cleared from the Troubleshooting page.

### Debug Log Level

**Enable Debug Log Level (Overall)** switches the ZigiOps application log level to `DEBUG`. At this level, the platform writes significantly more detail to its log files, which is valuable when diagnosing complex issues. This setting should be used temporarily and reverted once the investigation is complete, as debug-level logging generates large log files over time.

{% hint style="info" %}
**Best Practice:** Enable debug logging only when actively troubleshooting. Leaving it enabled in production increases disk usage and can affect log readability.
{% endhint %}

### Restoring Default Settings

If any logging or debug setting has been modified, you can restore it to its default value at any time. To do so, select the corresponding field in General Settings and click the **Restore** button.

### Generating a Support File

The **Download Support File** feature allows administrators to package relevant platform data into a single file for sharing with the ZigiWave support team. This file can include troubleshooting data, application logs, and configuration files.

ZigiOps → Settings → General Settings → Download Support File

The following options are available when generating a support file:

### Troubleshooting Data

Enable this setting to include collected troubleshooting data in the support file. You can then configure two additional parameters:

**Integrations:** Select the specific integrations whose troubleshooting data should be included in the file.

**Past "N" Days:** Select how many days of historical troubleshooting data to include.

#### Logs

Enable this setting to include the ZigiOps application log files in the support file.

#### Config Files

Enable this setting to include the ZigiOps configuration files in the support file.

### Log Storage and Access

ZigiOps application logs are stored on the ZigiOps host. Administrators can access them directly from the file system for review or archiving, in addition to including them in the support file.

The default log directory depends on the operating system where ZigiOps is installed:

| Operating System | Default Log Directory        |
| ---------------- | ---------------------------- |
| Windows          | `C:\ZigiWave\ZigiOps\logs`   |
| Linux            | `/opt/zigiwave/zigiops/logs` |

**Note:** Exact directory paths may vary depending on your installation configuration. If in doubt, refer to your installation settings or contact [ZigiWave Support](https://support.zigiwave.com/).

### Security and Compliance Considerations

ZigiOps is designed with security and data privacy in mind. The platform does not store any of the data transferred between integrated systems. Collected troubleshooting data, such as HTTP request and payload logs, is retained locally on the ZigiOps host and is fully under the control of the platform administrator.

ZigiOps is ISO 27001 certified, ensuring that the platform meets enterprise-grade information security standards. For a full overview of the platform's security posture, see the [ZigiWave Security Information page](https://www.zigiwave.com/security).

### Frequently Asked Questions

<details>

<summary>Where are ZigiOps audit logs stored?</summary>

ZigiOps application logs are stored on the local file system of the ZigiOps host. On Windows, the default location is `C:\ZigiWave\ZigiOps\logs`. On Linux, the default location is `/opt/zigiwave/zigiops/logs`. Logs can also be packaged into a support file via General Settings.

</details>

<details>

<summary>Does ZigiOps store the data it transfers between systems?</summary>

No. ZigiOps does not store any of the data transferred between integrated systems. Debug data collection is optional and is stored locally on the ZigiOps host only.

</details>

<details>

<summary>How do I enable debug logging in ZigiOps?</summary>

Navigate to **ZigiOps → Settings → General Settings → Debug** and enable the **Enable Debug Log Level (Overall)** setting. Remember to disable this once troubleshooting is complete.

</details>

<details>

<summary>How do I share logs with ZigiWave Support?</summary>

Use the **Download Support File** feature in General Settings to package logs, configuration files, and troubleshooting data into a single file. Share this file with the [ZigiWave Support team](https://support.zigiwave.com/).

</details>


---

# 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.zigiwave.com/administration/audit-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.