---
date: 2025-11-03
title: Filter Sidebar for Tables
badge: Launch Week 4 🚀
description: Quickly filter tables by column values in the filter sidebar with one click.
author: Nimar, Leo
ogImage: /images/changelog/2025-11-03-filter-sidebar.png
---

> **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).

**Day 1 of [Launch Week 4](/blog/2025-10-29-launch-week-4)** is here, and we're excited to announce the new filter sidebar for tables.

## The Filter Sidebar

We've made filters a lot more accessible and intuitive with the new filter sidebar.

You can now filter for most column values with one click. The values are sorted by number of occurrences when in the `SELECT` mode.
For those columns, we show the number of occurrences within the selected time range.

More complex filters (such as "contains" and "does not contain") are still available and can be chained together by selecting the `TEXT` mode.

Previously created "Saved Views" continue to work and new "Saved Views" can still be created from the filter sidebar.

- [See all Launch Week releases](/blog/2025-10-29-launch-week-4)

<!-- 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/2025-11-03-filter-sidebar-for-tables.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>.