---
date: 2026-05-15
title: "Choose columns and compress blob storage exports"
description: Pick which field groups are written to each row and enable gzip compression in scheduled S3, GCS, and Azure exports. Shrink files and drop fields you don't want to land in your warehouse.
author: Niklas
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the current documentation (https://langfuse.com/docs) and the API/SDK reference (https://api.reference.langfuse.com).

Two new controls let you reduce the size of your scheduled blob storage exports: column selection and gzip compression. Both are configurable per integration in **Project Settings → Integrations → Blob Storage**.

**Column selection.** Eleven groups cover the enriched observations row — toggle off the ones you don't need:

- **Drop `metadata` for privacy.** Keep user data out of your warehouse without filtering downstream.
- **Drop `io` to shrink files.** Inputs and outputs are usually the largest columns; deselecting them produces dramatically smaller exports for cost or latency analytics.
- **Drop `tools` and `prompt`** when your downstream consumer only needs traces, timings, and cost.

  ![Blob storage export field group settings](/images/changelog/2026-05-15-blob-storage-export-field-groups/blob_exporter_settings_field_groups.png)

The `core` group (`id`, `trace_id`, `start_time`, `end_time`, `project_id`, `parent_observation_id`, `type`) is required and always exported. The other ten groups — `basic`, `time`, `io`, `metadata`, `model`, `usage`, `prompt`, `metrics`, `tools`, `trace_context` — are individually toggleable. Existing integrations continue to export all groups; no action needed unless you want to narrow the schema.

Field groups are only available with the new enriched observations export, which is based on the [denormalized v4 data model](/docs/v4). The legacy export source uses a fixed column set and is unaffected.

**Gzip compression.** New integrations compress exported files with gzip by default, producing `.csv.gz`, `.json.gz`, or `.jsonl.gz` files readable by most data warehouses and pipeline tools without a manual decompression step. Toggle **Gzip Compression** off if your consumer expects plain files. Existing integrations are unaffected — they were backfilled as uncompressed so nothing breaks for current consumers.

Both controls are available on the REST API: `exportFieldGroups` and `compressed` on [`GET`/`PUT /api/public/integrations/blob-storage`](https://api.reference.langfuse.com/#tag/blobstorageintegrations).

## Learn more

- [Export to Blob Storage](/docs/api-and-data-platform/features/export-to-blob-storage)
- [Export Field Reference](/docs/api-and-data-platform/features/blob-storage-export-fields)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2026-05-15-blob-storage-export-field-groups.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.