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

# Configure Request Logging

> Control what data is stored for all LLM requests in your organisation

## Overview

The AI Gateway allows organisation owners to control what data is logged for all LLM requests across their organisation. This feature provides flexibility between complete observability and privacy compliance, enabling organisations to choose the appropriate logging level based on their security and compliance requirements.

## How It Works

Organisation owners can configure two aspects of request logging:

1. **Logging Mode**: Choose between Full Logging or Metrics Only mode
2. **Workspace Override**: Allow or restrict workspace managers from changing the organisation-level logging settings

These settings apply to all requests made within the organisation, ensuring consistent data handling practices across all teams and projects.

## Configuration

### Setting Up Request Logging

1. Navigate to `Admin Settings` in Strata Cloud Manager
2. Go to the `Organization Properties` section
3. Find the `Request Logging` settings
4. Configure your logging preferences
5. Save your changes

### Logging Modes

#### Full Logging

When enabled, the AI Gateway stores:

* Complete request payloads
* Full response content
* All associated metrics and metadata

This mode provides comprehensive observability for debugging, monitoring, and optimization purposes.

#### Metrics Only (Privacy Mode)

When enabled, the AI Gateway only tracks:

* Usage statistics (tokens, latency, costs)
* Request metadata
* Error information (without sensitive content)

This mode ensures privacy compliance by not storing any request or response content, while still maintaining essential operational metrics.

### Workspace-Level Control

The **"Allow respective workspace managers to toggle Request Logging"** option determines whether workspace managers can override the organisation-level settings:

* **When enabled**: Workspace managers can change logging settings for their specific workspace
* **When disabled**: All workspaces inherit and must use the organisation-level logging settings

<Note>
  When workspace-level control is disabled, any existing workspace-specific logging settings will be overridden by the organisation settings.
</Note>

## Workspace Configuration

If workspace-level control is enabled, workspace managers can configure logging for their workspace:

1. Navigate to the workspace settings
2. Click on your workspace and select the **Edit (🖊️) option**
3. In the **Edit Workspace** menu, head over to Workspace Properties
4. Configure the **Request Logging** setting
5. Save your changes

<Warning>
  Changing from Full Logging to Metrics Only will not retroactively remove previously logged data. [Contact support](mailto:support@portkey.ai) if you need to purge historical logs.
</Warning>

## Precedence Order

When different logging settings exist at multiple levels:

1. **Workspace settings** (highest priority) - if workspace-level control is enabled
2. **Organisation settings** (applies when workspace control is disabled)


## Related topics

- [MCP Advanced Configuration](/docs/aigw/product/mcp-gateway/advanced-configuration.md)
- [OpenAI Swarm](/docs/aigw/integrations/agents/openai-swarm.md)
- [Request Parameters Check](/docs/aigw/integrations/guardrails/request-parameters-check.md)
- [JWT Authentication](/docs/aigw/product/enterprise-offering/org-management/jwt.md)
- [AI Gateway](/docs/aigw/product/ai-gateway.md)